May 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2675: ---------------------------------- Fix Version/s: 4.17.34 > Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2675 > URL: https://issues.jboss.org/browse/JBTM-2675 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 4.17.34, 5.next > > > ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2293) Create a docker file to make web page update easier

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2293?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2293. --------------------------------- Resolution: Rejected > Create a docker file to make web page update easier > --------------------------------------------------- > > Key: JBTM-2293 > URL: https://issues.jboss.org/browse/JBTM-2293 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Cloud > Reporter: Gytis Trikleris > > Awestruct recuires quite a few dependencies to build a web page. Although it is not hard to install them manually, it is time consuming. It would be much easier to use docker for this. > This docker file is a good start: https://github.com/goldmann/dockerfiles/tree/master/awestruct -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/JBTM-2675?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ivo Studensky created pull request #1012 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2675 > URL: https://issues.jboss.org/browse/JBTM-2675 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.2.17.Final, 5.3.2.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > > ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2675) Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation

by Ivo Studensky (JIRA)

Ivo Studensky created JBTM-2675: ----------------------------------- Summary: Participant Initialization startup() method instead of shutdown() at ParticipantSideInitialisation Key: JBTM-2675 URL: https://issues.jboss.org/browse/JBTM-2675 Project: JBoss Transaction Manager Issue Type: Bug Components: XTS Affects Versions: 5.3.2.Final, 5.2.17.Final Reporter: Ivo Studensky Assignee: Ivo Studensky ParticipantSideInitialisation class calls ParticipantInitialisation.startup() instead of ParticipantInitialisation.shutdown() in its shutdown method. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2646) Include a quickstart showing a command line equivalent of the wildfly transaction console

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2646?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2646: -------------------------------- Priority: Minor (was: Blocker) > Include a quickstart showing a command line equivalent of the wildfly transaction console > ----------------------------------------------------------------------------------------- > > Key: JBTM-2646 > URL: https://issues.jboss.org/browse/JBTM-2646 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tooling > Affects Versions: 5.3.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > Provide a standalone tool (in the form of a quickstart) that duplicates the functionality of the wildfly transactions console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2668) Entity manager does not join transaction properly in JTA and Hibernate quickstart

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2668?page=com.atlassian.jira.plugin.... ] Work on JBTM-2668 started by Gytis Trikleris. --------------------------------------------- > Entity manager does not join transaction properly in JTA and Hibernate quickstart > --------------------------------------------------------------------------------- > > Key: JBTM-2668 > URL: https://issues.jboss.org/browse/JBTM-2668 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > To reproduce begin transaction at the start of TestCase.testJpa method and roll it back just before assertion. During the abort in BasicAction pending list is empty and no resources are rolled back. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2674) JTA does not set transaction timeout for XAResource for propagated transactions

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2674?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2674: ---------------------------------- Affects Version/s: 5.2.16.Final > JTA does not set transaction timeout for XAResource for propagated transactions > ------------------------------------------------------------------------------- > > Key: JBTM-2674 > URL: https://issues.jboss.org/browse/JBTM-2674 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > > I can see a fact that transaction timeout is not provided by subordinate transaction when passed by ejb remote call when JTA transaction are used. > Even when transaction timeout is defined (it could be seen that timeout is used when xaresources is used on client) the server where transaction is propagated shows xa resources using the default timeou value. > Client server (caller) - timeout is _6 seconds_ > {code} > 2016-05-19 11:50:51,461 TRACE [com.arjuna.ats.jta] (default task-18) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:483, xid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, timeout:6, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-483 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@7b44816f >, record id=0:ffff7f000001:57a802d4:573d8c57:21 > {code} > Server (callee) - uses timeout _0 seconds_ > {code} > 2016-05-19 11:50:39,374 TRACE [com.arjuna.ats.jta] (default task-12) XAResourceRecord.topLevelPrepare for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:502, xid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, timeout:0, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-502 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@4f35ed3f >, record id=0:ffff7f000001:3b603de1:573d8c5f:18 > {code} > Scenario that I'm running is > # enlist jms xa resource on client > # call to second server, it means enlist ejb remoting xa resource to transaction > # enlist test xa on server > # enlist jms xa resource on server > # enlist test xa on client > # starting 2PC > # prepare jms xa resource on server > # prepare ejb remoting xa resource on server > # prepare test xa resource on client > # transaction timeout is hit > # if underlying jms resource timeouts then XAResource.prepare call fails with XAER_NOTA and the whole transaction is rolled back > # > _(attaching server.log files for EAP 7.0.0/Narayana 5.2.16.Final where jbossts is caller and jbossts2 is callee)_ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2674) JTA does not set transaction timeout for XAResource for propagated transactions

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2674?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka reassigned JBTM-2674: ------------------------------------- Assignee: Tom Jenkinson > JTA does not set transaction timeout for XAResource for propagated transactions > ------------------------------------------------------------------------------- > > Key: JBTM-2674 > URL: https://issues.jboss.org/browse/JBTM-2674 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > > I can see a fact that transaction timeout is not provided by subordinate transaction when passed by ejb remote call when JTA transaction are used. > Even when transaction timeout is defined (it could be seen that timeout is used when xaresources is used on client) the server where transaction is propagated shows xa resources using the default timeou value. > Client server (caller) - timeout is _6 seconds_ > {code} > 2016-05-19 11:50:51,461 TRACE [com.arjuna.ats.jta] (default task-18) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:483, xid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, timeout:6, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-483 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@7b44816f >, record id=0:ffff7f000001:57a802d4:573d8c57:21 > {code} > Server (callee) - uses timeout _0 seconds_ > {code} > 2016-05-19 11:50:39,374 TRACE [com.arjuna.ats.jta] (default task-12) XAResourceRecord.topLevelPrepare for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:502, xid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, timeout:0, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-502 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@4f35ed3f >, record id=0:ffff7f000001:3b603de1:573d8c5f:18 > {code} > Scenario that I'm running is > # enlist jms xa resource on client > # call to second server, it means enlist ejb remoting xa resource to transaction > # enlist test xa on server > # enlist jms xa resource on server > # enlist test xa on client > # starting 2PC > # prepare jms xa resource on server > # prepare ejb remoting xa resource on server > # prepare test xa resource on client > # transaction timeout is hit > # if underlying jms resource timeouts then XAResource.prepare call fails with XAER_NOTA and the whole transaction is rolled back > # > _(attaching server.log files for EAP 7.0.0/Narayana 5.2.16.Final where jbossts is caller and jbossts2 is callee)_ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2674) JTA does not set transaction timeout for XAResource for propagated transactions

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2674?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2674: ---------------------------------- Component/s: JTA > JTA does not set transaction timeout for XAResource for propagated transactions > ------------------------------------------------------------------------------- > > Key: JBTM-2674 > URL: https://issues.jboss.org/browse/JBTM-2674 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.2.16.Final > Reporter: Ondra Chaloupka > > I can see a fact that transaction timeout is not provided by subordinate transaction when passed by ejb remote call when JTA transaction are used. > Even when transaction timeout is defined (it could be seen that timeout is used when xaresources is used on client) the server where transaction is propagated shows xa resources using the default timeou value. > Client server (caller) - timeout is _6 seconds_ > {code} > 2016-05-19 11:50:51,461 TRACE [com.arjuna.ats.jta] (default task-18) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:483, xid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, timeout:6, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-483 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@7b44816f >, record id=0:ffff7f000001:57a802d4:573d8c57:21 > {code} > Server (callee) - uses timeout _0 seconds_ > {code} > 2016-05-19 11:50:39,374 TRACE [com.arjuna.ats.jta] (default task-12) XAResourceRecord.topLevelPrepare for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:502, xid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, timeout:0, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-502 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@4f35ed3f >, record id=0:ffff7f000001:3b603de1:573d8c5f:18 > {code} > Scenario that I'm running is > # enlist jms xa resource on client > # call to second server, it means enlist ejb remoting xa resource to transaction > # enlist test xa on server > # enlist jms xa resource on server > # enlist test xa on client > # starting 2PC > # prepare jms xa resource on server > # prepare ejb remoting xa resource on server > # prepare test xa resource on client > # transaction timeout is hit > # if underlying jms resource timeouts then XAResource.prepare call fails with XAER_NOTA and the whole transaction is rolled back > # > _(attaching server.log files for EAP 7.0.0/Narayana 5.2.16.Final where jbossts is caller and jbossts2 is callee)_ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2674) JTA does not set transaction timeout for XAResource for propagated transactions

by Ondra Chaloupka (JIRA)

Ondra Chaloupka created JBTM-2674: ------------------------------------- Summary: JTA does not set transaction timeout for XAResource for propagated transactions Key: JBTM-2674 URL: https://issues.jboss.org/browse/JBTM-2674 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Ondra Chaloupka I can see a fact that transaction timeout is not provided by subordinate transaction when passed by ejb remote call when JTA transaction are used. Even when transaction timeout is defined (it could be seen that timeout is used when xaresources is used on client) the server where transaction is propagated shows xa resources using the default timeou value. Client server (caller) - timeout is _6 seconds_ {code} 2016-05-19 11:50:51,461 TRACE [com.arjuna.ats.jta] (default task-18) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:483, xid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, timeout:6, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:57a802d4:573d8c57:20, subordinatenodename=null, eis_name=java:/TestXAResource-483 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-483 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@7b44816f >, record id=0:ffff7f000001:57a802d4:573d8c57:21 {code} Server (callee) - uses timeout _0 seconds_ {code} 2016-05-19 11:50:39,374 TRACE [com.arjuna.ats.jta] (default task-12) XAResourceRecord.topLevelPrepare for XAResourceRecord < resource:TestXAResource(TestXAResourceCommon(id:502, xid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, timeout:0, prepareReturn:0)), txid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff7f000001:57a802d4:573d8c57:11, node_name=1, branch_uid=0:ffff7f000001:3b603de1:573d8c5f:17, subordinatenodename=2, eis_name=java:/TestXAResource-502 >, heuristic: TwoPhaseOutcome.FINISH_OK, product: Crash Recovery Test/EAP Test, jndiName: java:/TestXAResource-502 com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@4f35ed3f >, record id=0:ffff7f000001:3b603de1:573d8c5f:18 {code} Scenario that I'm running is # enlist jms xa resource on client # call to second server, it means enlist ejb remoting xa resource to transaction # enlist test xa on server # enlist jms xa resource on server # enlist test xa on client # starting 2PC # prepare jms xa resource on server # prepare ejb remoting xa resource on server # prepare test xa resource on client # transaction timeout is hit # if underlying jms resource timeouts then XAResource.prepare call fails with XAER_NOTA and the whole transaction is rolled back # _(attaching server.log files for EAP 7.0.0/Narayana 5.2.16.Final where jbossts is caller and jbossts2 is callee)_ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 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