[jbossts-issues] [JBoss JIRA] (JBTM-3066) Starting a nested LRA via the client API leaves the parent as the current context

[Michael Musgrove (Jira)]

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

Issue was automatically transitioned when Michael Musgrove created pull request #1372 in GitHub
-----------------------------------------------------------------------------------------------
    Status: Pull Request Sent  (was: Open)


> Starting a nested LRA via the client API leaves the parent as the current context
> ---------------------------------------------------------------------------------
>
>                 Key: JBTM-3066
>                 URL: https://issues.jboss.org/browse/JBTM-3066
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: LRA
>    Affects Versions: 5.9.0.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Major
>             Fix For: 5.next
>
>
> If an LRA is associated with a thread and that thread then starts a new LRA then the new one is nested under the first. When using the LRAClient API to start the child LRA the resulting context is left as the parent. This is wrong since the thread should now operate in the context of the nested LRA.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)