Hmm, looking more closely - it appears those MBeans are client connections.
Perhaps there's a fast reconnect of a client such that the new connection is
registering before the old is removed?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failed-to-register-
Could there be two brokers with the same name in that JVM?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failed-to-register-MBean-tp4690522p4690543.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
wrote:
> We are using activemq 5.10.0 in our product env. Today we found some warn
> logs below. What's reason?
>
>
> Thanks for any and all pointers!
>
>
> 2015-01-28 14:05:50,837 | WARN | Failed to register MBean
> org.apache.activemq:type=Broker,brokerN
We are using activemq 5.10.0 in our product env. Today we found some warn logs
below. What's reason?
Thanks for any and all pointers!
2015-01-28 14:05:50,837 | WARN | Failed to register MBean
org.apache.activemq:type=Broker,brokerName=ROOTNET_AMQ_5.10.0,connector=clientConne
I have a java producer and a remote consumer exchanging messages via HTTP.
There is single a broker managing request and response queues. JMX is
enabled.
With ActiveMQ 4.1.1, the broker reports the following:
WARN ManagedTransportConnection - Failed to register MBean:
org.apache.acti
