activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tommy Lindgren (Created) (JIRA)" <>
Subject [jira] [Created] (AMQ-3605) NullPointerException in TransportConnection
Date Wed, 23 Nov 2011 12:15:39 GMT
NullPointerException in TransportConnection

                 Key: AMQ-3605
             Project: ActiveMQ
          Issue Type: Bug
          Components: Transport
    Affects Versions: 5.5.0
         Environment: SLES 11 SP1
java version "1.6.0_23"
perl 5.10.0 + Net::Stomp 0.38_99
            Reporter: Tommy Lindgren
            Priority: Critical

I'm running ActiveMQ 5.5.0 and clients using Net::Stomp 0.38_99 and I'm seeing infrequent
NullPointerExceptions in TransportConnection:

Exception in thread "ActiveMQ Connection Dispatcher: /" java.lang.NullPointerException
        at org.apache.activemq.transport.TransportFilter.onCommand(
        at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(
        at org.apache.activemq.transport.stomp.StompSubscription.onMessageDispatch(
        at org.apache.activemq.transport.stomp.ProtocolConverter.onActiveMQCommand(
        at org.apache.activemq.transport.stomp.StompTransportFilter.oneway(
        at org.apache.activemq.transport.MutexTransport.oneway(
        at org.apache.activemq.thread.DedicatedTaskRunner.runTask(
        at org.apache.activemq.thread.DedicatedTaskRunner$

This seems to happen 1-2 times per month or so but the result is dire: new messages aren't
delivered to the affected client (you can see the number of pending messages increasing in
the admin web interface) until the client or ActiveMQ is restarted.

Relevant code snippet from,

326         if (context != null) {
327             if (context.isDontSendReponse()) {

implies that we are dealing with a race condition. I'm not familiar with the ActiveMQ code
base but it looks like it grabs a lock (serviceLock) before entering that function, so not
sure what's going on.

Since there's no timestamp associated with the stack trace I'm not completly sure what's going
on on the client side. I've tried to reproduce it by writing a small script that uses Net::Stomp
in a similar way to my real clients, but no luck so far.

No idea if it's relevant, but my affected clients have been both consuming and producing,
and sending/receiving on both topics and queues.

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