activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Mesnil (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-161) Graceful shutdown: add a timeout to stop Artemis
Date Wed, 22 Jun 2016 08:01:12 GMT


Jeff Mesnil commented on ARTEMIS-161:

The graceful-shutdown-timeout does not fit our requirements to gracefully shutdown Artemis.
It's a configuration parameter while we need to specify the timeout when the shutdown operation
is performed (depending on use case, the timeout value may vary widely).
Besides, there are use cases that are not covered yet by Artemis related to graceful shutdown
(in-flight request, possibily to resume work, etc.)

> Graceful shutdown: add a timeout to stop Artemis
> ------------------------------------------------
>                 Key: ARTEMIS-161
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.0.0
>            Reporter: Jeff Mesnil
>            Assignee: Justin Bertram
>             Fix For: 1.4.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
> 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

View raw message