[AMQNET-401] NullReferenceException from Apache.NMS.ActiveMQ.Transport.InactivityMonitor

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 1.5.6
• Fix Version/s: 1.6.0
• Component/s: NMS

Environment

Windows Server 2008 R2, .Net 4.0

• Assignee: Timothy A. Bish
• Reporter: Markus Karolus
• Created: 05/Dec/12 21:40
• Updated: 18/Jan/13 21:45
• Resolved: 18/Jan/13 21:45

Description

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[x]: 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)

Issue Links

• is duplicated by: AMQNET-402 Application crashes due to unhandled exception from NMS API