activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <jira+amq...@apache.org>
Subject [jira] Resolved: (AMQNET-312) Resource leak in NMS.Stomp Inactivity Monitor
Date Wed, 26 Jan 2011 20:50:44 GMT

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

Timothy Bish resolved AMQNET-312.
---------------------------------

    Resolution: Fixed

Fixed in trunk

> Resource leak in NMS.Stomp Inactivity Monitor
> ---------------------------------------------
>
>                 Key: AMQNET-312
>                 URL: https://issues.apache.org/jira/browse/AMQNET-312
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: Stomp
>    Affects Versions: 1.5.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 1.5.1
>
>
> Due to a race condition in the NMS.Stomp InactivityMonitor the object can leak Timer
instances that perform read and write checks.  The Dispose method needs to be synchronized
on the object monitor lock.  This change requires that the Connection class OnException fire
off the task of notifying any registered listeners and cleaning up resources to a separate
thread so the OnException call can complete and not initiate a DeadLock on the transport Dispose
call.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message