[
https://issues.apache.org/jira/browse/ACTIVEMQ6-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296950#comment-14296950
]
clebert suconic commented on ACTIVEMQ6-72:
------------------------------------------
>From Jeff Mesnil at ACTIVEMQ-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
> Increment graceful shutdown scenarios and add more tests
> --------------------------------------------------------
>
> Key: ACTIVEMQ6-72
> URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-72
> Project: Apache ActiveMQ 6
> Issue Type: Task
> Affects Versions: 6.0.0
> Reporter: Justin Bertram
> Fix For: 6.1.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
