Why do we see UnsatisfiedLinkError when restarting the JBoss A-MQ ?

Solution Unverified - Updated -

Issue

  • "java.lang.UnsatisfiedLinkError" was occurred while restarting JBoss A-MQ as following:
JBossA-MQ:karaf@root> dev:restart
JBossA-MQ:karaf@root> 
Please wait, JBoss A-MQ is initializing...
ERROR: Bundle org.apache.servicemix.bundles.snappy-java [113] Error starting mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.snappy-java/1.0.4.1_1 (org.osgi.framework.BundleException: Activator start error in bundle org.apache.servicemix.bundles.snappy-java [113].)
java.lang.UnsatisfiedLinkError: Native Library /Users/sjavurek/Fuse/JBossFuse/jboss-a-mq-6.0.0.redhat-024/data/cache/bundle113/version0.0/bundle.jar-lib/0/org/xerial/snappy/native/Mac/x86_64/libsnappyjava.jnilib already loaded in another classloader
    at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1792)
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1716)
    at java.lang.Runtime.loadLibrary0(Runtime.java:823)
    at java.lang.System.loadLibrary(System.java:1045)
    at org.xerial.snappy.SnappyBundleActivator.start(SnappyBundleActivator.java:33)
    at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
    at org.apache.felix.framework.Felix.doActivateBundle(Felix.java:2317)
    at org.apache.felix.framework.Felix$7.call(Felix.java:2255)
    at org.apache.felix.framework.Felix$6.call(Felix.java:2199)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
    at java.lang.Thread.run(Thread.java:680)
  • The issue can be reproduced as following:

    • 1) Start JBoss A-MQ using "$KARAF_HOME/bin/karaf"
    • 2) Restart JBoss A-MQ using following utility
         $KARAF_HOME%/bin/client -a 8101 -h localhost -u username -p password dev:restart

NOTE: JBoss A-MQ works without any troubles even though the error was occurred.

  • Why did this error occur?

  • When the error occurs, are there any functions that is not available? Even if this error occurs, isn't there any problem?

  • Used "dev:restart" to restart JBoss A-MQ. Are there any commands except "dev:restart" to restart JBoss A-MQ?

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.