[
https://issues.apache.org/jira/browse/AMQ-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449584#comment-13449584
]
Claus Ibsen commented on AMQ-4026:
----------------------------------
Working on the remainder. The close method of ActiveMQConnection may shutdown
its own thread pool from the same worker thread. That is a bit odd, but the old
logic just shutdown the thread pool to avoid accepting new tasks. So we will
introduce a quickShutdown method to use in these cases.
> Refactor logic to shutdown thread pools using a single API to ensure better
> shutdown and offer logging et all
> -------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-4026
> URL: https://issues.apache.org/jira/browse/AMQ-4026
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 5.7.0
>
>
> In Apache Camel we have a centralized API for thread pools. This allows us to
> track this in Camel, and ensure thread pools is enlisted in JMX, and also
> unregistered again. As well having logs when thread pools is created /
> shutdown etc. Also better logic for shutdown graceful and then fallback to be
> aggressive etc. And to add a thread factory, that offers a naming pattern
> style, so end users can customize thread naming etc.
> In activemq-core, there is pieces of logic for that. We should tidy this up,
> and especially ensure shutdown is happening consistent and more graceful, etc.
> This can help make it possible to do as Camel to also enlist thread pools in
> JMX.
--
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
