[jbossts-issues] [JBoss JIRA] (JBTM-3037) LRA context is not always removed if the LRA is ended

Tom Jenkinson (JIRA) issues at jboss.org
Thu Jul 5 04:59:00 EDT 2018

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

Tom Jenkinson commented on JBTM-3037:

I am not sure how this didn't link up with GitHub but the commit is here: https://github.com/jbosstm/narayana/commit/3c4b7c08f310eadb7cc87f9dfb1223c7b048a6f5

> LRA context is not always removed if the LRA is ended
> -----------------------------------------------------
>                 Key: JBTM-3037
>                 URL: https://issues.jboss.org/browse/JBTM-3037
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: LRA
>    Affects Versions: 5.8.2.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.next
> The following scenario leaves the LRA context still current:
> start an LRA
> call a service annotated with, for example,
> {code}
>  @LRA(value = LRA.Type.REQUIRED, cancelOn = {Response.Status.NOT_FOUND})
> {/code}
> If the invoked method returns the NOT_FOUND status then the LRA is automatically terminated. When the request returns to the client there should be no current LRA context active. The issue here is that the next request that the client makes may still have the old LRA still associated.

This message was sent by Atlassian JIRA

More information about the jbossts-issues mailing list