July 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2709) ObjectStoreBrowser cannot cope with JDBC store on Windows

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2709?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2709: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ObjectStoreBrowser cannot cope with JDBC store on Windows > --------------------------------------------------------- > > Key: JBTM-2709 > URL: https://issues.jboss.org/browse/JBTM-2709 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > While testing backport of JBTM-2614 I came across the ObjStoreBrowser test. This was failing on Windows. On looking into it I saw it was because the Browser map swaps the "/" in the type name to the system file separator path. This is likely because of the file system store. I have a fix that puts the entry in both ways but it will likely need some more work so providing as an example. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2713) Remove FileLock cruft from LogStore file

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2713: ----------------------------------- Summary: Remove FileLock cruft from LogStore file Key: JBTM-2713 URL: https://issues.jboss.org/browse/JBTM-2713 Project: JBoss Transaction Manager Issue Type: Task Components: Transaction Core Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Minor Fix For: 5.next It certainly isn't referenced: https://github.com/jbosstm/narayana/blob/29270942f17cc553ad1497a41f60fce1... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2712) Karaf build failing

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2712?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2712: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/370/ http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/964/ > Karaf build failing > ------------------- > > Key: JBTM-2712 > URL: https://issues.jboss.org/browse/JBTM-2712 > Project: JBoss Transaction Manager > Issue Type: Task > Components: OSGi > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > > The build of Karaf has started failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2712) Karaf build failing

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2712: ----------------------------------- Summary: Karaf build failing Key: JBTM-2712 URL: https://issues.jboss.org/browse/JBTM-2712 Project: JBoss Transaction Manager Issue Type: Task Components: OSGi Reporter: Tom Jenkinson Assignee: Amos Feng Priority: Blocker The build of Karaf has started failing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2711) Upgrade BlackTie to reference WildFly 11.0.0.Alpha1-SNAPSHOT

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2711?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #1039 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade BlackTie to reference WildFly 11.0.0.Alpha1-SNAPSHOT > ------------------------------------------------------------ > > Key: JBTM-2711 > URL: https://issues.jboss.org/browse/JBTM-2711 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > WildFly have gone to 11.0.0.Alpha1-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2711) Upgrade BlackTie to reference WildFly 11.0.0.Alpha1-SNAPSHOT

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2711: ----------------------------------- Summary: Upgrade BlackTie to reference WildFly 11.0.0.Alpha1-SNAPSHOT Key: JBTM-2711 URL: https://issues.jboss.org/browse/JBTM-2711 Project: JBoss Transaction Manager Issue Type: Task Components: BlackTie Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Blocker Fix For: 5.next WildFly have gone to 11.0.0.Alpha1-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2614: ----------------------------------------------- Tom Ross <tom.ross(a)redhat.com> changed the Status of [bug 1360648|https://bugzilla.redhat.com/show_bug.cgi?id=1360648] from ASSIGNED to POST > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.13.Final > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 9 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2710?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2710: ------------------------------------- The issue is that the "massage" in ServerTransaction of the value does not take into account a failure during a prepared resource. During investigation there is also the possibility to leave the corba endpoint open if we get a transient retryable error in the JTA commit. > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2710 > URL: https://issues.jboss.org/browse/JBTM-2710 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA, JTS > 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, 9 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2710?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #1038 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2710 > URL: https://issues.jboss.org/browse/JBTM-2710 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA, JTS > 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, 9 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2710?page=com.atlassian.jira.plugin.... ] Tom Jenkinson moved JBEAP-5454 to JBTM-2710: -------------------------------------------- Project: JBoss Transaction Manager (was: JBoss Enterprise Application Platform) Key: JBTM-2710 (was: JBEAP-5454) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JCA JTS (was: Transactions) Affects Version/s: (was: 7.0.0.GA) > XATerminator.rollback does not invoke XAResource.rollback for failed resources when JTS is used > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2710 > URL: https://issues.jboss.org/browse/JBTM-2710 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA, JTS > 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, 9 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 July 2016