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 2012/11/07 15:37:12 UTC

[jira] [Resolved] (AMQ-4019) Make better use of commons-pool in activemq-pool

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

Timothy Bish resolved AMQ-4019.
-------------------------------

    Resolution: Fixed

fixed now in trunk.
                
> Make better use of commons-pool in activemq-pool
> ------------------------------------------------
>
>                 Key: AMQ-4019
>                 URL: https://issues.apache.org/jira/browse/AMQ-4019
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: activemq-pool
>    Affects Versions: 5.6.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 5.7.0
>
>         Attachments: AMQ4019Patch.txt, AMQ4019Patch.txt, AMQ4019Patch.txt
>
>
> Currently activemq-pool uses only a tiny portion of the functionality that's available in commons-pool opting instead to reinvent a lot of things that now exists there such as keyed object pools.  We can refactor the current codebase to better use common-pool.  This allows for easily adding features like enabling async checks for Connections that have idled out and removing them from the pool as well as adding more diagnostic methods to our API and using a well tested pooling backend instead of our own custom code.  

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