activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank Gynnild (Created) (JIRA)" <>
Subject [jira] [Created] (AMQNET-356) Inactivity monitor (or another background task) cause a NullPointerException in ActiveMQ
Date Thu, 24 Nov 2011 19:50:39 GMT
Inactivity monitor (or another background task) cause a NullPointerException in ActiveMQ

                 Key: AMQNET-356
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: NMS
    Affects Versions: 1.5.2, 1.5.3
         Environment: Tested with both Active MQ 5.5, 5.6
and ActiveMQ.Net 1.5.2 and 1.5.3.

Broker URI: 
            Reporter: Frank Gynnild
            Assignee: Jim Gomes
            Priority: Critical

We're running various automatic unit tests that ran fine for ActiveMQ.NMS 1.5.1, but that
always fail
at the same spot when we test with the new 1.5.2 (or latest 1.5.3). Strangely, it fails between
tests, but it didn't used to do that before. Running these two tests alone doesn't provoke
the situation
so its been hard to isolate it. Since it is consistent, I thought it was best to create an
issue here, maybe you have some hints on what's going on. I think it's a bug though, because
we're using the failover protocol, yet the connection exception get raised through this handler:
connection.ExceptionListener += ConnectionExceptionListener;
When using failover, I don't think we ever should see the exception listener being called,
Only got this information so it's not much:
Type: Apache.NMS.NMSConnectionException. Message: Exception of type 'Apache.NMS.NMSConnectionException'
was thrown.

*Before* this happens, we also see this in the ActiveMQ broker:

2011-11-23 09:47:18,458 | WARN  | Async error occurred: java.lang.NullPointerException |
| ActiveMQ Transport: tcp:///
	at org.apache.activemq.command.MessageAck.visit(
	at org.apache.activemq.transport.TransportFilter.onCommand(
	at org.apache.activemq.transport.WireFormatNegotiator.onCommand(
	at org.apache.activemq.transport.InactivityMonitor.onCommand(
	at org.apache.activemq.transport.TransportSupport.doConsume(
	at org.apache.activemq.transport.tcp.TcpTransport.doRun(
	at Source)

Thanks for any ideas on this. I'll be more than happy to test any code, since it can be produced
every time
with the 1.5.2 release.

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