December 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3072) Add a test to verify the behaviour of LRA.Type.REQUIRES_NEW combined with LRA.delayClose

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3072?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3072: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > Add a test to verify the behaviour of LRA.Type.REQUIRES_NEW combined with LRA.delayClose > ---------------------------------------------------------------------------------------- > > Key: JBTM-3072 > URL: https://issues.jboss.org/browse/JBTM-3072 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA, Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Add a test that verifies the correct behaviour when a method is annotated with both REQUIRES_NEW and delayClose, ie something like: > {code} > @PUT > @Path(ActivityController.ACCEPT_WORK) > @LRA(value = LRA.Type.REQUIRES_NEW, delayClose = true) > public Response doInNewLRA( ....) {...} > {code} > The expected behaviour is: > {code} > /** > * If called outside a LRA context a new LRA will be created for the > * the duration of the method call and when the call completes it will > * be closed (this behaviour can be overridden using the > * {@link LRA#delayClose} attribute). > * > * If called inside a LRA context it will be suspended and a new LRA > * context will be created for the duration of the call. When the method > * finishes this new LRA will be closed and the original context will be > * resumed. This behaviour can be overridden using the > * {@link LRA#delayClose} attribute) in which case the original LRA > * remains suspended and the new LRA becomes the active one and only > * when that one is terminated will the original context be resumed. > */ > REQUIRES_NEW, > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3073) Do not mandate JAX-RS annotations on @Compensate/@Complete methods

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3073?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3073: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > Do not mandate JAX-RS annotations on @Compensate/@Complete methods > ------------------------------------------------------------------ > > Key: JBTM-3073 > URL: https://issues.jboss.org/browse/JBTM-3073 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Cloned from [https://github.com/eclipse/microprofile-lra/issues/35|http://example.com]: > It is up to the implementation on how the Compensate methods are called. > This could be through JAX-RS calls but this should not be the only way (although an implementation will probably only implement one method). This makes it easier to use the 'events' way of coordination. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2824) Check that the changes for JDK-9 support still build with JDK-8

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2824?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2824. ------------------------------- > Check that the changes for JDK-9 support still build with JDK-8 > --------------------------------------------------------------- > > Key: JBTM-2824 > URL: https://issues.jboss.org/browse/JBTM-2824 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.later > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Critical > Fix For: 5.9.1.Final > > > JBTM-2685 is adding support for building with the JDK-9 compiler using branch https://github.com/jbosstm/narayana/tree/jdk9-experimental > This JIRA is for reporting when the branch fails to build on JDK-8 (currently it is failing because the build is not producing the jar artefact for org.jboss.narayana.jts:narayana-jts-idlj). See CI job http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-jdk-9-jdk-8 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3029) SpecIT.timeLimitRequiredLRA failed on Mac CI

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3029?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3029. ------------------------------- > SpecIT.timeLimitRequiredLRA failed on Mac CI > -------------------------------------------- > > Key: JBTM-3029 > URL: https://issues.jboss.org/browse/JBTM-3029 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.8.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.1.Final > > > Failed on CI run http://172.17.130.4:8083/job/narayana-mac/PROFILE=MAIN,jdk=jdk8.latest,la... > The test does a timed wait on a condition which eventually times out. The test may just need tweaking or alternatively a more sophisticated test may be required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3030) Moving the tomcat-jta to the JWS web-servers repo

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3030?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3030. ------------------------------- > Moving the tomcat-jta to the JWS web-servers repo > ------------------------------------------------- > > Key: JBTM-3030 > URL: https://issues.jboss.org/browse/JBTM-3030 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tomcat > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Major > Fix For: 5.9.1.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3042) API to get detailed LRA information should not include stats type data

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3042?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3042: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > API to get detailed LRA information should not include stats type data > ---------------------------------------------------------------------- > > Key: JBTM-3042 > URL: https://issues.jboss.org/browse/JBTM-3042 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The interface to obtain information about an LRA [1] includes data such as when the LRA was started and ended. This type of information is more appropriate to monitoring and statistics gathering rather than core LRA info. Not all implementations may want to / be able to report these accurately so perhaps move them to an extended optional interface > [1] https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-client/src/ma... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3041) Include a test to run the microprofile-lra TCK

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3041?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3041. ------------------------------- > Include a test to run the microprofile-lra TCK > ---------------------------------------------- > > Key: JBTM-3041 > URL: https://issues.jboss.org/browse/JBTM-3041 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.1.Final > > > The narayana implementation of the LRA spec should include a test to validate that it conforms to the TCK at https://github.com/eclipse/microprofile-lra/tree/master/tck -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3044) Decouple TransactionContext from JNDI

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3044?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3044. ------------------------------- > Decouple TransactionContext from JNDI > ------------------------------------- > > Key: JBTM-3044 > URL: https://issues.jboss.org/browse/JBTM-3044 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Affects Versions: 5.9.0.Final > Reporter: Laird Nelson > Assignee: Laird Nelson > Priority: Major > Fix For: 5.9.1.Final > > > I've submitted a [pull request|https://github.com/jbosstm/narayana/pull/1346] that makes the CDI pieces of the Narayana project play more nicely with dependency injection in general. > There has been a [lengthy discussion|https://developer.jboss.org/thread/278367] of the issues. > [~tomjenkinson] indicated I should file an issue here to track it, so here it is. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3045) JTA CDI regression (or Standalone JTA 1.2 Quickstart failure)

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3045?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3045. ------------------------------- > JTA CDI regression (or Standalone JTA 1.2 Quickstart failure) > ------------------------------------------------------------- > > Key: JBTM-3045 > URL: https://issues.jboss.org/browse/JBTM-3045 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Priority: Critical > Fix For: 5.9.1.Final > > > The recent changes to our JTA CDI support (https://issues.jboss.org/browse/JBTM-3044) have either caused a regression or the Standalone JTA 1.2 Quickstart needs updating. The failure is: > {quote} > testMandatoryTransactionWithExistingTransaction(org.jboss.narayana.quickstarts.jta.TestCase) Time elapsed: 0.536 sec <<< ERROR! > javax.enterprise.inject.CreationException: Not a compound name: TransactionManager > {quote} > See for example CI run http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-quickstarts/159/c... > If the issue does turn out to be a regression then the priority needs to be marked as Critical. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3048) Some AbstractRecord test classes return invalid TwoPhaseOutcome values

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3048?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3048. ------------------------------- > Some AbstractRecord test classes return invalid TwoPhaseOutcome values > ---------------------------------------------------------------------- > > Key: JBTM-3048 > URL: https://issues.jboss.org/browse/JBTM-3048 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.9.1.Final > > > The test classes > arjuna/tests/classes/com/hp/mwtests/ts/arjuna/atomicaction/AtomicActionUnitTest.java > arjuna/tests/classes/com/hp/mwtests/ts/arjuna/atomicaction/TxStatsSystemErrorUnitTest.java > contain inner class implementations of AbstractRecord that return invalid values from the action lifecycle methods. For example: > {code} > public int topLevelCommit() {return 0;} > {code} > which maps to TwoPhaseOutcome.PREPARE_OK which is wrong. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 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 December 2018