activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher G. Stach II" <...@ldsys.net>
Subject Re: Problem with blocking of the brokers in ActiveMQ 4.0
Date Wed, 31 May 2006 19:26:04 GMT
Igor Bogicevic wrote:
> Hi,
> 
> I have a cluster of 2 activemq brokers with static network connector
> between them and after a while and about 300-400k of the messages it
> often happens that one of the brokers block as well as whole cluster
> and it stops receiving messages, and I have to restart both cluster
> nodes. The last what I can see in the log is this, but I am not sure
> that it's related with the problem itself:
> 
> ERROR ManagedRegionBroker            - Failed to register subscription
> TopicSubscription: consumer=ID:box13.lo-37035-1148956198434-0:0:-1:1,
> destinations=0, dispatched=0, delivered=0, matched=0, discarded=0
> javax.management.InstanceAlreadyExistsException:
> org.apache.activemq:BrokerName=localhost,Type=Subscription,active=true,name=ID_box13.lo-37035-1148956198434-0_0_-1_1
> 
>        at
> com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:452)
> 
>        at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1410)
> 
>        at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:936)
> 
>        at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:337)
> 
>        at
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:497)
> 
>        at
> org.apache.activemq.broker.jmx.ManagedRegionBroker.registerSubscription(ManagedRegionBroker.java:260)
> 
>        at
> org.apache.activemq.broker.jmx.ManagedRegionBroker.registerSubscription(ManagedRegionBroker.java:180)
> 
>        at
> org.apache.activemq.broker.jmx.ManagedTopicRegion.createSubscription(ManagedTopicRegion.java:44)
> 
>        at
> org.apache.activemq.broker.region.AbstractRegion.addConsumer(AbstractRegion.java:145)
> 
>        at
> org.apache.activemq.broker.region.TopicRegion.addConsumer(TopicRegion.java:113)
> 
>        at
> org.apache.activemq.broker.region.RegionBroker.addConsumer(RegionBroker.java:296)
> 
>        at
> org.apache.activemq.broker.BrokerFilter.addConsumer(BrokerFilter.java:73)
>        at
> org.apache.activemq.advisory.AdvisoryBroker.addConsumer(AdvisoryBroker.java:77)
> 
>        at
> org.apache.activemq.broker.BrokerFilter.addConsumer(BrokerFilter.java:73)
>        at
> org.apache.activemq.broker.MutableBrokerFilter.addConsumer(MutableBrokerFilter.java:86)
> 
>        at
> org.apache.activemq.broker.AbstractConnection.processAddConsumer(AbstractConnection.java:427)
> 
>        at
> org.apache.activemq.command.ConsumerInfo.visit(ConsumerInfo.java:295)
>        at
> org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
> 
>        at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
> 
>        at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
> 
>        at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
> 
>        at
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:114)
> 
>        at
> org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
> 
>        at
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:87)
> 
>        at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:143)
>        at java.lang.Thread.run(Thread.java:595)
> 
> I am using version 4.0 of ActiveMQ with J2SE 1.5_06. Does anyone has
> experience with this, or knows what could be a problem?
> 
> Thanks,
> Igor

That's just a side effect of the actual problem.  That exception happens
when you register an MBean with a name that has already been registered.
 I assume that one of your beans is restarting (or being restarted by
something/someone else) and registering itself with its original name.
As for the root cause, that being the broker hanging, I have no idea.

-- 
Christopher G. Stach II

Mime
View raw message