November 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2789) Replace deprecated resteasy classes

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2789?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2789. ------------------------------- > Replace deprecated resteasy classes > ----------------------------------- > > Key: JBTM-2789 > URL: https://issues.jboss.org/browse/JBTM-2789 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.3.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.4.0.Final > > > Replace resteasy classes with the jaxrs 2 equivalents in the jpa quickstart: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-quickstarts-ipv6/... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2739) Add a CI job for testing jboss-transaction-spi

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2739?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2739. --------------------------------- Resolution: Done > Add a CI job for testing jboss-transaction-spi > ---------------------------------------------- > > Key: JBTM-2739 > URL: https://issues.jboss.org/browse/JBTM-2739 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > We need a CI job to test that narayana works with the latest jboss-transaction-spi and this should include PRs as well as master. > In addition, the two projects duplicate tests so the the duplicates need removing from narayana (but only after we have added this CI testing). > Note that jboss-transaction-spi has a test dependency on the last released stable version of narayana so that dependency would need to changed to the version of our current SNAPSHOT for these new proposed CI jobs to be useful. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2739) Add a CI job for testing jboss-transaction-spi

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2739?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2739: -------------------------------- Fix Version/s: 5.next > Add a CI job for testing jboss-transaction-spi > ---------------------------------------------- > > Key: JBTM-2739 > URL: https://issues.jboss.org/browse/JBTM-2739 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > We need a CI job to test that narayana works with the latest jboss-transaction-spi and this should include PRs as well as master. > In addition, the two projects duplicate tests so the the duplicates need removing from narayana (but only after we have added this CI testing). > Note that jboss-transaction-spi has a test dependency on the last released stable version of narayana so that dependency would need to changed to the version of our current SNAPSHOT for these new proposed CI jobs to be useful. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2771) JTS XAResources that throw XA_RETRY or XAER_RMFAIL cannot be retried

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2771?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2771: -------------------------------- Fix Version/s: 5.next > JTS XAResources that throw XA_RETRY or XAER_RMFAIL cannot be retried > -------------------------------------------------------------------- > > Key: JBTM-2771 > URL: https://issues.jboss.org/browse/JBTM-2771 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.3.5.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > Attachments: JMSProxyMessagingServerCrashRecoveryTestCase_prepareHalt_jts_server.log > > > There is a flag that is persisted _committed which defines if a commit was attempted on an XAResource. In the case where the XAR returned XARETRY for example, we would have consulted that flag and not reattempted the commit. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2771) JTS XAResources that throw XA_RETRY or XAER_RMFAIL cannot be retried

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2771?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2771: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JTS XAResources that throw XA_RETRY or XAER_RMFAIL cannot be retried > -------------------------------------------------------------------- > > Key: JBTM-2771 > URL: https://issues.jboss.org/browse/JBTM-2771 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.3.5.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > Attachments: JMSProxyMessagingServerCrashRecoveryTestCase_prepareHalt_jts_server.log > > > There is a flag that is persisted _committed which defines if a commit was attempted on an XAResource. In the case where the XAR returned XARETRY for example, we would have consulted that flag and not reattempted the commit. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2761) Add the nexus repository to the OSGi quickstart

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2761?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2761: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Add the nexus repository to the OSGi quickstart > ----------------------------------------------- > > Key: JBTM-2761 > URL: https://issues.jboss.org/browse/JBTM-2761 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Can't be found by the CI system until it flushes to maven central -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2783) Add suspend and resume methods to RecoveryManagerService application server integration code

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2783?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2783: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Add suspend and resume methods to RecoveryManagerService application server integration code > -------------------------------------------------------------------------------------------- > > Key: JBTM-2783 > URL: https://issues.jboss.org/browse/JBTM-2783 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Recovery manager service in WildFly needs to be able to suspend and resume recovery manager service. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2786) MySQL JDBCStore occasionally gets deadlock exception

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2786?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2786: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1087 > MySQL JDBCStore occasionally gets deadlock exception > ---------------------------------------------------- > > Key: JBTM-2786 > URL: https://issues.jboss.org/browse/JBTM-2786 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Occasionally in QA tests we see the MySQL CI job fail with messages about deadlocks. > From what I can see from http://stackoverflow.com/questions/2332768/how-to-avoid-mysql-deadlock-fo... it can be because the where clauses are not ordered the same so a table lock can happen. Reordering the where clauses would hopefully fix this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2769) CMR resource calls xa_forget on local resources

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2769?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2769: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CMR resource calls xa_forget on local resources > ----------------------------------------------- > > Key: JBTM-2769 > URL: https://issues.jboss.org/browse/JBTM-2769 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.3.5.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > {code} > 2016-10-06 17:50:17,105 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012290: failed to recover Transaction 0:ffff7f000001:6351fff9:57f67185:2a: java.lang.NullPointerException > at com.arjuna.ats.internal.jta.resources.arjunacore.CommitMarkableResourceRecord.forgetHeuristic(CommitMarkableResourceRecord.java:544) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doForget(BasicAction.java:3603) > at com.arjuna.ats.arjuna.coordinator.BasicAction.forgetHeuristics(BasicAction.java:1347) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Abort(BasicAction.java:1991) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doCommit(BasicAction.java:2852) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Commit(BasicAction.java:1871) > at com.arjuna.ats.arjuna.recovery.RecoverAtomicAction.replayPhase2(RecoverAtomicAction.java:71) > at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.doRecoverTransaction(AtomicActionRecoveryModule.java:152) > at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.processTransactionsStatus(AtomicActionRecoveryModule.java:253) > at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.periodicWorkSecondPass(AtomicActionRecoveryModule.java:109) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) > {code} > A local resource will have no concept of the forget and indeed the app server has an implementation that throws an exception if you call it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2770) Xids that relate to an CMR that has been recovered are rolledback even if the CMR committed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2770?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2770: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Xids that relate to an CMR that has been recovered are rolledback even if the CMR committed > ------------------------------------------------------------------------------------------- > > Key: JBTM-2770 > URL: https://issues.jboss.org/browse/JBTM-2770 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.3.5.Final > Reporter: Ondra Chaloupka > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > During recovery the CMR orphan detection checks to make sure that there is not an indoubt transaction that pertains to the CMR before deciding if an Xid is an orphan. Actually the check should also see if the transaction committed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 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 November 2016