May 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1107: -------------------------------- Reporter: Tom Jenkinson (was: Paul Robinson) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Compensations > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers would be invoked in case of the system crash. > In addition, @CompensationScoped beans should be available during the recovery. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2678) @TxLogged annotation not working

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2678?page=com.atlassian.jira.plugin.... ] Gytis Trikleris reassigned JBTM-2678: ------------------------------------- Assignee: Gytis Trikleris > @TxLogged annotation not working > -------------------------------- > > Key: JBTM-2678 > URL: https://issues.jboss.org/browse/JBTM-2678 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > @TxLogged annotation does not work in Compensations framework. All it's assertions were removed from the tests with this commit: https://github.com/jbosstm/narayana/commit/efd15eeb080c6b6338f3658c4aa581... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2678) @TxLogged annotation does not work

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2678?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2678: ---------------------------------- Summary: @TxLogged annotation does not work (was: @TxLogged annotation not working) > @TxLogged annotation does not work > ---------------------------------- > > Key: JBTM-2678 > URL: https://issues.jboss.org/browse/JBTM-2678 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > @TxLogged annotation does not work in Compensations framework. All it's assertions were removed from the tests with this commit: https://github.com/jbosstm/narayana/commit/efd15eeb080c6b6338f3658c4aa581... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2678) @TxLogged annotation not working

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2678: ------------------------------------- Summary: @TxLogged annotation not working Key: JBTM-2678 URL: https://issues.jboss.org/browse/JBTM-2678 Project: JBoss Transaction Manager Issue Type: Bug Components: Compensations Reporter: Gytis Trikleris Fix For: 5.next @TxLogged annotation does not work in Compensations framework. All it's assertions were removed from the tests with this commit: https://github.com/jbosstm/narayana/commit/efd15eeb080c6b6338f3658c4aa581... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2579) Throw XAException in XATerminator::commit if a wrapped resource fails transiently

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2579?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2579: ----------------------------------------------- Radovan Netuka <rnetuka(a)redhat.com> changed the Status of [bug 1329142|https://bugzilla.redhat.com/show_bug.cgi?id=1329142] from ASSIGNED to MODIFIED > Throw XAException in XATerminator::commit if a wrapped resource fails transiently > --------------------------------------------------------------------------------- > > Key: JBTM-2579 > URL: https://issues.jboss.org/browse/JBTM-2579 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.31, 5.2.9.Final > > > It is possible for a resource that we are wrapping to return say XA_RETRY or XA_RMFAIL and therefore end up in the BasicAction failed list. However there is no error returned from commit in this circumstance as the recovery manager should ensure a consistent outcome. > The reason this becomes a problem for JTA and XATerminator in particular is that as no error is returned a parent coordinator will assume the branch completed successfully. In the future when it calls XATerminator::recover though this branch will be returned and detected as an orphan. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka reassigned JBTM-2677: ------------------------------------- Assignee: Tom Jenkinson > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2677: ---------------------------------- Affects Version/s: 5.2.16.Final > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2677: ---------------------------------- Component/s: JTS > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2677 > URL: https://issues.jboss.org/browse/JBTM-2677 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > > I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. > The scenario is following: > There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. > # RAR is deployed > # RAR opens a java socket where listens for message > # MDB of TestResourceMessageListener is deployed > # test client sends prepare command > # test client sends commit command > # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL > # test client receives error code XAER_RMFAIL > # test client sends recover command > # test client receives number of in-doubt xid - which is one > # test client sends rollback command > # XATerminator calls rollback on the in-doubt xid > # expecting TestXAResource.rollback would be called > After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). > [1] > {code} > 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) > 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2677) XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created JBTM-2677: ------------------------------------- Summary: XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used Key: JBTM-2677 URL: https://issues.jboss.org/browse/JBTM-2677 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Ondra Chaloupka I do experience an issue of not rollbacking failed XAResource when XATerminator.rollback is called on jca inflow transaction. This works wrong when JTS is used. For the same testcase when JTA is used all in-doubt XAResources are rolled back. The scenario is following: There is a a test RA which drives an inflow transaction to a MDB. MDB then works with two TestXAResources which are enlisted to the supplied transaction. # RAR is deployed # RAR opens a java socket where listens for message # MDB of TestResourceMessageListener is deployed # test client sends prepare command # test client sends commit command # first TestXAResource commits, second TestXAResource throws XAException.XAER_RMFAIL # test client receives error code XAER_RMFAIL # test client sends recover command # test client receives number of in-doubt xid - which is one # test client sends rollback command # XATerminator calls rollback on the in-doubt xid # expecting TestXAResource.rollback would be called After the XATerminator.rollback is invoked there is no call of rollback for the unfinished XAResource. I can see that abort phase is invoked [1] (see attached jboss eap server.log) but the real invocation of the XAResource.rollback does not happen (for the JTA transaction it runs fine). [1] {code} 2016-05-18 11:20:20,385 TRACE [com.arjuna.ats.jts] (default-threads- 1) ServerTransaction::doPhase2Abort (0:ffff7f000001:-728dfa93:573c33bc:24 ) 2016-05-18 11:20:55,416 TRACE [com.arjuna.ats.jts] (default-threads- 1) ArjunaTransactionImple::get_status for 0:ffff7f000001:-728dfa93:573c33bc:24 returning CosTransactions::StatusCommitted -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2634) Create Narayana Spring Boot starter quickstart

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2634?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2634: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create Narayana Spring Boot starter quickstart > ---------------------------------------------- > > Key: JBTM-2634 > URL: https://issues.jboss.org/browse/JBTM-2634 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Create a demonstrator application for Narayana Spring Boot starter before raising pull request to Spring. This would allow to make a better review of the Narayana Spring Boot integration on the forum. > Quickstart should have a simple example of JTA and crash recovery. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 12 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 May 2016