October 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2939) JTS for not putting transaction to heuristic state during recovery for XAException.XAER_NOTA

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2939?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2939: ---------------------------------- Description: JTS moves transaction to heuristic state when participant during recovery returns {{XAExeption.XAER_NOTA}} error code. This is a bit pointless as this particular error code does not mean that there was some trouble with RM but that RM just already does not know about the transaction branch. For recovery it means that the branch was committed/rolled-back either before recovery started or in some previous recovery run (where probably something crashed). We can assumed the transaction was completed and ignore the {{XAER_NOTA}} (in case of recovery). This behaviour is already present in JTA. This came from EAP issue: JBEAP-13023 where you can find more on the reproducing. was: JTS moves transaction to heuristic state when participant during recovery returns {{XAExeption.XAER_NOTA}} error code. This is a bit pointless as this particular error code does not mean that there was some trouble with RM but that RM just already does not know about the transaction branch. For recovery it means that the branch was committed/rolled-back either before recovery started or in some previous recovery run (where probably something crashed). We can assumed the transaction was completed and ignore the {{XAER_NOTA}} (in case of recovery). This behaviour is already present in JTA. > JTS for not putting transaction to heuristic state during recovery for XAException.XAER_NOTA > -------------------------------------------------------------------------------------------- > > Key: JBTM-2939 > URL: https://issues.jboss.org/browse/JBTM-2939 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Affects Versions: 5.7.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > JTS moves transaction to heuristic state when participant during recovery returns {{XAExeption.XAER_NOTA}} error code. This is a bit pointless as this particular error code does not mean that there was some trouble with RM but that RM just already does not know about the transaction branch. For recovery it means that the branch was committed/rolled-back either before recovery started or in some previous recovery run (where probably something crashed). > We can assumed the transaction was completed and ignore the {{XAER_NOTA}} (in case of recovery). This behaviour is already present in JTA. > This came from EAP issue: JBEAP-13023 where you can find more on the reproducing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2939) JTS for not putting transaction to heuristic state during recovery for XAException.XAER_NOTA

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created JBTM-2939: ------------------------------------- Summary: JTS for not putting transaction to heuristic state during recovery for XAException.XAER_NOTA Key: JBTM-2939 URL: https://issues.jboss.org/browse/JBTM-2939 Project: JBoss Transaction Manager Issue Type: Enhancement Components: JTS Affects Versions: 5.7.0.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka JTS moves transaction to heuristic state when participant during recovery returns {{XAExeption.XAER_NOTA}} error code. This is a bit pointless as this particular error code does not mean that there was some trouble with RM but that RM just already does not know about the transaction branch. For recovery it means that the branch was committed/rolled-back either before recovery started or in some previous recovery run (where probably something crashed). We can assumed the transaction was completed and ignore the {{XAER_NOTA}} (in case of recovery). This behaviour is already present in JTA. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2938) LRA participant complete/compensate methods should use HTTP PUT

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2938: -------------------------------------- Summary: LRA participant complete/compensate methods should use HTTP PUT Key: JBTM-2938 URL: https://issues.jboss.org/browse/JBTM-2938 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.7.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.later LRA participant complete and compensate methods are currently called using an HTTP POST request. Since these methods should be idempotent they should respond to PUT since in a REST based system PUT is idempotent and POST is not. Both the implementation and the specification need changing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2935) Make LRA @Complete optional

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2935?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2935: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Make LRA @Complete optional > --------------------------- > > Key: JBTM-2935 > URL: https://issues.jboss.org/browse/JBTM-2935 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > LRA compensators currently require both @Complete and @Compensate annotations to be present. The @Complete should be optional. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2937) Do not recommend "X-" prefixed headers

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2937: -------------------------------------- Summary: Do not recommend "X-" prefixed headers Key: JBTM-2937 URL: https://issues.jboss.org/browse/JBTM-2937 Project: JBoss Transaction Manager Issue Type: Enhancement Components: LRA Affects Versions: 5.7.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next Quote from PR https://github.com/jbosstm/microprofile-sandbox/pull/3 raised by @nicolaferraro : {quote} A small change to the spec in order to use "Long-Running-Action" and "Short-Running-Action" headers instead of "X-lra" and "X-sra". "X-" prefixed headers should be deprecated by RFC-6648 and RFC-7231. They are not mandated by this spec, but they'll be used by microprofile rest services, so it's important for other technologies to use them if they want to build interoperable rest services. {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2936) JAX-RS response headers from an LRA @Nested method doesn't include the parent LRA id

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2936?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2936: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1222 > JAX-RS response headers from an LRA @Nested method doesn't include the parent LRA id > ------------------------------------------------------------------------------------ > > Key: JBTM-2936 > URL: https://issues.jboss.org/browse/JBTM-2936 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > When a JAX-RS resource method annotated with @Nested returns the response headers do not include the parent LRA id. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2936) JAX-RS response headers from an LRA @Nested method doesn't include the parent LRA id

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2936: -------------------------------------- Summary: JAX-RS response headers from an LRA @Nested method doesn't include the parent LRA id Key: JBTM-2936 URL: https://issues.jboss.org/browse/JBTM-2936 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.7.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next When a JAX-RS resource method annotated with @Nested returns the response headers do not include the parent LRA id. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2935) Make LRA @Complete optional

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2935?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1225 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Make LRA @Complete optional > --------------------------- > > Key: JBTM-2935 > URL: https://issues.jboss.org/browse/JBTM-2935 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > LRA compensators currently require both @Complete and @Compensate annotations to be present. The @Complete should be optional. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2935) Make LRA @Complete optional

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2935: -------------------------------------- Summary: Make LRA @Complete optional Key: JBTM-2935 URL: https://issues.jboss.org/browse/JBTM-2935 Project: JBoss Transaction Manager Issue Type: Enhancement Components: LRA Affects Versions: 5.7.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next LRA compensators currently require both @Complete and @Compensate annotations to be present. The @Complete should be optional. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2017