[jboss-jira] [JBoss JIRA] (WFLY-4937) Implement graceful shutdown for transactions

[Gytis Trikleris (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gytis Trikleris updated WFLY-4937:
----------------------------------
    Description: 
This feature will allow EAP supported transaction services to react to suspend and resume requests. The supported services are JTA, JTS, WS-AT, and WS-BA.
After suspend, all the services remain functional. All external requests bound to the existing transactions are allowed in. All external requests requiring new transaction are blocked. All remote transaction management requests, except begin, are allowed in.
After resume, all requests are allowed in.
After suspend timeout, all services must shutdown.

  was:
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





> Implement graceful shutdown for transactions
> --------------------------------------------
>
>                 Key: WFLY-4937
>                 URL: https://issues.jboss.org/browse/WFLY-4937
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Transactions
>    Affects Versions: 10.0.0.Alpha5
>            Reporter: Michael Musgrove
>            Assignee: Gytis Trikleris
>             Fix For: 11.0.0.CR1
>
>
> This feature will allow EAP supported transaction services to react to suspend and resume requests. The supported services are JTA, JTS, WS-AT, and WS-BA.
> After suspend, all the services remain functional. All external requests bound to the existing transactions are allowed in. All external requests requiring new transaction are blocked. All remote transaction management requests, except begin, are allowed in.
> After resume, all requests are allowed in.
> After suspend timeout, all services must shutdown.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)