February 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1368) Allow multiple JDBC Object Store jobs to run concurrently by using a table prefix (perhaps the job name)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1368?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1368: -------------------------------- Summary: Allow multiple JDBC Object Store jobs to run concurrently by using a table prefix (perhaps the job name) (was: Allow multiple JDBC Object Store jobs using a table prefix of the job name) > Allow multiple JDBC Object Store jobs to run concurrently by using a table prefix (perhaps the job name) > -------------------------------------------------------------------------------------------------------- > > Key: JBTM-1368 > URL: https://issues.jboss.org/browse/JBTM-1368 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Tom Jenkinson > Assignee: Ondřej Chaloupka > Fix For: 4.17.4, 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1313) Performance related work that involves other products should be in a separate repository

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1313?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1313: -------------------------------- Issue Type: Task (was: Feature Request) > Performance related work that involves other products should be in a separate repository > ------------------------------------------------------------------------------------------ > > Key: JBTM-1313 > URL: https://issues.jboss.org/browse/JBTM-1313 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator, Performance Testing > Affects Versions: 5.0.0.M1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.M3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Any performance related activities done by the dev team that require installation of other transaction managers should done a repo that is separate from the main narayana repo. Currently this includes: > - some changes to the jts quickstart > - the performance harness in qa/tests/product -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1368) Consider allowing multiple JDBC Object Store jobs using a table prefix of the job name

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1368?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1368: -------------------------------- Issue Type: Task (was: Feature Request) > Consider allowing multiple JDBC Object Store jobs using a table prefix of the job name > -------------------------------------------------------------------------------------- > > Key: JBTM-1368 > URL: https://issues.jboss.org/browse/JBTM-1368 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Tom Jenkinson > Assignee: Ondřej Chaloupka > Fix For: 4.17.4, 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-731) refactor qa tests to reduce code duplication

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-731?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-731: ------------------------------- Issue Type: Task (was: Feature Request) > refactor qa tests to reduce code duplication > -------------------------------------------- > > Key: JBTM-731 > URL: https://issues.jboss.org/browse/JBTM-731 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.10.0 > Reporter: Jonathan Halliday > Assignee: Ondřej Chaloupka > > The qa tests include a massive about of almost but not quite identical code. Refactor to reduce duplication. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1486) Prepare a blog post for XTS default context propagation

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1486?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1486: -------------------------------- Issue Type: Task (was: Feature Request) > Prepare a blog post for XTS default context propagation > -------------------------------------------------------- > > Key: JBTM-1486 > URL: https://issues.jboss.org/browse/JBTM-1486 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, TxBridge, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 4 hours > Time Spent: 1 hour, 30 minutes > Remaining Estimate: 2 hours, 30 minutes > > Describing JBTM-1447 and JBTM-986. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1487) TXBridge 4.17 branch quickstart has 5.0.0.M2-SNAPSHOT dependencies

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1487?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1487: -------------------------------- Issue Type: Bug (was: Feature Request) > TXBridge 4.17 branch quickstart has 5.0.0.M2-SNAPSHOT dependencies > ------------------------------------------------------------------ > > Key: JBTM-1487 > URL: https://issues.jboss.org/browse/JBTM-1487 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator, TxBridge, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 4.17.4 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > See: > https://github.com/jbosstm/quickstart/blob/4.17/TXBridge/wsat-jta-multi_h... > Check for others. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1463) Allow pull requests to test pull requests for the jbosstm fork of jboss-as

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1463?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1463: -------------------------------- Issue Type: Task (was: Feature Request) > Allow pull requests to test pull requests for the jbosstm fork of jboss-as > -------------------------------------------------------------------------- > > Key: JBTM-1463 > URL: https://issues.jboss.org/browse/JBTM-1463 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 5.0.0.Final > > > to allow changes to our repo and to pull in changes we need to AS7 but not require those changes to be pushed to 5_BRANCH until they are tested -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1391) Prepare a blog post to introduce the TXFramework

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1391?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1391: -------------------------------- Issue Type: Task (was: Feature Request) > Prepare a blog post to introduce the TXFramework > ------------------------------------------------ > > Key: JBTM-1391 > URL: https://issues.jboss.org/browse/JBTM-1391 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > Original Estimate: 2 days > Time Spent: 4 hours, 40 minutes > Remaining Estimate: 1 day, 4 hours > -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1147) Refactor ParticipantCompletion recovery tests to remove duplicate rules

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1147?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1147: -------------------------------- Issue Type: Task (was: Enhancement) > Refactor ParticipantCompletion recovery tests to remove duplicate rules > ----------------------------------------------------------------------- > > Key: JBTM-1147 > URL: https://issues.jboss.org/browse/JBTM-1147 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Affects Versions: 4.16.4, 5.0.0.M1 > Reporter: Paul Robinson > Assignee: Ondřej Chaloupka > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > The Byteman rules for the participant completion XTS recovery tests have many rules that are almost duplicates of each other. For example: > The following rules in BACrashDuringCommit could be refactored into a single rule > {code} > ##################################################################### > # Setup counter MultiParticipantParticipantCompletionParticipantCloseTest > # > RULE setup counter MultiParticipantParticipantCompletionParticipantCloseTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseTest > METHOD run() > AT ENTRY > IF TRUE > DO debug("creating counter and rendezvous"), > createCounter("closes", 3), > createRendezvous("closes-complete", 2) > ENDRULE > ##################################################################### > # Setup counter MultiParticipantCoordinatorCompletionParticipantCloseTest > # > RULE setup counter MultiParticipantCoordinatorCompletionParticipantCloseTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseAndExitTest > METHOD run() > AT ENTRY > IF TRUE > DO debug("creating counter and rendezvous"), > createCounter("closes", 3), > createRendezvous("closes-complete", 2) > ENDRULE > ##################################################################### > # Setup counter MultiServiceParticipantCompletionParticipantCloseTest > # > RULE setup counter MultiServiceParticipantCompletionParticipantCloseTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseTest > METHOD run() > AT ENTRY > IF TRUE > DO debug("creating counter and rendezvous"), > createCounter("closes", 3), > createRendezvous("closes-complete", 2) > ENDRULE > ##################################################################### > # Setup counter MultiServiceParticipantCompletionParticipantCloseAndExitTest > # > RULE setup counter MultiServiceParticipantCompletionParticipantCloseAndExitTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseAndExitTest > METHOD run() > AT ENTRY > IF TRUE > DO debug("creating counter and rendezvous"), > createCounter("closes", 3), > createRendezvous("closes-complete", 2) > ENDRULE > {code} > These can be re-factored in to a rule like this: > {code} > RULE setup counter > INTERFACE org.jboss.jbossts.xts.servicetests.test.XTSServiceTest > METHOD run() > AT ENTRY > IF $0.getClass().getName().contains("ParticipantCompletionParticipant") > DO debug("creating counter and rendezvous"), > createCounter("closes", 3), > createRendezvous("closes-complete", 2) > ENDRULE > {code} > This assumes that we have the same numbers for each use of: > {code} > createCounter("closes", 3), > createRendezvous("closes-complete", 2) > {code} > Which is *usually* the case: > {code} > grep -r createCounter\(\"closes\" . > ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./src/test/resources/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./src/test/resources/scripts/BACrashDuringOnePhaseCommit.txt: createCounter("closes", 1), > ./src/test/resources/scripts/BASubordinateCrashDuringCommit.txt: createCounter("closes", 3), > ./src/test/resources/scripts/BASubordinateCrashDuringComplete.txt: createCounter("closes", 3), > ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./target/test-classes/scripts/BACrashDuringCommit.txt: createCounter("closes", 3), > ./target/test-classes/scripts/BACrashDuringOnePhaseCommit.txt: createCounter("closes", 1), > ./target/test-classes/scripts/BASubordinateCrashDuringCommit.txt: createCounter("closes", 3), > ./target/test-classes/scripts/BASubordinateCrashDuringComplete.txt: createCounter("closes", 3), > {code} > Maybe we just override the rule for the one exception. Ideas for what to do here are to be investigated. > Also, the following similar rules are also present in this file: > {code} > ##################################################################### > # Wait on Rendezvous before calling uba.close() on MultiServiceParticipantCompletionParticipantCloseTest > # > RULE wait for closes MultiParticipantParticipantCompletionParticipantCloseTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseTest > METHOD run() > AT CALL UserBusinessActivity.close() > IF TRUE > DO debug("waiting to call close"), > rendezvous("closes-complete"), > debug("rendezvous complete, calling close") > ENDRULE > ##################################################################### > # Wait on Rendezvous before calling uba.close() on MultiParticipantParticipantCompletionParticipantCloseAndExitTest > # > RULE wait for closes MultiParticipantParticipantCompletionParticipantCloseAndExitTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiParticipantParticipantCompletionParticipantCloseAndExitTest > METHOD run() > AT CALL UserBusinessActivity.close() > IF TRUE > DO debug("waiting to call close"), > rendezvous("closes-complete"), > debug("rendezvous complete, calling close") > ENDRULE > ##################################################################### > # Wait on Rendezvous before calling uba.close() on MultiServiceParticipantCompletionParticipantCloseTest > # > RULE wait for closes MultiServiceParticipantCompletionParticipantCloseTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseTest > METHOD run() > AT CALL UserBusinessActivity.close() > IF TRUE > DO debug("waiting to call close"), > rendezvous("closes-complete"), > debug("rendezvous complete, calling close") > ENDRULE > ##################################################################### > # Wait on Rendezvous before calling uba.close() on MultiServiceParticipantCompletionParticipantCloseAndExitTest > # > RULE wait for closes MultiServiceParticipantCompletionParticipantCloseAndExitTest > CLASS org.jboss.jbossts.xts.servicetests.test.ba.MultiServiceParticipantCompletionParticipantCloseAndExitTest > METHOD run() > AT CALL UserBusinessActivity.close() > IF TRUE > DO debug("waiting to call close"), > rendezvous("closes-complete"), > debug("rendezvous complete, calling close") > ENDRULE > {code} > Which could be replaced with something like this: > {code} > RULE wait for closes > INTERFACE org.jboss.jbossts.xts.servicetests.test.XTSServiceTest > METHOD run() > AT CALL UserBusinessActivity.close() > IF $0.getClass().getName().contains("ParticipantCompletionParticipant") > DO debug("waiting to call close"), > rendezvous("closes-complete"), > debug("rendezvous complete, calling close") > ENDRULE > {code} > We could also re-factor these two rules out into a separate Byteman script and add it to all tests that need it. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1442) Prepare a blog post to announce M2

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1442?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1442: -------------------------------- Issue Type: Task (was: Feature Request) > Prepare a blog post to announce M2 > ---------------------------------- > > Key: JBTM-1442 > URL: https://issues.jboss.org/browse/JBTM-1442 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M2 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > -- 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, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2013