June 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2679: ------------------------------------- Hi Ondra, the fix version is 5.next (in case we added a new feature too). I marked it resolved - thanks for the contribution! > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next, 5.2.18.Final > > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. > Created assembly plugin jira: https://issues.apache.org/jira/browse/MASSEMBLY-809 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2679) Artifact of narayana-full does not contain bits of jbossxts.jar

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2679?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2679: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next 5.2.18.Final Resolution: Done > Artifact of narayana-full does not contain bits of jbossxts.jar > --------------------------------------------------------------- > > Key: JBTM-2679 > URL: https://issues.jboss.org/browse/JBTM-2679 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next, 5.2.18.Final > > > Zip file {{narayana-full-$VERSION-bin.zip}} under directory {{narayana-full/target}} which is created from the built artifacts does not contains bits of {{jbossxts.jar}}. The artifact for xts with the filename {{jbossxts.jar}} is available but contains the same bits as it's counterpart {{-api}} jar file. > Created assembly plugin jira: https://issues.apache.org/jira/browse/MASSEMBLY-809 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2687) There are typos in DisabledContextPropagationTests and EnabledContextPropagationTests

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBTM-2687?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Dan Simko created pull request #1021 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > There are typos in DisabledContextPropagationTests and EnabledContextPropagationTests > ------------------------------------------------------------------------------------- > > Key: JBTM-2687 > URL: https://issues.jboss.org/browse/JBTM-2687 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing, TxBridge > Affects Versions: 5.3.3.Final > Reporter: Daniel Simko > Assignee: Gytis Trikleris > Priority: Minor > > There are three times: > {code}parameters.add(new BasicNameValuePair("isTransaction", "ture"));{code} > instead of > {code}parameters.add(new BasicNameValuePair("isTransaction", "true"));{code} > which affect test behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2687) There are typos in DisabledContextPropagationTests and EnabledContextPropagationTests

by Daniel Simko (JIRA)

Daniel Simko created JBTM-2687: ---------------------------------- Summary: There are typos in DisabledContextPropagationTests and EnabledContextPropagationTests Key: JBTM-2687 URL: https://issues.jboss.org/browse/JBTM-2687 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing, TxBridge Affects Versions: 5.3.3.Final Reporter: Daniel Simko Assignee: Gytis Trikleris Priority: Minor There are three times: {code}parameters.add(new BasicNameValuePair("isTransaction", "ture"));{code} instead of {code}parameters.add(new BasicNameValuePair("isTransaction", "true"));{code} which affect test behavior. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2686) Introduce a Heuristic example in the karaf osgi-jta quickstart

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2686?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Amos Feng created pull request #171 in GitHub --------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Introduce a Heuristic example in the karaf osgi-jta quickstart > -------------------------------------------------------------- > > Key: JBTM-2686 > URL: https://issues.jboss.org/browse/JBTM-2686 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > > This example could be used to show how to mange the transaction object stores with the karaf cli commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2686) Introduce a Heuristic example in the karaf osgi-jta quickstart

by Amos Feng (JIRA)

Amos Feng created JBTM-2686: ------------------------------- Summary: Introduce a Heuristic example in the karaf osgi-jta quickstart Key: JBTM-2686 URL: https://issues.jboss.org/browse/JBTM-2686 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Demonstrator Reporter: Amos Feng Assignee: Amos Feng This example could be used to show how to mange the transaction object stores with the karaf cli commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2677: -------------------------------- Comment: was deleted (was: Please can you attach a trace log, I have trouble getting the test running.) > 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 > Fix For: 5.next > > > 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, 10 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2677: -------------------------------- Comment: was deleted (was: I see the log on the JBEAP) > 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 > Fix For: 5.next > > > 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, 10 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2677: ------------------------------------- I see the log on the JBEAP > 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 > Fix For: 5.next > > > 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, 10 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2677?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2677: ------------------------------------- Please can you attach a trace log, I have trouble getting the test running. > 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 > Fix For: 5.next > > > 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, 10 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 June 2016