December 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1383) LogStoreRecoveryTest hang

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1383?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1383: ------------------------------------- Doesn't seem to reproduce if you just run the single test: {code} for i in {1..200}; do echo ITERATION $i; ./build.sh -f ArjunaCore/arjuna/pom.xml -Dtest=LogStoreRecoveryTest test ; [ $? = 0 ] || break; done {code} Trying running the suite in a loop: {code} for i in {1..200}; do echo ITERATION $i; ./build.sh -f ArjunaCore/arjuna/pom.xml test ; [ $? = 0 ] || break; done {code} > LogStoreRecoveryTest hang > ------------------------- > > Key: JBTM-1383 > URL: https://issues.jboss.org/browse/JBTM-1383 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 5.0.0.M2 > Reporter: Michael Musgrove > Assignee: Paul Robinson > Attachments: debug.25494 > > > http://172.17.131.2/job/jbossts-narayana-java6/123 job is stuck running LogStoreRecoveryTest -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1354) JCA recovery race condition

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1354?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1354: ------------------------------------- Problem is normally there is just one recovery manager thread, in the case of JCA we can be invoked by a second thread > JCA recovery race condition > --------------------------- > > Key: JBTM-1354 > URL: https://issues.jboss.org/browse/JBTM-1354 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA, JTA, Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.M2 > > > Evidenced in SimpleIsolatedServers::testSimultaneousRecovery > Basically XATerminatorImple -> SAA::activate() -> XAResourceRecord::restore_state() -> getNewXAResource() -> XARecoveryModule::getNewXAResource() > At this point _xidScans may be none-null but still only partial from the first scan: periodicWorkSecondPass -> bottomUpRecovery -> resourceInitiatedRecoveryForRecoveryHelpers -> xaRecovery > if (_xidScans == null) > _xidScans = new Hashtable<XAResource,RecoveryXids>(); > What I am not sure of is whether we should synchronize bottomUpRecovery and getNewXAResource as that would stop this race condition. Gonna give that a whirl. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1354) JCA recovery race condition

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1354?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-1354: --------------------------------- > JCA recovery race condition > --------------------------- > > Key: JBTM-1354 > URL: https://issues.jboss.org/browse/JBTM-1354 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA, JTA, Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.3, 5.0.0.M2 > > > Evidenced in SimpleIsolatedServers::testSimultaneousRecovery > Basically XATerminatorImple -> SAA::activate() -> XAResourceRecord::restore_state() -> getNewXAResource() -> XARecoveryModule::getNewXAResource() > At this point _xidScans may be none-null but still only partial from the first scan: periodicWorkSecondPass -> bottomUpRecovery -> resourceInitiatedRecoveryForRecoveryHelpers -> xaRecovery > if (_xidScans == null) > _xidScans = new Hashtable<XAResource,RecoveryXids>(); > What I am not sure of is whether we should synchronize bottomUpRecovery and getNewXAResource as that would stop this race condition. Gonna give that a whirl. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1354) JCA recovery race condition

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1354?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1354: -------------------------------- Fix Version/s: 4.17.4 (was: 4.17.3) > JCA recovery race condition > --------------------------- > > Key: JBTM-1354 > URL: https://issues.jboss.org/browse/JBTM-1354 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA, JTA, Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.M2 > > > Evidenced in SimpleIsolatedServers::testSimultaneousRecovery > Basically XATerminatorImple -> SAA::activate() -> XAResourceRecord::restore_state() -> getNewXAResource() -> XARecoveryModule::getNewXAResource() > At this point _xidScans may be none-null but still only partial from the first scan: periodicWorkSecondPass -> bottomUpRecovery -> resourceInitiatedRecoveryForRecoveryHelpers -> xaRecovery > if (_xidScans == null) > _xidScans = new Hashtable<XAResource,RecoveryXids>(); > What I am not sure of is whether we should synchronize bottomUpRecovery and getNewXAResource as that would stop this race condition. Gonna give that a whirl. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1298) Build timeout on SimpleIsolatedServers test

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1298?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1298. --------------------------------- Resolution: Duplicate Issue > Build timeout on SimpleIsolatedServers test > ------------------------------------------- > > Key: JBTM-1298 > URL: https://issues.jboss.org/browse/JBTM-1298 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.M2 > > > See: http://172.17.131.2/job/jbossts-narayana-java7/23/console -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1385) ATS integration SimpleIsolatedServers.testSimultaneousRecover assertion error 5

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1385?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1385: -------------------------------- Fix Version/s: 5.0.0.M2 > ATS integration SimpleIsolatedServers.testSimultaneousRecover assertion error 5 > ------------------------------------------------------------------------------- > > Key: JBTM-1385 > URL: https://issues.jboss.org/browse/JBTM-1385 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.4, 5.0.0.M2 > > > See: http://172.17.131.2/job/jbossts-branch417-EAP61-java6/1525 > Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 37.972 sec <<< FAILURE! > testSimultaneousRecover(com.arjuna.ats.jta.distributed.SimpleIsolatedServers) Time elapsed: 3.358 sec <<< FAILURE! > java.lang.AssertionError: 5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1298) Build timeout on SimpleIsolatedServers test

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1298?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1298: -------------------------------- Fix Version/s: 4.17.4 (was: 4.17.3) > Build timeout on SimpleIsolatedServers test > ------------------------------------------- > > Key: JBTM-1298 > URL: https://issues.jboss.org/browse/JBTM-1298 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.M2 > > > See: http://172.17.131.2/job/jbossts-narayana-java7/23/console -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1298) Build timeout on SimpleIsolatedServers test

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1298?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-1298: --------------------------------- > Build timeout on SimpleIsolatedServers test > ------------------------------------------- > > Key: JBTM-1298 > URL: https://issues.jboss.org/browse/JBTM-1298 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 4.17.3, 5.0.0.M2 > > > See: http://172.17.131.2/job/jbossts-narayana-java7/23/console -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1298) Build timeout on SimpleIsolatedServers test

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1298?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1298: ------------------------------------- http://172.17.131.2/job/btny-pulls-narayana/269/console > Build timeout on SimpleIsolatedServers test > ------------------------------------------- > > Key: JBTM-1298 > URL: https://issues.jboss.org/browse/JBTM-1298 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 4.17.3, 5.0.0.M2 > > > See: http://172.17.131.2/job/jbossts-narayana-java7/23/console -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1387) Java heap space ends while building JBoss AS test suite

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1387?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1387. --------------------------------- Resolution: Done Skip AS test compilation > Java heap space ends while building JBoss AS test suite > ------------------------------------------------------- > > Key: JBTM-1387 > URL: https://issues.jboss.org/browse/JBTM-1387 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.M2 > > > See: > http://172.17.131.2/job/jbossts-branch417-EAP61-skipTests/547 > http://172.17.131.2/job/jbossts-branch417-EAP61-skipTests/548 > http://172.17.131.2/job/jbossts-narayana-skipTests/143 > http://172.17.131.2/job/jbossts-narayana-skipTests/144 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 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 December 2012