activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tommy Lindgren (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQ-3605) NullPointerException in TransportConnection
Date Mon, 12 Dec 2011 20:35:30 GMT


Tommy Lindgren commented on AMQ-3605:

No NullPointerExceptions with 4.6-SNAPSHOT/trunk, that is correct.

According to the "Connections" admin web page (and netstat), the affected client is still
connected to AMQ. I assume all or most EOFExceptions, SocketExceptions and InactivityIOException
are from my fork/connect/subscribe/exit script.
> NullPointerException in TransportConnection
> -------------------------------------------
>                 Key: AMQ-3605
>                 URL:
>             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
>              Labels: stomp
>         Attachments: AMQ-3605-Patch.txt,,
> I'm running ActiveMQ 5.5.0 and clients using Net::Stomp 0.38_99 and I'm seeing infrequent
NullPointerExceptions in TransportConnection:
> {noformat}
> Exception in thread "ActiveMQ Connection Dispatcher: /" java.lang.NullPointerException
>         at
>         at$1.onCommand(
>         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
>         at
>         at
>         at org.apache.activemq.thread.DedicatedTaskRunner.runTask(
>         at org.apache.activemq.thread.DedicatedTaskRunner$
> {noformat}
> 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,
> {noformat}
> 326         if (context != null) {
> 327             if (context.isDontSendReponse()) {
> {noformat}
> 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