You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Markus Karolus (JIRA)" <ji...@apache.org> on 2012/12/05 22:41:57 UTC

[jira] [Created] (AMQNET-401) NullReferenceException from Apache.NMS.ActiveMQ.Transport.InactivityMonitor

Markus Karolus created AMQNET-401:
-------------------------------------

             Summary: NullReferenceException from Apache.NMS.ActiveMQ.Transport.InactivityMonitor 
                 Key: AMQNET-401
                 URL: https://issues.apache.org/jira/browse/AMQNET-401
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: NMS
    Affects Versions: 1.5.6
         Environment: Windows Server 2008 R2, .Net 4.0
            Reporter: Markus Karolus
            Assignee: Jim Gomes
            Priority: Critical


It's the same problem which is descibed in,
https://issues.apache.org/jira/browse/AMQNET-339
in the current version (1.5.6) the real problem is not fixed, so I created this new issue.

Today we had an crash on one of our enviromental boxes:
Directly after a failover we got the following message from the InactivityMonitor "InactivityMonitor[{0}]: Timer Task didn't shutdown properly."
Afterwards the whole process shuts down after an UnhandledException handling. In the WriteCheck method a NullReferenceException was thrown.

It seems that during the StopMonitorThreads the timer connectionCheckTimer couldn't stop correctly and ansyncTasks exists. Directly after that the asyncTasks will be set to null -> In the currenr running WriteCheck a NullReferenceException occures. 

(This problem was already commented in AMQNET-339 as last comment from Matthew Good)


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira