August 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2458) Think of the possibility to improve Compensations API with lambdas

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2458?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2458: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > Think of the possibility to improve Compensations API with lambdas > ------------------------------------------------------------------ > > Key: JBTM-2458 > URL: https://issues.jboss.org/browse/JBTM-2458 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Emmanuel suggested to reduce verbosity in Compensations API by making it possible to use lambdas for handler implementation. > We should try to think of the best API changes to introduce that. > We could rewrite MongoDB quickstart to make it easier to visualise the difference. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2460) Expose TransactionListenerRegistry via the SPI

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2460?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2460: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > Expose TransactionListenerRegistry via the SPI > ---------------------------------------------- > > Key: JBTM-2460 > URL: https://issues.jboss.org/browse/JBTM-2460 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > TransactionListenerRegistry is for clients to register for transaction related events and is implemented by the TransactionManager but the SPI does not allow the user to discover the interface which means they have to write unpleasant code like: > {code} > (TransactionListenerRegistry) getTransactionManager(); > {code} > So we need a method in the SPI to get and set an instance of the interface. The setter will be for the container to set it and the getter is for clients to register interest in the events -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2467) REST-AT performance tests fail

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2467?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2467: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > REST-AT performance tests fail > ------------------------------ > > Key: JBTM-2467 > URL: https://issues.jboss.org/browse/JBTM-2467 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The REST-AT tests in the performance repo fail because the deployment to the undertow server used in the tests is failing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2468) xts, jts and rts performance comparison job has failures

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2468?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2468: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > xts, jts and rts performance comparison job has failures > -------------------------------------------------------- > > Key: JBTM-2468 > URL: https://issues.jboss.org/browse/JBTM-2468 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The weekly NCL jenkins job for performance comparison of jts/xts/rts has three issues: > - the throughput is coming out at 0 (I think it is because its very slow but it needs investigating); > - the jts component fails to configure wildfly into jts mode (I have temporarily disabled it in the job config); > - it runs against 9.0.0.Alpha2-SNAPSHOT (so it needs updating to run against the wildfly bi weekly builds) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2476) When a transaction times out, print the stack traces of the threads involved

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2476?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2476: -------------------------------- Fix Version/s: 5.next (was: 5.2.1) > When a transaction times out, print the stack traces of the threads involved > ---------------------------------------------------------------------------- > > Key: JBTM-2476 > URL: https://issues.jboss.org/browse/JBTM-2476 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Would be useful to help understand what the code was doing when the transaction times out. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2472) Move the jboss-as checking to BlackTie build part

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2472?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2472: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Move the jboss-as checking to BlackTie build part > ------------------------------------------------- > > Key: JBTM-2472 > URL: https://issues.jboss.org/browse/JBTM-2472 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently only blacktie uses jboss-as version and requires it to be in sync with the application server. We should move this to that part of the build in order to not prevent other aspects of the build breaking when the version updates: > Move the jboss-as.version from /pom.xml to /blacktie/pom.xml > Move the checking of the jboss-as version from function jboss-as to function blacktie: > https://github.com/jbosstm/narayana/blob/master/scripts/hudson/narayana.s... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2479) Do not run maven rulecheck when -DskipTests is enabled

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2479?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2479: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Do not run maven rulecheck when -DskipTests is enabled > ------------------------------------------------------ > > Key: JBTM-2479 > URL: https://issues.jboss.org/browse/JBTM-2479 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > If you don't provide clean the rule check can easily fail: > {code} > [INFO] Checking 3 byteman scripts in C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes > CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L242951774 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.shutdown(Z)V > exits unaccounted for in block B4 > [ERROR] Checking byteman script rules failed with 1 errors > [ERROR] ERROR : Unexpected exception transforming class com.arjuna.ats.arjuna.coordinator.TransactionReaper using rule "ReaperTestCase3 unlatch reaper and reaper worker" loaded from C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes\reaper.btm line 326 > java.lang.NullPointerException > {code} > So it is advantageous not to run the rulecheck with skipTests as in: > ./build.sh install -DskipTests -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2479) Do not run maven rulecheck when -DskipTests is enabled

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2479?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2479: -------------------------------- Fix Version/s: 5.next > Do not run maven rulecheck when -DskipTests is enabled > ------------------------------------------------------ > > Key: JBTM-2479 > URL: https://issues.jboss.org/browse/JBTM-2479 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > If you don't provide clean the rule check can easily fail: > {code} > [INFO] Checking 3 byteman scripts in C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes > CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1402599109 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L173783788 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L818209618 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1465146431 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1725885575 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1320809135 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L152937115 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L1699637904 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.check()V > CFG.carryForward: unexpected! invalid open enters count for block L242951774 in method com.arjuna.ats.arjuna.coordinator.TransactionReaper.shutdown(Z)V > exits unaccounted for in block B4 > [ERROR] Checking byteman script rules failed with 1 errors > [ERROR] ERROR : Unexpected exception transforming class com.arjuna.ats.arjuna.coordinator.TransactionReaper using rule "ReaperTestCase3 unlatch reaper and reaper worker" loaded from C:\Users\tom\projects\jbosstm\narayana\ArjunaCore\arjuna\target\test-classes\reaper.btm line 326 > java.lang.NullPointerException > {code} > So it is advantageous not to run the rulecheck with skipTests as in: > ./build.sh install -DskipTests -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2455) Re-enable generate of javadoc jar for narayana-full

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2455?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2455: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Re-enable generate of javadoc jar for narayana-full > --------------------------------------------------- > > Key: JBTM-2455 > URL: https://issues.jboss.org/browse/JBTM-2455 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > It seems as part of JBTM-2395 it seems the generation of the uber javadoc jar was accidentally disabled. It should be re-enabled for the next release. > Workaround was to mod the pom during the release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2481) Automate NRP

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2481: ----------------------------------- Summary: Automate NRP Key: JBTM-2481 URL: https://issues.jboss.org/browse/JBTM-2481 Project: JBoss Transaction Manager Issue Type: Task Components: Release Process Reporter: Tom Jenkinson Assignee: Gytis Trikleris Fix For: 5.later There are a number of steps on NRP that could be automated using Jira API. Lets try to do that: https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 4 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 August 2015