[
https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on WFLY-4937:
----------------------------------------
OK that makes sense, thanks. I assume that:
- there is no benefit in handling the suspended event by not reporting done if there are
still outstanding transactions;
- there is no concept of ordering of shutdown callbacks according to the subsystem
dependency graph.
If my assumptions are correct I will reject the JIRA
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)