May 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2175) XTS HierarchyTest failure

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2175: ------------------------------------- Summary: XTS HierarchyTest failure Key: JBTM-2175 URL: https://issues.jboss.org/browse/JBTM-2175 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.0.2 http://172.17.131.2/view/Narayana+BlackTie/job/narayana/517/PROFILE=XTS,j... {code} ------------------------------------------------------------------------------- Test set: com.arjuna.wsas.tests.arq.basic.HierarchyTest ------------------------------------------------------------------------------- Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.197 sec <<< FAILURE! testComparision(com.arjuna.wsas.tests.arq.basic.HierarchyTest) Time elapsed: 0.086 sec <<< FAILURE! java.lang.AssertionError: null at org.junit.Assert.fail(Assert.java:86) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertFalse(Assert.java:64) at org.junit.Assert.assertFalse(Assert.java:74) at com.arjuna.wsas.tests.arq.basic.HierarchyTest.testComparision(HierarchyTest.java:87)` {code} {code} [0m18:39:20,935 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content [0m[0m18:39:20,941 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "test.war" (runtime-name: "test.war") [0m[33m18:39:21,282 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. [0m[0m18:39:21,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment test.war [0m[0m18:39:21,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: test.war [0m[0m18:39:21,403 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment test.war [0m[0m18:39:22,065 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /test [0m[0m18:39:22,503 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "test.war" (runtime-name : "test.war") [0m[0m18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 [0m[0m18:39:22,977 INFO [stdout] (default task-4) Started: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:21 [0m[0m18:39:22,978 INFO [stdout] (default task-4) [0m[0m18:39:22,978 INFO [stdout] (default task-4) Hierarchy: Activity context: 0:ffffac118321:-6095bd9c:537258b4:20 0:ffffac118321:-6095bd9c:537258b4:21 [0m[0m18:39:22,978 INFO [stdout] (default task-4) [0m[0m18:39:22,978 INFO [stdout] (default task-4) Current: ActivityImple: 0:ffffac118321:-6095bd9c:537258b4:20 [0m[0m18:39:23,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /test [0m[0m18:39:23,092 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment test.war [0m[0m18:39:23,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment test.war (runtime-name: test.war) in 50ms [0m[0m18:39:23,272 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/ac/46009223d8a629a76daadbd3e571660ba5d77a/content [0m[0m18:39:23,273 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "test.war" (runtime-name: "test.war") [0m {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2165?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2165: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/659, https://github.com/jbosstm/narayana/pull/660 (was: https://github.com/jbosstm/narayana/pull/658, https://github.com/jbosstm/narayana/pull/659) > CMR synchronisations should be interposed > ----------------------------------------- > > Key: JBTM-2165 > URL: https://issues.jboss.org/browse/JBTM-2165 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.20, 5.0.2 > > > A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2165?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2165: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CMR synchronisations should be interposed > ----------------------------------------- > > Key: JBTM-2165 > URL: https://issues.jboss.org/browse/JBTM-2165 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.20, 5.0.2 > > > A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2165) CMR synchronisations should be interposed

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2165?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2165: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/658, https://github.com/jbosstm/narayana/pull/659 A normal beforeCompletion synchronisation (aka session synch) is allowed to enlist a CMR resource into a transaction which in turn will register its own synch. The latter must be ordered after any synchs that have already ran or are already running. The fix is to register CMR synchs as interposed (see javax.transaction.TransactionSynchronizationRegistry#registerInterposedSynchronization) which are guaranteed to run after all normal session synchs have been called. > CMR synchronisations should be interposed > ----------------------------------------- > > Key: JBTM-2165 > URL: https://issues.jboss.org/browse/JBTM-2165 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19, 5.0.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.20, 5.0.2 > > > A CMR resource registers a synchronization to perform deferred cleanup of xids. Since it is possible for another synchronization to enlist a CMR resource the CMR synch must be ordered after non interposed synchronizations. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2121) Add a jdbc object store implementation for later revisions of MySQL driver

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2121?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2121: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1027126|https://bugzilla.redhat.com/show_bug.cgi?id=1027126] from ASSIGNED to MODIFIED > Add a jdbc object store implementation for later revisions of MySQL driver > -------------------------------------------------------------------------- > > Key: JBTM-2121 > URL: https://issues.jboss.org/browse/JBTM-2121 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.17.17, 5.0.1 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.20, 5.0.2 > > > commit 44553931 updated the MySQl driver to 5.1.28. > In this revision of the driver, it is reporting as mysql, not mysql_ab. It should be possible to duplicate our mysql_ab_driver to mysql_driver in order to catch both cases. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1702) one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1702?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-1702: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=983039, https://bugzilla.redhat.com/show_bug.cgi?id=990503, https://bugzilla.redhat.com/show_bug.cgi?id=1096947, https://bugzilla.redhat.com/show_bug.cgi?id=1097265 (was: https://bugzilla.redhat.com/show_bug.cgi?id=983039, https://bugzilla.redhat.com/show_bug.cgi?id=990503, https://bugzilla.redhat.com/show_bug.cgi?id=1096947) > one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success > ------------------------------------------------------------------------------------------------- > > Key: JBTM-1702 > URL: https://issues.jboss.org/browse/JBTM-1702 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 5.0.0.M2 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.18, 5.0.2 > > > We provide our own XAResource implementation for our database product, > in our unit testsuite we do also test common error conditions. > The error condition we test here is, that XAResource.end() throws an XAException with an XA_RBCOMMFAIL error code, this error code (by definition and also in our implementation) indicates an unilateral transaction rollback. > The expected behavior is, that when the TransactionManager invokes end() during it's commit procedure and sees an exception, that the transaction is considered as rolled-back and the bean client receives an exception, indicating the transaction failure. > The observed behavior is, that the bean client completes the bean method invocation successfully. Of course the transaction was rolled back by the database server and the subsequent bean invocations don't work correctly, because data assumed to be stored was actually not stored. > This error occurs if and only if the one-phase optimization is used, i.e. if > exactly one XAResource instance is enlisted with the TransactionManager. > If we enlist 2+ XAResource instances, then the one-phase optimization can't be used and the observed behavior is as expected, i.e. the bean client gets an exception, that the transaction could not be completed successfully. > The broken logic is contained in here (also see a complete stack trace below): > com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2310) --> l.2339-2360: actionStatus = ActionStatus.COMMITTED > Here the outcome was TwoPhaseOutcome.FINISH_ERROR but is mapped to ActionStatus.COMMITTED, this is clearly wrong for all XA_RB* error codes. > FIX suggestion: If there are cases, where this mapping is required, then instead of one FINISH_ERROR return value, two return values should be introduced, so that at least all XA_RB* error codes can be mapped properly to a transaction failure. > This is the complete stacktrace of our exception (logged immediately prior before it was thrown): > About to throw 1: com.versant.odbms.VersantXAException: Detach error: Network error on database [jpadb1@localhost]. > com.versant.odbms.VersantXAException: Detach error: Network error on database [jpadb1@localhost]. > at com.versant.odbms.XAResourceImpl.getResult(XAResourceImpl.java:553) > at com.versant.odbms.XAResourceBase.detach(XAResourceBase.java:54) > at com.versant.odbms.XAResourceImpl.end(XAResourceImpl.java:278) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelOnePhaseCommit(XAResourceRecord.java:597) --> returns TwoPhaseOutcome.FINISH_ERROR (l.734) > at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2310) --> l.2339-2360: actionStatus = ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1475) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:98) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) --> returns ActionStatus.COMMITTED > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165) --> l.1169 break, no exception > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2174) Provide LockFree annotation and test

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2174?page=com.atlassian.jira.plugin.... ] Mark Little closed JBTM-2174. ----------------------------- > Provide LockFree annotation and test > ------------------------------------ > > Key: JBTM-2174 > URL: https://issues.jboss.org/browse/JBTM-2174 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > Fix For: 5.0.2 > > > TransactionFree exists but is a superset (disassociates the transaction context too). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2174) Provide LockFree annotation and test

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2174?page=com.atlassian.jira.plugin.... ] Mark Little resolved JBTM-2174. ------------------------------- Resolution: Done > Provide LockFree annotation and test > ------------------------------------ > > Key: JBTM-2174 > URL: https://issues.jboss.org/browse/JBTM-2174 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > Fix For: 5.0.2 > > > TransactionFree exists but is a superset (disassociates the transaction context too). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2174) Provide LockFree annotation and test

by Mark Little (JIRA)

Mark Little created JBTM-2174: --------------------------------- Summary: Provide LockFree annotation and test Key: JBTM-2174 URL: https://issues.jboss.org/browse/JBTM-2174 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: STM Affects Versions: 5.0.1 Reporter: Mark Little Assignee: Mark Little Fix For: 5.0.2 TransactionFree exists but is a superset (disassociates the transaction context too). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2173) Inherited annotations

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2173?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2173: ----------------------------------- Careful thought in that some probably should be but others maybe not so much. > Inherited annotations > --------------------- > > Key: JBTM-2173 > URL: https://issues.jboss.org/browse/JBTM-2173 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > > More of an open question at this point: should the annotations be @Inherited? Needs careful thought and time I don't have at this point ;) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 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 2014