[jboss-jira] [JBoss JIRA] (WFLY-1247) graceful shutdown
Brian Stansberry (JIRA)
issues at jboss.org
Mon Apr 7 15:26:14 EDT 2014
[ https://issues.jboss.org/browse/WFLY-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12959891#comment-12959891 ]
Brian Stansberry commented on WFLY-1247:
----------------------------------------
We currently have a model where only one management request that modifies state is allowed to execute at a time. From this it roughly follows that only one timeout value would be relevant at a time.[1]
Based on that it should be possible to store the current value in a service available to any services that gracefully stop, i.e. the "separate services" David mentions. When such a service needs to stop, it checks for the timeout value.
What needs to stop determines what services check the value. A full shutdown requires everything to stop; an undeploy requires some subset to stop.
[1] Roughly because a user could possibly do multiple ops in a batch with different values. Which we could just not support, or add some logic to track the max value set in a given context and provide that.
> graceful shutdown
> -----------------
>
> Key: WFLY-1247
> URL: https://issues.jboss.org/browse/WFLY-1247
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Emanuel Muckenhuber
> Assignee: Stuart Douglas
>
> We need to define a clear contract between these networking services and the services that use them in order to be able to perform a graceful shutdown of remote connectors.
--
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
More information about the jboss-jira
mailing list