Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by wildfly-ci
, 1 year ago
no artemis-native-64 in java.library.path org.jboss.as.test.manualmode.messaging.ha.ReplicatedFailoverTestCase.testBackupActivation: java.lang.RuntimeException: org.jboss.as.test.integration.common.jms.JMSOperationsException: "WFLYCTL0212: Duplicate
java.lang.UnsatisfiedLinkError: no artemis-native-64 in java.library.path
org.jboss.as.test.manualmode.messaging.ha.ReplicatedFailoverTestCase.testBackupActivation: java.lang.RuntimeException: org.jboss.as.test.integration.common.jms.JMSOperationsException: "WFLYCTL0212: Duplicate resource [
    (\"subsystem\" => \"messaging-activemq\"),
    (\"server\" => \"default\"),
    (\"jms-queue\" => \"FailoverTestCase-Queue\")
]"	at org.jboss.as.test.integration.common.jms.JMSOperationsProvider.execute(JMSOperationsProvider.java:145)	at org.jboss.as.test.integration.common.jms.ActiveMQProviderJMSOperations.executeOperation(ActiveMQProviderJMSOperations.java:181)	at org.jboss.as.test.integration.common.jms.ActiveMQProviderJMSOperations.createJmsQueue(ActiveMQProviderJMSOperations.java:87)	at org.jboss.as.test.integration.common.jms.ActiveMQProviderJMSOperations.createJmsQueue(ActiveMQProviderJMSOperations.java:79)	at org.jboss.as.test.manualmode.messaging.ha.FailoverTestCase.setUpServer1(FailoverTestCase.java:46)	at org.jboss.as.test.manualmode.messaging.ha.ReplicatedFailoverTestCase.setUpServer1(ReplicatedFailoverTestCase.java:48)