You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2015/09/09 15:17:46 UTC
[jira] [Updated] (ARTEMIS-161) Graceful shutdown: add a timeout to
stop Artemis
[ https://issues.apache.org/jira/browse/ARTEMIS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
clebert suconic updated ARTEMIS-161:
------------------------------------
Fix Version/s: (was: 1.1.0)
1.2.0
> Graceful shutdown: add a timeout to stop Artemis
> ------------------------------------------------
>
> Key: ARTEMIS-161
> URL: https://issues.apache.org/jira/browse/ARTEMIS-161
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.0.0
> Reporter: Jeff Mesnil
> Assignee: Justin Bertram
> Fix For: 1.2.0
>
>
> We want to provide a graceful shutdown for Artemis to leave some time for JMS clients to finish their work before stopping the server.
> This is also covered by ARTEMIS-72 which deals with refusing new remote connections once the shutdown process is started (while keeping in-vm connections opened).
> This issue is about specifying a timeout when stopping the ActiveMQServer.
> It is possible to provide a general shutdown timeout in the server configuration but this is not suitable.
> A shutdown process is contextual: it may be a quick shutdown in case of emergency (with a timeout of some seconds) or a long timeout (several hours) in case of planned upgrade for example.
> This parameter should be specified when the admin starts the shutdown process and be passed to the ActiveMQServer (and its wrapping JMSServerManger) stop() method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)