activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Resolved) (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Resolved] (AMQNET-349) Add new method to IConnection to purge locally created temp destinations
Date Tue, 15 Nov 2011 20:34:51 GMT

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

Timothy Bish resolved AMQNET-349.
---------------------------------

    Resolution: Fixed
      Assignee: Timothy Bish  (was: Jim Gomes)

Change applied in trunk.
                
> Add new method to IConnection to purge locally created temp destinations
> ------------------------------------------------------------------------
>
>                 Key: AMQNET-349
>                 URL: https://issues.apache.org/jira/browse/AMQNET-349
>             Project: ActiveMQ .Net
>          Issue Type: New Feature
>          Components: ActiveMQ, NMS
>    Affects Versions: 1.5.0, 1.5.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> For Connection instances that are created and used over a long period of time or used
in a Cached manner the locally allocated temp destinations can build up over time if not manually
deleted by the user.  If a pooling scenario it would be nice if the pool could purge the connection's
temp destinations before placing the Connection back in the free list.  
> Suggest adding a method such as:
> {noformat}
> void CleanupTempDestinations();
> {noformat}
> Or something similar to the IConnection interface to make this usable across NMS Providers.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message