[
https://issues.apache.org/jira/browse/ACTIVEMQ6-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296831#comment-14296831
]
Jeff Mesnil commented on ACTIVEMQ6-52:
--------------------------------------
In the case of using ActiveMQ in an application server, we would also like to
distinguish between external acceptors (backed by Netty) and in-memory ones.
When the app server suspends its activity, it prevents new external connections
but should still allow the current existing ones to perform their works.
It should also not prevent new internal connections to be created.
>From an API point of view, that means we would be interested to prevent new
>connections from netty acceptors when the app server suspends its activity.
>But this should have no impact on existing external connection and any
>in-memory connections
> Graceful Shutdown
> -----------------
>
> Key: ACTIVEMQ6-52
> URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-52
> Project: Apache ActiveMQ 6
> Issue Type: Bug
> Reporter: clebert suconic
> Assignee: Justin Bertram
> Fix For: 6.0.0
>
>
> We should provide a way for the system to gracefully shutdown connections
> allowing them to finish their work before the server is going out.
> This could be done by issuing a close from Server to client on all the
> connections.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
