You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2010/12/22 16:51:00 UTC

[jira] Created: (AMQNET-298) NMS.ActiveMQ Transports don't properly close down when the dispose method is called.

NMS.ActiveMQ Transports don't properly close down when the dispose method is called.
------------------------------------------------------------------------------------

                 Key: AMQNET-298
                 URL: https://issues.apache.org/jira/browse/AMQNET-298
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: ActiveMQ
    Affects Versions: 1.4.1
            Reporter: Timothy Bish
            Assignee: Timothy Bish
             Fix For: 1.5.0


When calling Dispose() on a top level Transport in the chain of transports the chain isn't always properly closed leaving dangling resources running such as multiple InactivityMonitor transports.

* FailoverTransport dispose should call Stop in order to ensure its reconnect tasks and contained transports are all closed.
* TransportFilter Stop needs to call next.Stop() to propagate the Stop event.  
* The BackupTransport should properly dispose of its Transport when its marked as Disposed.



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

[jira] Resolved: (AMQNET-298) NMS.ActiveMQ Transports don't properly close down when the dispose method is called.

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQNET-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQNET-298.
---------------------------------

    Resolution: Fixed

Fixed in trunk

> NMS.ActiveMQ Transports don't properly close down when the dispose method is called.
> ------------------------------------------------------------------------------------
>
>                 Key: AMQNET-298
>                 URL: https://issues.apache.org/jira/browse/AMQNET-298
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ
>    Affects Versions: 1.4.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 1.5.0
>
>
> When calling Dispose() on a top level Transport in the chain of transports the chain isn't always properly closed leaving dangling resources running such as multiple InactivityMonitor transports.
> * FailoverTransport dispose should call Stop in order to ensure its reconnect tasks and contained transports are all closed.
> * TransportFilter Stop needs to call next.Stop() to propagate the Stop event.  
> * The BackupTransport should properly dispose of its Transport when its marked as Disposed.

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