March 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1211) Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1211?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-1211. ------------------------------------ Resolution: Done Fixed on master - removing fix for 4.17 since the issue only affects txoj which isn't used in EAP > Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote > ------------------------------------------------------------------------------ > > Key: JBTM-1211 > URL: https://issues.jboss.org/browse/JBTM-1211 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS, Testing, Transaction Core > Affects Versions: 4.16.4 > Reporter: Paul Robinson > Assignee: Michael Musgrove > Fix For: 5.0.0.M3 > > Attachments: jbossts-narayana-java6-ipv6-dualstack.57.tar, jtsremote(1).zip, jtsremote.zip > > Original Estimate: 1 day > Remaining Estimate: 1 day > > See: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java6/232 > {code} > Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote > [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 169.235 sec > {code} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1350) Deadlock in LockManager

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1350?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1350: ----------------------------------- Fix Version/s: (was: 4.17.3) > Deadlock in LockManager > ----------------------- > > Key: JBTM-1350 > URL: https://issues.jboss.org/browse/JBTM-1350 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 5.0.0.M1, 4.17.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.M3 > > Attachments: deadlock_via_intrinsic_lock, deadlock_via_ServerNestedAction, jstack.16785 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > A deadlock can occur whilst calling LockManager.setlock if another thread tries to commit a transaction that has the same lock manager as a participant. The attached java stack dump, jstack.16785, (from test com.hp.mwtests.ts.jts.remote.hammer.DistributedHammer2) shows an example. It shows two threads interacting with a remote HammerObject: > - Thread 1 updates the remote object; > - Thread 2 commits a transaction that has the same HammerObject instance as a participant; > Thread 1 calls setlock on HammerObject which synchronizes on BasicAction.Current() and LockManager.locksHeldLockObject and then activates the object (which triggers an object load from the object store). The activate call tries to lock StateManager.mutex and this is where thread 1 deadlocks. > Meanwhile a commit request is issued which results in Thread 2 running at the same time thread 1 is calling activate. The commit asks HammerObject to prepare and commit. The participant commit asks HammerObject to release any locks it has held (LockManager.releaseAll). This call first tries to lock BasicAction.Current() which is null during commit time (since commit disassociates the transaction from the thread before committing the participants). Instead it locks StateManager.mutex which succeeds. Then it tries to lock LockManager.locksHeldLockObject and that is where Thread 2 deadlocks. > Note that the problem arises because Thread 2 gets null when it calls BasicAction.Current() and instead locks StateManager.mutex. If BasicAction.Current() was not null thread 2 would try to lock it but would not obtain the lock until thread 1 had completed the activate call and released BasicAction.Current() thus allowing thread 2 to continue as normal. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1211) Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1211?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1211: ----------------------------------- Fix Version/s: (was: 4.17.4) > Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote > ------------------------------------------------------------------------------ > > Key: JBTM-1211 > URL: https://issues.jboss.org/browse/JBTM-1211 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS, Testing, Transaction Core > Affects Versions: 4.16.4 > Reporter: Paul Robinson > Assignee: Michael Musgrove > Fix For: 5.0.0.M3 > > Attachments: jbossts-narayana-java6-ipv6-dualstack.57.tar, jtsremote(1).zip, jtsremote.zip > > Original Estimate: 1 day > Remaining Estimate: 1 day > > See: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java6/232 > {code} > Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote > [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 169.235 sec > {code} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1510) QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2#CrashRecovery05_2_Test076

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1510?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1510: -------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2#CrashRecovery05_2_Test076 > ------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1510 > URL: https://issues.jboss.org/browse/JBTM-1510 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.Final > > Attachments: CrashRecovery05_2_Test076.tar.gz, TEST-org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2.txt > > > See: http://172.17.131.2/job/narayana/173/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1510) QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2#CrashRecovery05_2_Test076

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1510?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1510: -------------------------------- Fix Version/s: 5.0.0.M3 (was: 5.0.0.Final) > QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2#CrashRecovery05_2_Test076 > ------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1510 > URL: https://issues.jboss.org/browse/JBTM-1510 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M3 > > Attachments: CrashRecovery05_2_Test076.tar.gz, TEST-org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2.txt > > > See: http://172.17.131.2/job/narayana/173/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1593) Most top level subsystem folders in the quickstart repo are missing README.md files

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1593?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1593: -------------------------------- Description: Top level subsystem folders in the quickstart repo are missing README.md files (except XTS). Use the XTS README.md as an example of what they should look like. I suggest the workload assignments for completing this task as follows: ArjunaCore - Mike ArjunaJTA - Mike ArjunaJTS - Mike atsintegration - Mike ObjectStore - Mike blacktie Amos rest-tx - Mike was: Top level subsystem folders in the quickstart repo are missing README.md files (except XTS). Use the XTS README.md as an example of what they should look like. I suggest the workload assignments for completing this task as follows: ArjunaCore - Mike ArjunaJTA - Mike ArjunaJTS - Mike atsintegration - Mike ObjectStore - Mike blacktie Amos rest-tx - Mike TXBridge Paul TXFramework Paul > Most top level subsystem folders in the quickstart repo are missing README.md files > ----------------------------------------------------------------------------------- > > Key: JBTM-1593 > URL: https://issues.jboss.org/browse/JBTM-1593 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator > Affects Versions: 5.0.0.M2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.Final > > > Top level subsystem folders in the quickstart repo are missing README.md files (except XTS). > Use the XTS README.md as an example of what they should look like. I suggest the workload assignments for completing this task as follows: > ArjunaCore - Mike > ArjunaJTA - Mike > ArjunaJTS - Mike > atsintegration - Mike > ObjectStore - Mike > blacktie Amos > rest-tx - Mike -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1593) Most top level subsystem folders in the quickstart repo are missing README.md files

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1593?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1593: ------------------------------------- I've removed TXFramework and TXBridge from the list as they where moved into XTS for M2. > Most top level subsystem folders in the quickstart repo are missing README.md files > ----------------------------------------------------------------------------------- > > Key: JBTM-1593 > URL: https://issues.jboss.org/browse/JBTM-1593 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator > Affects Versions: 5.0.0.M2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.Final > > > Top level subsystem folders in the quickstart repo are missing README.md files (except XTS). > Use the XTS README.md as an example of what they should look like. I suggest the workload assignments for completing this task as follows: > ArjunaCore - Mike > ArjunaJTA - Mike > ArjunaJTS - Mike > atsintegration - Mike > ObjectStore - Mike > blacktie Amos > rest-tx - Mike -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1593) Most top level subsystem folders in the quickstart repo are missing README.md files

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1593: -------------------------------------- Summary: Most top level subsystem folders in the quickstart repo are missing README.md files Key: JBTM-1593 URL: https://issues.jboss.org/browse/JBTM-1593 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Demonstrator Affects Versions: 5.0.0.M2 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 5.0.0.Final Top level subsystem folders in the quickstart repo are missing README.md files (except XTS). Use the XTS README.md as an example of what they should look like. I suggest the workload assignments for completing this task as follows: ArjunaCore - Mike ArjunaJTA - Mike ArjunaJTS - Mike atsintegration - Mike ObjectStore - Mike blacktie Amos rest-tx - Mike TXBridge Paul TXFramework Paul -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1465) Performance tests using JDBCStore

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1465?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1465: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Performance tests using JDBCStore > --------------------------------- > > Key: JBTM-1465 > URL: https://issues.jboss.org/browse/JBTM-1465 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Performance Testing, Transaction Core > Affects Versions: 4.17.3 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 4.17.4, 5.0.0.M3 > > > Some of the core and txoj performance tests appear to be running against the JDBC object store rather than the default file store. It's possible that this change has been put in place to test the updated JDBC object store, but it should not be the default. It's also possible that it is simply a bug, or inheriting some configuration update from earlier tests. The performance tests should be returned to work against the default file implementation and if necessary new jdbc specific tests added. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1465) Performance tests using JDBCStore

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1465?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1465: -------------------------------- Priority: Minor (was: Major) > Performance tests using JDBCStore > --------------------------------- > > Key: JBTM-1465 > URL: https://issues.jboss.org/browse/JBTM-1465 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Performance Testing, Transaction Core > Affects Versions: 4.17.3 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 4.17.4, 5.0.0.M3 > > > Some of the core and txoj performance tests appear to be running against the JDBC object store rather than the default file store. It's possible that this change has been put in place to test the updated JDBC object store, but it should not be the default. It's also possible that it is simply a bug, or inheriting some configuration update from earlier tests. The performance tests should be returned to work against the default file implementation and if necessary new jdbc specific tests added. -- 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, 3 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 March 2013