[jira] [Resolved] (AMQNET-402) Application crashes due to unhandled exception from NMS API

["Timothy Bish (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQNET-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQNET-402.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.0
                   1.5.7
         Assignee: Timothy Bish  (was: Jim Gomes)

Added additional logic to protect against this error. 
                
> Application crashes due to unhandled exception from NMS API
> -----------------------------------------------------------
>
>                 Key: AMQNET-402
>                 URL: https://issues.apache.org/jira/browse/AMQNET-402
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: NMS
>    Affects Versions: 1.5.5
>         Environment: ActiveMQ apache-activemq-5.5.0
> Apache.NMS.ActiveMQ v1.5.5
> Java 1.6.0.27
> Operating System: Windows 2008 Server
>            Reporter: Oswin D
>            Assignee: Timothy Bish
>             Fix For: 1.5.7, 1.6.0
>
>
> The application crashes due to an unhandled exception from NMS API. The "NullReferenceException" from Apache.NMS.ActiveMQ.Transport.InactivityMonitor.WriteCheck() is logged in event viewer.
> With reference to https://issues.apache.org/jira/browse/AMQNET-339, already null check is done for asyncWriteTask in WriteCheck(). But still with that fix, we got the unhandled null reference exception. After checking null for asyncTasks before calling "this.asyncTasks.Wakeup();", our issue was fixed and we didnot get any further exception from WriteCheck().

--
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