Broker log full of Failed to register queue messages

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Broker log full of Failed to register queue messages

Ishitori
Hi, I am using a cluster of 2 brokers connected via Duplex connector. Brokers version is 5.10.0, Windows Server 2012 R2, java = SE 1.7.0_51-b13.

Recently I found that both brokers log is full of the same messages:

Full text of warning:
2014-09-02 07:37:41,430 | WARN | Failed to register queue://<queue_name> | org.apache.activemq.network.MBeanBridgeDestination | ActiveMQ NIO Worker 8283
javax.management.InstanceAlreadyExistsException: org.apache.activemq:brokerName=AMQ_Broker_1,connector=networkConnectors,networkConnectorName=<same_queue_name-DuplexConnector,networkBridge=tcp_//<ip_and_port>,type=Broker,direction=inbound,destinationType=Queue,destinationName=<same_queue_name>
at com.sun.jmx.mbeanserver.Repository.addMBean(Unknown Source)[:1.7.0_51]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(Unknown Source)[:1.7.0_51]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(Unknown Source)[:1.7.0_51]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(Unknown Source)[:1.7.0_51]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(Unknown Source)[:1.7.0_51]
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(Unknown Source)[:1.7.0_51]
at org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)[activemq-broker-5.10.0.jar:5.10.0]
at org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)[activemq-broker-5.10.0.jar:5.10.0]
at org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:96)[activemq-broker-5.10.0.jar:5.10.0]
at org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115)[activemq-broker-5.10.0.jar:5.10.0]
at org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1672)[activemq-broker-5.10.0.jar:5.10.0]
at org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:643)[activemq-broker-5.10.0.jar:5.10.0]
at org.apache.activemq.network.DemandForwardingBridgeSupport$3.onCommand(DemandForwardingBridgeSupport.java:224)[activemq-broker-5.10.0.jar:5.10.0]
at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)[activemq-client-5.10.0.jar:5.10.0]
at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)[activemq-client-5.10.0.jar:5.10.0]
at org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)[activemq-client-5.10.0.jar:5.10.0]
at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:270)[activemq-client-5.10.0.jar:5.10.0]
at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)[activemq-client-5.10.0.jar:5.10.0]
at org.apache.activemq.transport.nio.NIOTransport.serviceRead(NIOTransport.java:138)[activemq-client-5.10.0.jar:5.10.0]
at org.apache.activemq.transport.nio.NIOTransport$1.onSelect(NIOTransport.java:69)[activemq-client-5.10.0.jar:5.10.0]
at org.apache.activemq.transport.nio.SelectorSelection.onSelect(SelectorSelection.java:94)[activemq-client-5.10.0.jar:5.10.0]
at org.apache.activemq.transport.nio.SelectorWorker$1.run(SelectorWorker.java:119)[activemq-client-5.10.0.jar:5.10.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)[:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)[:1.7.0_51]
at java.lang.Thread.run(Unknown Source)[:1.7.0_51]

What is that? There are a lot of messages like that in both brokers and I believe a new one is created as soon as a new message is sent to the broker.

Am I correct that there something wrong between brokers interactions, since 1 broker tells to another one to create a queue which already exists on the 2nd broker? What could cause that and how can I fix it?
Reply | Threaded
Open this post in threaded view
|

Re: Broker log full of Failed to register queue messages

Marcus A.
I have the same problem. Did you have any solution?
Reply | Threaded
Open this post in threaded view
|

Re: Broker log full of Failed to register queue messages

gurunath
Do you guys find any solution for this issue ?

Even I am having the same issue. No clue or any other symptoms in the logs.

Regards
Guru
@tallguru
Reply | Threaded
Open this post in threaded view
|

Re: Broker log full of Failed to register queue messages

Ishitori
Nope :( It still happens from time to time. Restart of the services helped us, so we do it from time to time.
Reply | Threaded
Open this post in threaded view
|

Re: Broker log full of Failed to register queue messages

Tim Bain
Gurunath, are you using NIO like Ishitori is?  Or is that an unrelated red
herring?

Ishitori, did you ever submit a JIRA bug report for this?  If you haven't,
please do, since it sounds like there's a bug here and without a JIRA entry
it's less likely to get investigated/fixed.

I looked at the code (
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.activemq/activemq-all/5.10.0/org/apache/activemq/network/MBeanBridgeDestination.java)
and it looks to me like we're attempting to create a new MBean in both
onInboundMessage() and onOutBoundMessage().  In both cases, we check for
non-existence before doing the work, but the check is on a different map in
each method (inboundDestinationViewMap and outboundDestinationViewMap,
respectively).  So we can only add one entry for inbound messages and one
for outbound ones, but that still seems like it would allow double
registration in the situation where we had both inbound and outbound
messages.  Am I looking at that right?

Tim

On Fri, May 22, 2015 at 12:05 PM, Ishitori <[hidden email]> wrote:

> Nope :( It still happens from time to time. Restart of the services helped
> us, so we do it from time to time.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-tp4685241p4696875.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>