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

[Tom Jenkinson (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094723#comment-13094723 ] 

Tom Jenkinson commented on WFLY-4937:
-------------------------------------

Sorry, I was unclear. I wasn't proposing to pause the individual transactions.

What I meant was:
1. When suspend is called
2. Allow existing remote transactions to complete
3. Do not allow new remote transactions to be created
4. Until resume is called (or server restarts)

Is that the intended behavior? I think it would be consistent with what you are proposing (so long as doOtherStuff is @RequiresNew - if it was @Requires as the TX is already existing we wouldn't actually reject those ones as the lookup of the transaction would succeed)

> 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: Michael Musgrove
>             Fix For: 11.0.0.Alpha1
>
>
> 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)