You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by xbranko <xb...@netscape.net> on 2007/04/25 19:54:09 UTC

4.2 master-slave configuration exception

ActiveMQ: 4.2-20070328.130210-35
java 1.5.0_04

Master and slave configured as per instructions, and both come up. Both
receive messages from producer. When using the admin webapp on master to
look at the queue, the queue gets displayed, but the slave gets the NP
exception:
ERROR Service                        - Async error occurred:
java.lang.NullPointerException
java.lang.NullPointerException
        at
org.apache.activemq.broker.region.RegionBroker.processDispatchNotification(RegionBroker.java:543)
        at
org.apache.activemq.broker.BrokerFilter.processDispatchNotification(BrokerFilter.java:201)
        at
org.apache.activemq.broker.BrokerFilter.processDispatchNotification(BrokerFilter.java:201)
        at
org.apache.activemq.broker.BrokerFilter.processDispatchNotification(BrokerFilter.java:201)
        at
org.apache.activemq.broker.MutableBrokerFilter.processDispatchNotification(MutableBrokerFilter.java:209)
        at
org.apache.activemq.broker.TransportConnection.processMessageDispatchNotification(TransportConnection.java:498)
        at
org.apache.activemq.command.MessageDispatchNotification.visit(MessageDispatchNotification.java:76)
        at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:282)
        at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:188)
        at
org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:96)
        at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
        at
org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:224)
        at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:97)
        at
org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
        at
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)


During master and slave startup these two messages appear in respective logs
(I renamed the brokers to 'master' and 'slave' instead of default
'localhost'):
[in master log] WARN  BrokerRegistry                 - Broker localhost not
started so using master instead
[in slave log]    WARN  BrokerRegistry                 - Broker localhost
not started so using slave instead
If I rename both brokers back to localhost, the above messages do not show,
but the NPE is still happening.

Is it correct to use the admin webapp tool to look at the slave, while it is
in the slave mode?

Thanks,
Branko
-- 
View this message in context: http://www.nabble.com/4.2-master-slave-configuration-exception-tf3647044s2354.html#a10186093
Sent from the ActiveMQ - User mailing list archive at Nabble.com.