September 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3061) CMR recovery wrongly handles commit and rollback

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/JBTM-3061?page=com.atlassian.jira.plugin.... ] Jiri Ondrusek reassigned JBTM-3061: ----------------------------------- Assignee: Jiri Ondrusek (was: Ondra Chaloupka) > CMR recovery wrongly handles commit and rollback > ------------------------------------------------- > > Key: JBTM-3061 > URL: https://issues.jboss.org/browse/JBTM-3061 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.5.32.Final > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > The recovery of CMR works wrongly. > For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. > # cmr resource prepare (no real action on the local transction) > # xa resource prepare (prepared in real as XA) > # cmr resource commit (commiting the local transaction) > # JVM crash > # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. > This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. > This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3061) CMR recovery wrongly handles commit and rollback

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/JBTM-3061?page=com.atlassian.jira.plugin.... ] Jiri Ondrusek updated JBTM-3061: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1366 (was: https://github.com/jbosstm/narayana/pull/1343) > CMR recovery wrongly handles commit and rollback > ------------------------------------------------- > > Key: JBTM-3061 > URL: https://issues.jboss.org/browse/JBTM-3061 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.5.32.Final > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > The recovery of CMR works wrongly. > For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. > # cmr resource prepare (no real action on the local transction) > # xa resource prepare (prepared in real as XA) > # cmr resource commit (commiting the local transaction) > # JVM crash > # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. > This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. > This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3061) CMR recovery wrongly handles commit and rollback

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/JBTM-3061?page=com.atlassian.jira.plugin.... ] Jiri Ondrusek updated JBTM-3061: -------------------------------- Fix Version/s: (was: 5.9.0.Final) Affects Version/s: 5.5.32.Final (was: 5.8.1.Final) > CMR recovery wrongly handles commit and rollback > ------------------------------------------------- > > Key: JBTM-3061 > URL: https://issues.jboss.org/browse/JBTM-3061 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.5.32.Final > Reporter: Jiri Ondrusek > Assignee: Ondra Chaloupka > > The recovery of CMR works wrongly. > For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. > # cmr resource prepare (no real action on the local transction) > # xa resource prepare (prepared in real as XA) > # cmr resource commit (commiting the local transaction) > # JVM crash > # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. > This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. > This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3061) CMR recovery wrongly handles commit and rollback

by Jiri Ondrusek (JIRA)

Jiri Ondrusek created JBTM-3061: ----------------------------------- Summary: CMR recovery wrongly handles commit and rollback Key: JBTM-3061 URL: https://issues.jboss.org/browse/JBTM-3061 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Affects Versions: 5.8.1.Final Reporter: Jiri Ondrusek Assignee: Ondra Chaloupka Fix For: 5.9.0.Final The recovery of CMR works wrongly. For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. # cmr resource prepare (no real action on the local transction) # xa resource prepare (prepared in real as XA) # cmr resource commit (commiting the local transaction) # JVM crash # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3060) Enhance quickstart readme with summary of all quickstarts while sorting them into categories

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-3060?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-3060: --------------------------------------- It seems there is a bit more work on this. Some quickstarts do not work with WildFly at all. There is need be done maintanance. > Enhance quickstart readme with summary of all quickstarts while sorting them into categories > -------------------------------------------------------------------------------------------- > > Key: JBTM-3060 > URL: https://issues.jboss.org/browse/JBTM-3060 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > The current README of the quickstart repository https://github.com/jbosstm/quickstart/blob/5.9.0.Final/README.md is a bit modest. Any stranger should get information about the overall structure of the repo while guiding him to find the quickstart he needs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3060) Enhance quickstart readme with summary of all quickstarts while sorting them into categories

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created JBTM-3060: ------------------------------------- Summary: Enhance quickstart readme with summary of all quickstarts while sorting them into categories Key: JBTM-3060 URL: https://issues.jboss.org/browse/JBTM-3060 Project: JBoss Transaction Manager Issue Type: Enhancement Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Priority: Minor The current README of the quickstart repository https://github.com/jbosstm/quickstart/blob/5.9.0.Final/README.md is a bit modest. Any stranger should get information about the overall structure of the repo while guiding him to find the quickstart he needs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3059) Move the JAX-RS specific parts of the LRA API into a separate API

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-3059: -------------------------------------- Summary: Move the JAX-RS specific parts of the LRA API into a separate API Key: JBTM-3059 URL: https://issues.jboss.org/browse/JBTM-3059 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.9.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next To ensure that the LRA APIs have broader applicability the JAX-RS specific aspects of the API need to be pulled out into a separate section. This change will mean it is possible to provide implementations of the API using non JAX-RS transports (such as gRPC etc). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3058) Add STM tests that verify nested transactions are closed

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3058?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3058: ----------------------------------- Description: STM implements "Closed Nested Transactions" as opposed to Flattened or Open. We need a test which demonstrates that nested transactions follow the closed model. Furthermore, STM implementations can differ in how transactional code and non-transactional code are isolated from each other (with respect to visibility of updates during a transaction). Add a test that verifies that we use the "Weak Isolation" model. Details of the expected behaviour is covered in the Sept 2018 jbossts blog entitled "[Tips on how to evaluate STM implementations|http://example.com|https://jbossts.blogspot.com/2018/09/t...]" was: STM implements "Closed Nested Transactions" as opposed to Flattened or Open. We need a test which demonstrates that nested transactions are closed. STM implementations can differ in how transactional code and non-transactional code are isolated from each other (with respect to visibility of updates during a transaction). Add a test that verifies that we use the "Weak Isolation" model. Details of the expected behaviour is covered in the Sept 2018 jbossts blog entitled "Tips on how to evaluate STM implementations" > Add STM tests that verify nested transactions are closed > -------------------------------------------------------- > > Key: JBTM-3058 > URL: https://issues.jboss.org/browse/JBTM-3058 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > STM implements "Closed Nested Transactions" as opposed to Flattened or Open. We need a test which demonstrates that nested transactions follow the closed model. > Furthermore, STM implementations can differ in how transactional code and non-transactional code are isolated from each other (with respect to visibility of updates during a transaction). Add a test that verifies that we use the "Weak Isolation" model. > Details of the expected behaviour is covered in the Sept 2018 jbossts blog entitled "[Tips on how to evaluate STM implementations|http://example.com|https://jbossts.blogspot.com/2018/09/t...]" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2478) Use Flame Graph tool

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2478?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2478: -------------------------------- Issue Type: Task (was: Enhancement) > Use Flame Graph tool > -------------------- > > Key: JBTM-2478 > URL: https://issues.jboss.org/browse/JBTM-2478 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Priority: Optional > > Tools and instructions are at: > https://github.com/jesperpedersen/perfjava/ <-- CPU sampling > https://github.com/jesperpedersen/javamemflame <-- Memory allocation tracking > Both use Agent_OnLoad/Agent_OnUnload, so better for smaller tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2788) TestGroup_txcore is missing from the documentation

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2788?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2788: -------------------------------- Issue Type: Bug (was: Enhancement) > TestGroup_txcore is missing from the documentation > -------------------------------------------------- > > Key: JBTM-2788 > URL: https://issues.jboss.org/browse/JBTM-2788 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Affects Versions: 5.3.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > > The [narayana QA test suite documentation |http://narayana.io//docs/project/index.html#d0e18351] is missing a description of the tests in the TestGroup_txcore group. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2018