[
https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin....
]
David Lloyd edited comment on WFLY-4937 at 7/16/15 9:56 AM:
------------------------------------------------------------
Are you certain that this is the right behavior? If we disallow new transactions, then
existing EJB sessions (for example) might fail to be completed.
Since the transaction manager is not considered an "entry point" in terms of
graceful shutdown, it should not respond to a graceful shutdown other than perhaps
registering outstanding transactions with the shutdown manager.
was (Author: dmlloyd):
Are you certain that this is the right behavior? If we disallow new transactions, then
existing EJB sessions (for example) might fail to be completed.
Since the transaction manager is not considered an "entry point" in terms of
graceful shutdown, it should not respond to a graceful shutdown other than perhaps
registering outstanding requests with the shutdown manager.
Implement graceful shutdown for transactions
--------------------------------------------
Key: WFLY-4937
URL:
https://issues.jboss.org/browse/WFLY-4937
Project: WildFly
Issue Type: Sub-task
Components: Transactions
Affects Versions: 10.0.0.Alpha5
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 10.0.0.Alpha6
We will handle suspend for JTA and JTS by disallowing new transactions and then block the
suspend thread until the count of active transactions drops to zero. We will also suspend
the recovery manager.
We will *not* do graceful shutdown for the optional XTS subsystem. For example an
incoming XTS request for an existing transaction will be blocked.
Question: should we
- raise a new JIRA for this XTS case;
- document the deficiency and see if there are complaints;
- document the deficiency and fix it in a subsequent release
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)