Unable To Create Queue Receiver Due To JMSException (Doc ID 2261130.1)

Last updated on JUNE 07, 2017

Applies to:

Oracle SOA Suite - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

3 node SOA servers cluster connecting to queues in OSB domain by using JMS JNDI. One of the OSB server is brought down (which brought down associated JMS server), however SOA servers are still trying to look up JMS server in shutdown OSB server.


Unable to create Queue receiver due to JMSException.
The error can occur due to one of the following; 1) when a destination either is not understood by a provider or is no longer valid. 2) If using message selector, the message selector syntax is invalid. 3) session fails to create a receiver due to some internal error 4) an internal error on the JMS provider/server side.
Please examine the wrapped exception from the JMS provider to determine the exact cause. Message selector issues can be resolved by correcting the syntax. If the destination is no longer valid, either re-create the destination or correct the adapter spec properties to point to the correct destination. If the failure is due to some internal error on the JMS provider side, please examine additional JMS provider/server logs to determine the problem. If transient in nature, adapter will try to recover from such transient issues on its own.
 BINDING.JCA-12135
ERRJMS_ERR_CR_QUEUE_CONS.
Unable to create Queue receiver due to JMSException.
The error can occur due to one of the following; 1) when a destination either is not understood by a provider or is no longer valid. 2) If using message selector, the message selector syntax is invalid. 3) session fails to create a receiver due to some internal error 4) an internal error on the JMS provider/server side.
Please examine the wrapped exception from the JMS provider to determine the exact cause. Message selector issues can be resolved by correcting the syntax. If the destination is no longer valid, either re-create the destination or correct the adapter spec properties to point to the correct destination. If the failure is due to some internal error on the JMS provider side, please examine additional JMS provider/server logs to determine the problem. If transient in nature, adapter will try to recover from such transient issues on its own.

at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:574)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:478)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:355)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:947)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:797)
at oracle.tip.adapter.jms.inbound.JmsConsumer.recover(JmsConsumer.java:1089)
at oracle.tip.adapter.jms.inbound.JmsConsumer.runInbound(JmsConsumer.java:1000)
at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:846)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:184)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:209)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:618)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:39)
Caused by: weblogic.jms.common.JMSException: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.jms.backend.JMSServerNAME'. Resolved 'weblogic.jms.backend'; remaining name 'JMSServerNAME'
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:127)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:51)
at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:3227)
at weblogic.jms.client.JMSSession.setupConsumer(JMSSession.java:2966)
at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2896)
at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2860)
at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:2755)
at weblogic.jms.client.WLSessionImpl.createReceiver(WLSessionImpl.java:971)
at oracle.tip.adapter.jms.JMS.WLJMSConnection$12.run(WLJMSConnection.java:534)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:368)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:132)
at weblogic.jms.extensions.JMSDestinationAvailabilityHelper$DestinationAvailabilityListenerWrapper.runAs(JMSDestinationAvailabilityHelper.java:538)
at oracle.tip.adapter.jms.JMS.WLJMSConnection.createQueueReceivers(WLJMSConnection.java:527)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:571)
... 16 more
Caused by: weblogic.jms.common.JMSException: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.jms.backend.JMSServerNAME'. Resolved 'weblogic.jms.backend'; remaining name 'JMSServerNAME'
at weblogic.utils.StackTraceDisabled.unknownMethod()
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.jms.backend.JMSServerNAME'. Resolved 'weblogic.jms.backend'; remaining name 'JMSServerNAME'
... 1 more

]]

 

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