activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Resolved] (AMQNET-423) The application crashes due to an unhandled exception from NMS API.
Date Fri, 15 Mar 2013 18:34:14 GMT

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

Jim Gomes resolved AMQNET-423.
------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.7

This check has been added to the 1.5.x branch and the trunk version.
                
> The application crashes due to an unhandled exception from NMS API.
> -------------------------------------------------------------------
>
>                 Key: AMQNET-423
>                 URL: https://issues.apache.org/jira/browse/AMQNET-423
>             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: Jim Gomes
>             Fix For: 1.5.7
>
>
> The application crashes due to an unhandled exception from NMS API. The "NullReferenceException"
from Apache.NMS.ActiveMQ.Transport.InactivityMonitor.ReadCheck() is logged in event viewer.
> The issue was fixed after adding null check for "asyncTasks" in InactivityMonitor.cs/ReadCheck()
before calling "this.asyncTasks.Wakeup();"

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