August 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1040) IL: An apparent infinite recursive loop (IL_INFINITE_RECURSIVE_LOOP)

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1040?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1040: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) > IL: An apparent infinite recursive loop (IL_INFINITE_RECURSIVE_LOOP) > -------------------------------------------------------------------- > > Key: JBTM-1040 > URL: https://issues.jboss.org/browse/JBTM-1040 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Amos Feng > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M5 > > > 1.XTS/WSAS > com.arjuna.mw.wsas.completionstatus.Unknown Line 52 > There is an apparent infinite recursive loop in com.arjuna.mw.wsas.completionstatus.Unknown.equals(Object) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1041) IP: A parameter is dead upon entry to a method but overwritten (IP_PARAMETER_IS_DEAD_BUT_OVERWRITTEN)

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1041?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1041: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) > IP: A parameter is dead upon entry to a method but overwritten (IP_PARAMETER_IS_DEAD_BUT_OVERWRITTEN) > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-1041 > URL: https://issues.jboss.org/browse/JBTM-1041 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Amos Feng > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M5 > > > 1.XTS/WSCF > com.arjuna.mwlabs.wscf.model.sagas.arjunacore.ParticipantRecord Line 540 > The parameter toDelete to com.arjuna.mwlabs.wscf.model.sagas.arjunacore.ParticipantRecord.remove(AbstractRecord) is dead upon entry but overwritten > 2.XTS/WSCF > com.arjuna.mwlabs.wscf.model.twophase.arjunacore.ParticipantRecord Line 523 > The parameter toDelete to com.arjuna.mwlabs.wscf.model.twophase.arjunacore.ParticipantRecord.remove(AbstractRecord) is dead upon entry but overwritten -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-855) Create an example showing integration with Tomcat and Spring

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.s... ] Gytis Trikleris updated JBTM-855: --------------------------------- Fix Version/s: 6.0.0.Final (was: 5.0.0.Final) > Create an example showing integration with Tomcat and Spring > ------------------------------------------------------------ > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 6.0.0.Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Simple example showing TS in use by tomcat and spring -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1474) Update "wsat-jta-multi_service" quickstart to use new APIs

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1474?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1474: -------------------------------- Component/s: Demonstrator > Update "wsat-jta-multi_service" quickstart to use new APIs > ---------------------------------------------------------- > > Key: JBTM-1474 > URL: https://issues.jboss.org/browse/JBTM-1474 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, TxBridge, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1763) Consider running the QA tests in parrallel

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1763?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1763: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) > Consider running the QA tests in parrallel > ------------------------------------------ > > Key: JBTM-1763 > URL: https://issues.jboss.org/browse/JBTM-1763 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M5 > > > The QA tests currently take 5hrs to run per orb. This constitutes 83% of our CI run time. > My understanding is that the time is mostly taken up in Thread.sleep. The test times range from 1 to 99seconds. So there are no major hotspots. The problem is that there are so many tests. > I suspect we could run these tests in parallel to make better utilisation of resources. > The tests don't run in an AS, but they do acquire ports. There may be other restrictions that make running them in parallel hard or impossible. > It would be easier to simply carve up the tests into, say 5 parts per orb and have CI do the parallelism. However, this will consume more CI nodes than if we ran them in parallel on a single node. > I think it would be worth investigating if we can run the tests in n batches (say n=10 initially, but should be configurable). Where each batch runs with a different port configuration. This may prove too disruptive to the tests, > and also more bother than it is worth. Maybe we could do an initial investigation to see if this has legs? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1473) Update "wsat-jta-multi_hop" quickstart to use new APIs

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1473?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1473: -------------------------------- Component/s: Demonstrator > Update "wsat-jta-multi_hop" quickstart to use new APIs > ------------------------------------------------------ > > Key: JBTM-1473 > URL: https://issues.jboss.org/browse/JBTM-1473 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, TxBridge, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1444) Review the logging in XTS when WS-AT participants throw Exceptions in commit or rollback

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1444?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1444: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) > Review the logging in XTS when WS-AT participants throw Exceptions in commit or rollback > ---------------------------------------------------------------------------------------- > > Key: JBTM-1444 > URL: https://issues.jboss.org/browse/JBTM-1444 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Priority: Minor > Labels: assign > Fix For: 5.0.0.M5 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Check what happens when each possible Exception is thrown from a WS-AT participant's commit or Rollback method. > For each case consider whether enough logging is provided. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1808) Investigate why QA tests take 5hrs to run per ORB

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1808?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1808: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.Final) > Investigate why QA tests take 5hrs to run per ORB > ------------------------------------------------- > > Key: JBTM-1808 > URL: https://issues.jboss.org/browse/JBTM-1808 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System, Testing > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M5 > > > Our full build and test suite takes 12hrs to run. This is causing severe strain on our CI resources. > Out of this 12hrs, 10hrs is consumed by the QA test suite (5hrs per orb). It would be good to understand where this time is spent so that we can hopefully bring the test time down. > If there is no reasonable way to bring the timing down, we could chop the tests up into 5 groups (per orb) taking 1hr each. This would make better use of our CI cluster during quiet periods, but will not eleviate the load during busy periods. It is also likely to be a poor usage of resources as I suspect the CPU utilisation of each job will be low. > I suspect the problem is that we have a lot of Thread.sleeps in the tests. Therefore we are likely to see long tests with low resource (CPU) utilisation. However, further investigation is required to understand where the time is spent. > As an initial investigation, it would be good to profile the CPU utilisation on one of the CI nodes (take it offline) whilst running these tests. Also, it would be handy to find out how much time is spent in a Thread.sleep call (assuming that is where the time is spent). > My understanding is that Thread.sleep is used to wait for certain background tasks to complete. It's likely that Byteman could be used to replace the sleeps. However, due to the number of tests this may not be feasible. Alternatively, we may discover that there is a common set of Byteman rules that could be applied to the majority of tests, which may prove "good enough". > Also, we may be able to run these tests in parallel. This could drive up CPU utilisation, but would probably also interfere with the timings of the tests meaning that the current thread.sleeps are no longer adequate. > To summarise, this is a general task to investigate why the tests take so long and to also come up with some candidate solutions to bring the total test duration down. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1873) Create quickstart showing new features implemented with @Compensatable

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1873?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1873: ---------------------------------- Priority: Minor (was: Major) > Create quickstart showing new features implemented with @Compensatable > ---------------------------------------------------------------------- > > Key: JBTM-1873 > URL: https://issues.jboss.org/browse/JBTM-1873 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M5 > > Original Estimate: 4 hours > Time Spent: 3 hours > Remaining Estimate: 1 hour > > Show main features provided by @Compensatable annotation: dontCancelOn, cancelOn, compensation types. > Reuse Paul's quickstart JBTM-1682. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1885) RTS InboundBridgeTestCase failures

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1885?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1885: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > RTS InboundBridgeTestCase failures > ---------------------------------- > > Key: JBTM-1885 > URL: https://issues.jboss.org/browse/JBTM-1885 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST, Testing > Affects Versions: 5.0.0.M4 > Reporter: Amos Feng > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5 > > > {noformat} > Results : > Failed tests: testRollbackWithTwoParticipants(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1> > testCommit(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1> > testRollback(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): expected:<0> but was:<1> > Tests in error: > testRollbackWithTwoParticipants(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): Unexpected status. Expected 200 got 500 > testRollback(org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeTestCase): Unexpected status. Expected 200 got 500 > {noformat} > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/227/TESTS=MAIN,jd... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/233/TESTS=MAIN,jd... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/234/TESTS=BLACKTI... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/235/TESTS=BLACKTI... -- 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, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2013