Unable To Resolve 'eis.jms.WLSConnectionFactoryJNDIXA' While Constructing JMS Messaging Bridge (Doc ID 1595863.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.5 to 10.3.6
Information in this document applies to any platform.

Symptoms

When attempting to creating a JMS Messaging Bridge in the WLS Admin Console, the jms-xa-adp.rar adapter does not get installed and you get the following error in the WLS Console :-


Error: Failed to register library Extension-Name-jms-xa-adp, Implemenation-Version: 10.3.5.0. Library cannot have implementation-Version set, without also specifying its Specification-Version



Snippet from SOA log file soa_server1_JMS.log:

#### <> <> <Bridge "ChromeBridge" failed to get one of the adapters from JNDI (javax.naming.NameNotFoundException: Unable to resolve 'eis.jms.WLSConnectionFactoryJNDIXA'. Resolved 'eis.jms'; remaining name 'WLSConnectionFactoryJNDIXA').
javax.naming.NameNotFoundException: Unable to resolve 'eis.jms.WLSConnectionFactoryJNDIXA'. Resolved 'eis.jms'; remaining name 'WLSConnectionFactoryJNDIXA'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at weblogic.jms.bridge.internal.MessagingBridge.startInternal(MessagingBridge.java:565)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1034)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms