Deploying Application Fails With Error: java.lang.UnsatisfiedLinkError: mqjbnd05.dll: Can't find dependent libraries (Doc ID 578376.1)

Last updated on FEBRUARY 18, 2025

Applies to:

Symptoms

• Application was built following the IBM MQ WebSphere sample from OTN site:
  
  How to Configure and Use Oracle's JMS Connector with IBM WebSphere MQ JMS
  Note that this document is no longer available due to the age of this product.
  
  
  
• Deploying the application fails with the following error
  Caused by: java.lang.UnsatisfiedLinkError: <PATH>\IBM\WebSphere MQ\Java\lib\mqjbnd05.dll: Can't find dependent libraries

• The OH\j2ee\<instance>\log\<instance_group_x>\oc4j\log.xml file has the following exception stack
  <MSG_TEXT>[how-to-connect-to-mqseries] An error occured deploying EJB module:
  java.lang.InstantiationException: Resource exception(MQJMSRAInstanceName) for MessageDrivenBean
  DealerEjbName during endpoint activation: Error when attempting a create a Worker thread for
  endpoint: javax.resource.ResourceException: createJMSObjects: java.lang.UnsatisfiedLinkError:
  <PATH>\IBM\WebSphere MQ\Java\lib\mqjbnd05.dll: Can't find dependent libraries.:
  javax.resource.ResourceException: createJMSObjects: java.lang.UnsatisfiedLinkError:
  <PATH>\IBM\WebSphere MQ\Java\lib\mqjbnd05.dll: Can't find dependent libraries</MSG_TEXT>
  
  <SUPPL_DETAIL><![CDATA[java.lang.InstantiationException: Resource
  exception(MQJMSRAInstanceName) for MessageDrivenBean DealerEjbName during endpoint activation:
  Error when attempting a create a Worker thread for endpoint: javax.resource.ResourceException:
  createJMSObjects: java.lang.UnsatisfiedLinkError: <PATH>\IBM\WebSphere MQ\Java\lib\mqjbnd05.dll: Can't find dependent libraries.: javax.resource.ResourceException:
  createJMSObjects: java.lang.UnsatisfiedLinkError: <PATH>\IBM\WebSphere MQ\Java\lib\mqjbnd05.dll: Can't find dependent libraries
  at com.evermind.server.ejb.MessageDrivenHome.initializeJCAServer(MessageDrivenHome.java:576)
  at com.evermind.server.ejb.MessageDrivenHome.initialize(MessageDrivenHome.java:225)
  at com.evermind.server.ejb.MessageDrivenHome.start(MessageDrivenHome.java:128)
  atcom.evermind.server.ejb.EJBPackageDeployment.startMessageDrivenHomes(EJBPackageDeployment.java:1182)
  at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:1051)
  at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:217)
  at com.evermind.server.Application.setConfig(Application.java:413)
  at com.evermind.server.Application.setConfig(Application.java:314)
  at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1853)
  at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:512)
  at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:196)
  at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
  at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
  at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
  at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
  at java.lang.Thread.run(Thread.java:595)
  ]]></SUPPL_DETAIL>

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.