November 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1801) Move all test properties into root pom.xml

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1801?page=com.atlassian.jira.plugin.... ] Gytis Trikleris reassigned JBTM-1801: ------------------------------------- Assignee: (was: Gytis Trikleris) > Move all test properties into root pom.xml > ------------------------------------------ > > Key: JBTM-1801 > URL: https://issues.jboss.org/browse/JBTM-1801 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Paul Robinson > Priority: Trivial > Fix For: 5.later > > > We have these test properties duplicated in many places: > https://github.com/jbosstm/narayana/blob/master/XTS/localjunit/pom.xml#L22 > We should move them up to the root pom.xml to simplify maintenance. As part of this task you need to hunt out all these usages and similar. Then come up with a common set of properties that works in all cases and move to the root pom.xml. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-928) ATParticipantCrashAndRecover Crash Recovery test needs completing

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-928?page=com.atlassian.jira.plugin.s... ] Gytis Trikleris reassigned JBTM-928: ------------------------------------ Assignee: (was: Gytis Trikleris) > ATParticipantCrashAndRecover Crash Recovery test needs completing > ----------------------------------------------------------------- > > Key: JBTM-928 > URL: https://issues.jboss.org/browse/JBTM-928 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing, XTS > Affects Versions: 4.17.0.M1/5.0.0.M1 > Reporter: Tom Jenkinson > > This test was not completed due to a problem with JBossWS that prevented the test case from being possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 12 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: -------------------------------- Fix Version/s: 5.next > 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, 12 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: Resolved (was: Pull Request Sent) Resolution: Done > 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 > > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2800) Miscellaneous qa suite improvements

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2800?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2800. --------------------------------- Assignee: Tom Jenkinson Resolution: Done > Miscellaneous qa suite improvements > ----------------------------------- > > Key: JBTM-2800 > URL: https://issues.jboss.org/browse/JBTM-2800 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Some of the tests are not easy to debug and during debug you have to constantly move your TaskImpl.properties out of the way so provide a way to get more logging and allow setting options such as remote debugger easier. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2800) Miscellaneous qa suite improvements

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2800?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2800: -------------------------------- Fix Version/s: 5.next > Miscellaneous qa suite improvements > ----------------------------------- > > Key: JBTM-2800 > URL: https://issues.jboss.org/browse/JBTM-2800 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Fix For: 5.next > > > Some of the tests are not easy to debug and during debug you have to constantly move your TaskImpl.properties out of the way so provide a way to get more logging and allow setting options such as remote debugger easier. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2787) TestGroup_txcore_recovery::Recovery_Crash_StateManager_Test004 fails with DB2

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2787?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2787: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TestGroup_txcore_recovery::Recovery_Crash_StateManager_Test004 fails with DB2 > ----------------------------------------------------------------------------- > > Key: JBTM-2787 > URL: https://issues.jboss.org/browse/JBTM-2787 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > When DB2 tests are running (this is a very slow configuration for CI) the recovery manager process appears to be interfering with the setup of the test. > Set up of test: > 2016-11-06 16:04:03,172 out: 2016-11-06 16:04:03,172 [main] WARN com.arjuna.ats.arjuna - ARJUNA012382: Action id 0:ffffac11000a:c397:581f5466:4 could not be transitioned to committed > Recovery manager process: > 2016-11-06 16:04:24,188 out: 2016-11-06 16:04:24,188 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012382: Action id 0:ffffac11000a:c397:581f5466:1 could not be transitioned to committed > 2016-11-06 16:04:24,225 out: 2016-11-06 16:04:24,225 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012016: PersistenceRecord::topLevelCommit - commit_state call failed for 0:ffffac11000a:c397:581f5466:1 > 2016-11-06 16:04:24,225 out: 2016-11-06 16:04:24,225 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012022: PersistenceRecord::topLevelCommit - commit_state error > 2016-11-06 16:04:25,504 out: 2016-11-06 16:04:25,504 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012382: Action id 0:ffffac11000a:c397:581f5466:3 could not be transitioned to committed > 2016-11-06 16:04:25,549 out: 2016-11-06 16:04:25,549 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012016: PersistenceRecord::topLevelCommit - commit_state call failed for 0:ffffac11000a:c397:581f5466:3 > 2016-11-06 16:04:25,549 out: 2016-11-06 16:04:25,549 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012022: PersistenceRecord::topLevelCommit - commit_state error > 2016-11-06 16:04:37,523 out: 2016-11-06 16:04:37,523 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012382: Action id 0:ffffac11000a:c397:581f5466:4 could not be transitioned to committed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2787) TestGroup_txcore_recovery::Recovery_Crash_StateManager_Test004 fails with DB2

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2787?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2787: -------------------------------- Fix Version/s: 5.next > TestGroup_txcore_recovery::Recovery_Crash_StateManager_Test004 fails with DB2 > ----------------------------------------------------------------------------- > > Key: JBTM-2787 > URL: https://issues.jboss.org/browse/JBTM-2787 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > When DB2 tests are running (this is a very slow configuration for CI) the recovery manager process appears to be interfering with the setup of the test. > Set up of test: > 2016-11-06 16:04:03,172 out: 2016-11-06 16:04:03,172 [main] WARN com.arjuna.ats.arjuna - ARJUNA012382: Action id 0:ffffac11000a:c397:581f5466:4 could not be transitioned to committed > Recovery manager process: > 2016-11-06 16:04:24,188 out: 2016-11-06 16:04:24,188 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012382: Action id 0:ffffac11000a:c397:581f5466:1 could not be transitioned to committed > 2016-11-06 16:04:24,225 out: 2016-11-06 16:04:24,225 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012016: PersistenceRecord::topLevelCommit - commit_state call failed for 0:ffffac11000a:c397:581f5466:1 > 2016-11-06 16:04:24,225 out: 2016-11-06 16:04:24,225 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012022: PersistenceRecord::topLevelCommit - commit_state error > 2016-11-06 16:04:25,504 out: 2016-11-06 16:04:25,504 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012382: Action id 0:ffffac11000a:c397:581f5466:3 could not be transitioned to committed > 2016-11-06 16:04:25,549 out: 2016-11-06 16:04:25,549 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012016: PersistenceRecord::topLevelCommit - commit_state call failed for 0:ffffac11000a:c397:581f5466:3 > 2016-11-06 16:04:25,549 out: 2016-11-06 16:04:25,549 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012022: PersistenceRecord::topLevelCommit - commit_state error > 2016-11-06 16:04:37,523 out: 2016-11-06 16:04:37,523 [Periodic Recovery] WARN com.arjuna.ats.arjuna - ARJUNA012382: Action id 0:ffffac11000a:c397:581f5466:4 could not be transitioned to committed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2673) ThreadUtil getThreadId(Thread) ignores argument

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2673?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2673. --------------------------------- Resolution: Done > ThreadUtil getThreadId(Thread) ignores argument > ----------------------------------------------- > > Key: JBTM-2673 > URL: https://issues.jboss.org/browse/JBTM-2673 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > During investigation of https://developer.jboss.org/thread/269784?start=15&tstart=0 it was observed that the ThreadUtil implementation does not use the Thread argument and simply uses a ThreadLocal: > https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2803) compareHierarchies traceln's wrong elements

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2803?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2803. --------------------------------- Fix Version/s: 5.next Assignee: Tom Jenkinson Resolution: Done > compareHierarchies traceln's wrong elements > ------------------------------------------- > > Key: JBTM-2803 > URL: https://issues.jboss.org/browse/JBTM-2803 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > If compareHierarchies is called (only done in trace iirc) then the right elements are compared but if they are not equal the wrong elements are compared IOOBE are possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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