[
https://issues.jboss.org/browse/WFLY-1247?page=com.atlassian.jira.plugin....
]
David Lloyd commented on WFLY-1247:
-----------------------------------
If we're going to do deployment-level graceful shutdown, then we have to have a clear
rule which establishes when a deployment is no longer being used. I think this might not
always be possible to determine though; imagine the following scenarios:
* A servlet in a WAR references stateless EJBs in an EJB JAR; the EJB JAR is requested to
be shut down gracefully
* A servlet in a WAR references two stateless EJBs in two EJB JARs, which in turn
reference one another; one EJB JAR is requested to be shut down gracefully
In both of these cases, the dependents have to be considered in the shutdown decision;
thus neither EJB JAR can be shut down until/unless the WAR is shut down.
Consider this scenario:
* A stateful EJB in JAR A references, and is referenced by, a stateful EJB in JAR B
In this case, neither JAR can be shut down until/unless they both are.
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