A-MQ Returns javax.management.InstanceAlreadyExistsException
Issue
- A network of brokers is configured to use Duplex connections, but when a message is sent to an existing queue a
javax.management.InstanceAlreadyExistsExceptionwarning message is logged.
Broker Configuration Details:
<networkConnectors>
<networkConnector
name="duplexConnection"
userName="userName"
password="password"
uri="static://(tcp://localhost:port)"
duplex="true"
networkTTL="3" />
</networkConnectors>
Warning Message Details:
javax.management.InstanceAlreadyExistsException: org.apache.activemq:brokerName=amqBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//localhost_port,type=Broker,direction=inbound,destinationType=Queue,destinationName=Example
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
- By moving the installation directory of Fuse/A-MQ to a new directory and starting the server a
javax.management.InstanceAlreadyExistsExceptionerror message is logged.
Environment
-
Red Hat JBoss A-MQ
- Version: 6.2.1
-
Red Hat JBoss Fuse
- Version: 6.2.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
