activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Karolus (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Commented] (AMQNET-401) NullReferenceException from Apache.NMS.ActiveMQ.Transport.InactivityMonitor
Date Fri, 07 Dec 2012 07:17:21 GMT

    [ https://issues.apache.org/jira/browse/AMQNET-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526188#comment-13526188
] 

Markus Karolus commented on AMQNET-401:
---------------------------------------

The stack trace:

Exception='System.NullReferenceException: Object reference not set to an instance of an object.
   at Apache.NMS.ActiveMQ.Transport.InactivityMonitor.WriteCheck()
   at Apache.NMS.ActiveMQ.Transport.InactivityMonitor.CheckConnection(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode
code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback
callback, Object state, Boolean ignoreSyncCtx)
   at System.Threading._TimerCallback.PerformTimerCallback(Object state)'."	
                
> 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

Mime
View raw message