My Oracle Support Banner

Unable To Create Topic Subscriber Due To JMSException. (Doc ID 2861114.1)

Last updated on APRIL 07, 2022

Applies to:

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

Symptoms

On : 12.2.1.4.0 version, Fabric

Unable to create Topic subscriber due to a JMSException after upgrading from 12.1.3 to 12.2.1.4 .


The following error occurs.

ERROR
-----------------------
[2022-02-06T17:41:27.083-06:00] [soa_server1] [ERROR] [] [oracle.soa.adapter.jms.connection] [tid: [ACTIVE].ExecuteThread: '63' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: 6b98b833-0a53-43ec-a745-65ca3797c80e-000001b7,0] [APP: soa-infra] [partition-name: DOMAIN] [tenant-name: GLOBAL] oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSDestination oracle.tip.adapter.jms.JMS.JMSDestination@4299ffd9, String null) caught an Exception when trying to create a JMS Subscriber. Error message=Cannot change the details of a durable subscription when it is in use, error code=null, error name=javax.jms.JMSException: Cannot change the details of a durable subscription when it is in use

[2022-02-06T17:41:27.610-06:00] [soa_server1] [ERROR] [] [oracle.soa.adapter.jms.inbound] [tid: [ACTIVE].ExecuteThread: '63' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: 6b98b833-0a53-43ec-a745-65ca3797c80e-000001b7,0] [APP: soa-infra] [partition-name: DOMAIN] [tenant-name: GLOBAL] JMSMessageConsumer_init:[destination = jms/fabric/EDNTopic (payload = 1, subscriber = Formalizac_SCA_160622)]:ERRJMS_ERR_CR_TOPIC_CONS.[[
Unable to create Topic subscriber 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 subscriber due to some internal error and 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-12134
ERRJMS_ERR_CR_TOPIC_CONS.
Unable to create Topic subscriber 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 subscriber due to some internal error and 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:544)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:478)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:358)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:950)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:881)
at oracle.tip.adapter.jms.inbound.JmsConsumer.runInbound(JmsConsumer.java:943)
at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:930)
at oracle.integration.platform.blocks.event.jms2.EdnWorkManager$EdnWork.run(EdnWorkManager.java:111)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:209)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)
Caused by: javax.jms.JMSException: Cannot change the details of a durable subscription when it is in use
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:127)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:51)
at weblogic.messaging.dispatcher.CrossPartitionDispatcher.dispatchSync(CrossPartitionDispatcher.java:52)
at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:3230)
at weblogic.jms.client.JMSSession.setupConsumer(JMSSession.java:2969)
at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2899)
at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2863)
at weblogic.jms.client.JMSSession.createDurableSubscriber(JMSSession.java:2669)
at oracle.tip.adapter.jms.JMS.WLJMSConnection$9.run(WLJMSConnection.java:450)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:386)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:132)
at weblogic.jms.extensions.JMSDestinationAvailabilityHelper$DestinationAvailabilityListenerWrapper.runAs(JMSDestinationAvailabilityHelper.java:546)
at oracle.tip.adapter.jms.JMS.WLJMSConnection.createDurableTopicSubscribers(WLJMSConnection.java:438)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:526)
... 15 more


Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


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