activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Koerner (JIRA)" <>
Subject [jira] [Created] (AMQ-3887) Occasional Null Pointer Exception during NetworkConnector connection
Date Mon, 18 Jun 2012 16:03:45 GMT
Ron Koerner created AMQ-3887:

             Summary: Occasional Null Pointer Exception during NetworkConnector connection
                 Key: AMQ-3887
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.6.0
         Environment: SLES 10
            Reporter: Ron Koerner

While starting a duplex NetworkConnector an NPE can be observed on the receiving side.

2012-06-18 17:34:24,571 INFO  .DemandForwardingBridgeSupport - Network connection between
vm://proxy-cbpi001#8 and tcp:///169.254.
0.5:59412(cbox-56BU101117) has been established. [StartLocalBridge: localBroker=vm://proxy-cbpi001#8]
2012-06-18 17:34:24,577 WARN  .DemandForwardingBridgeSupport - Caught an exception processing
local command [BrokerService[proxy-c
bpi001] Task-19]
java.lang.NullPointerException: null
        at org.apache.activemq.transport.ResponseCorrelator.onCommand(
        at org.apache.activemq.transport.MutexTransport.onCommand(
        at org.apache.activemq.transport.vm.VMTransport.doDispatch( [activemq-core-5.6.0.jar:5.6.0]
        at org.apache.activemq.transport.vm.VMTransport.dispatch( [activemq-core-5.6.0.jar:5.6.0]
        at org.apache.activemq.transport.vm.VMTransport.oneway( [activemq-core-5.6.0.jar:5.6.0]
        at org.apache.activemq.transport.MutexTransport.oneway( [activemq-core-5.6.0.jar:5.6.0]
        at org.apache.activemq.transport.ResponseCorrelator.oneway(
        at org.apache.activemq.thread.PooledTaskRunner.runTask(
        at org.apache.activemq.thread.PooledTaskRunner$ [activemq-core-5.6.0.jar:5.6.0]
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [na:1.6.0_20]
        at java.util.concurrent.ThreadPoolExecutor$ Source) [na:1.6.0_20]
        at Source) [na:1.6.0_20]

The other broker will eventually connect, but with about a hundred of connecting brokers this
occurs too often to ignore.

As this seems to be a race condition it is quite difficult to reproduce reliably. I assume
producerInfo is accessed in configureMessage before it is initialized in startRemoteBridge.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message