November 2012 - jbossts-issues - Jboss List Archives

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

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1298: ----------------------------------- Summary: 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: 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, 12 months

2
13
0 / 0

[JBoss JIRA] (JBTM-939) Fix intermittant qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2

by Tom Jenkinson (Created) (JIRA)

Fix intermittant qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 --------------------------------------------------------------------------------------------------- Key: JBTM-939 URL: https://issues.jboss.org/browse/JBTM-939 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Tom Jenkinson Fix For: 4.15.x, 5.0.0.M2 Assuming failure in test rather than failed test: >>>>> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 >>>>> [junit] Tests run: 50, Failures: 1, Errors: 0, Time elapsed: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

5
29
0 / 0

[JBoss JIRA] (JBTM-1349) LogStoreRecoveryTest failure

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1349: -------------------------------------- Summary: LogStoreRecoveryTest failure Key: JBTM-1349 URL: https://issues.jboss.org/browse/JBTM-1349 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Common Affects Versions: 4.17.3 Environment: Run the test on a fast machine Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.17.3 http://172.17.131.2/job/jbossts-branch417-EAP61-java6/1500/ Jonathan root caused the issue as being due to the byteman script "RULE done log purge" signalling the "RULE LogStore.purged" and then setting the flag "LogStore done purge". But the rule that checks the flag "LogStore done purge" runs before the flag is set. The fix is to set the flag and then do the signal. -- 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, 12 months

2
6
0 / 0

[JBoss JIRA] (JBTM-1344) org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins)

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1344: ----------------------------------- Summary: org.jboss.jbossts.txbridge.tests.outbound.junit.OutboundBasicTests Timeout (900mins) Key: JBTM-1344 URL: https://issues.jboss.org/browse/JBTM-1344 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: TxBridge Reporter: Paul Robinson Assignee: Paul Robinson Priority: Minor Fix For: 4.17.3, 5.0.0.M2 See: http://172.17.131.2/job/jbossts-narayana-java6/81/ -- 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, 12 months

2
3
0 / 0

[JBoss JIRA] (JBTM-1305) Quickstart pull job config hard codes a specifc version of the app server so pulls for 417 test against 500 AS

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1305: ----------------------------------- Summary: Quickstart pull job config hard codes a specifc version of the app server so pulls for 417 test against 500 AS Key: JBTM-1305 URL: https://issues.jboss.org/browse/JBTM-1305 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 4.17.1, 5.0.0.M2 -- 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, 12 months

1
5
0 / 0

[JBoss JIRA] (JBTM-1329) test(com.hp.mwtests.ts.jts.local.orbsetup.ORBSetupTest): Error: org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 208 completed: No

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1329: ----------------------------------- Summary: test(com.hp.mwtests.ts.jts.local.orbsetup.ORBSetupTest): Error: org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 208 completed: No Key: JBTM-1329 URL: https://issues.jboss.org/browse/JBTM-1329 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Michael Musgrove Fix For: 5.0.0.M2, 4.17.3 http://172.17.131.2/job/jbossts-branch417-EAP61-ipv6-dualstack/107/ -- 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, 12 months

2
2
0 / 0

[JBoss JIRA] (JBTM-1238) Intermittent failure Rest-TX SpecTest

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1238: ----------------------------------- Summary: Intermittent failure Rest-TX SpecTest Key: JBTM-1238 URL: https://issues.jboss.org/browse/JBTM-1238 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 4.17.0 http://172.17.131.2/job/narayana-pulls/104/ -- 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, 12 months

3
14
0 / 0

[JBoss JIRA] (JBTM-1304) Quickstarts readmes reference JBOSS_HOME rather than APP_SERVER_HOME

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1304: ----------------------------------- Summary: Quickstarts readmes reference JBOSS_HOME rather than APP_SERVER_HOME Key: JBTM-1304 URL: https://issues.jboss.org/browse/JBTM-1304 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Reporter: Tom Jenkinson Assignee: Tom Jenkinson -- 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, 12 months

1
3
0 / 0

[JBoss JIRA] (JBTM-1356) Parallel prepare implementation does not handle LRCO correctly

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1356: -------------------------------------- Summary: Parallel prepare implementation does not handle LRCO correctly Key: JBTM-1356 URL: https://issues.jboss.org/browse/JBTM-1356 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 5.0.0.M1 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Optional Fix For: 5.0.0.M3 We implement LRCO by putting the 1PC aware resources at the end of the prepared list. Prepare is implemented by preparing each record in the prepared list and then stopping if any prepare fails. This means that if any 2PC aware resource fails then the 1PC resources are not get asked to prepare/commit. The parallel prepare implementation prepares all participants in separate threads which is wrong - it should prepare 2PC aware participants first and if they vote commit should the 1PC resources be asked to commit. -- 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, 12 months

1
1
0 / 0

[JBoss JIRA] (JBTM-1293) ATBridgeTest#testSimple counter isn't incrimented

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1293: ----------------------------------- Summary: ATBridgeTest#testSimple counter isn't incrimented Key: JBTM-1293 URL: https://issues.jboss.org/browse/JBTM-1293 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 See: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java7/21/... {code} @Test public void testSimple() throws Exception { ut.begin(); client.incrementCounter(1); ut.commit(); ut.begin(); int counter = client.getCounter(); ut.commit(); Assert.assertEquals(1, counter); } {code} Even though the first transaction should have committed an update to the counter, it is still set to zero in the second transaction. This happens intermittently (once so far). It also happened on Beacon which is notorious for test failures caused by things going slowly. I would suspect that the bridged JTA transaction in the first transaction hasn't quite finished the commit when the second transaction is begun. If the WS-AT coordinator sends an async commit to the participants and an async committed to the client, then this problem could happen if the client's 'committed' is received before the participant's 'commit' message. To verify this we need to check that the coordinator sends an async (@OneWay) commit message to the participant. In which case the simplest solution is to add a 5sec delay between the two transactions. We should also look for other tests that may be affected. -- 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

12 years

3
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2012