javax.jms.InvalidClientIDException due to Duplicate ClientID using Durable Subscriber (Doc ID 2258107.1)

Last updated on MAY 02, 2017

Applies to:

Oracle WebLogic Server - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

Weblogic JMS bridge generating error in Foreign JMS server using durable subscriber. 

javax.jms.InvalidClientIDException: Broker: broker - Client: MessagingBridge.EllipseServicesBridge already connected from tcp://10.11.112.121:55662
at org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:255)
at org.apache.activemq.broker.jmx.ManagedRegionBroker.addConnection(ManagedRegionBroker.java:231)
at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:97)
at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:97)
at org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:95)
at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:97)
at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:97)
at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:102)
at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:102)
at org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:817)
at org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:77)
at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:338)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:188)
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:300)
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:745)

Line 215: 12:44:43,532 INFO [stdout] (ActiveMQ Transport: tcp:///10.11.112.121:38607@61616) javax.jms.InvalidClientIDException: Broker: broker - Client: MessagingBridge.MibEventReplyBridge already connected from tcp://10.11.112.119:62691
Line 409: 12:44:58,203 INFO [stdout] (ActiveMQ Transport: tcp:///10.11.112.118:62976@61616) javax.jms.InvalidClientIDException: Broker: broker - Client: MessagingBridge.MibEventReplyBridge already connected from tcp://10.11.112.119:62691
Line 475: 12:45:16,528 INFO [stdout] (ActiveMQ Transport: tcp:///10.11.112.119:62889@61616) javax.jms.InvalidClientIDException: Broker: broker - Client: MessagingBridge.EllipseServicesBridge already connected from tcp://10.11.112.120:51902
Line 498: 12:45:18,298 INFO [stdout] (ActiveMQ Transport: tcp:///10.11.112.120:52045@61616) javax.jms.InvalidClientIDException: Broker: broker - Client: MessagingBridge.MibEventReplyBridge already connected from tcp://10.11.112.119:62691

 

 

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