October 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 Michael Musgrove (Jira)

Michael Musgrove created JBTM-3072: -------------------------------------- Summary: 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 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3067) Build and run the narayana with JDK-11

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3067?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3067: -------------------------------- Priority: Critical (was: Major) > Build and run the narayana with JDK-11 > -------------------------------------- > > Key: JBTM-3067 > URL: https://issues.jboss.org/browse/JBTM-3067 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > > The jdk-11 could be downloaded from https://jdk.java.net/11/ and the most important feature that impacts us is [JEP 320: Remove the Java EE and CORBA Modules|https://openjdk.java.net/jeps/320] > The CI job is http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-jdk-11/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3067) Build and run the narayana with JDK-11

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3067?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-3067: ------------------------------------- I added the linux build to the ci-report-generator, once the Windows build is available we need to add it too: https://github.com/jbosstm/ci-report-generator/commit/cb1f736821781d848ab... > Build and run the narayana with JDK-11 > -------------------------------------- > > Key: JBTM-3067 > URL: https://issues.jboss.org/browse/JBTM-3067 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Major > > The jdk-11 could be downloaded from https://jdk.java.net/11/ and the most important feature that impacts us is [JEP 320: Remove the Java EE and CORBA Modules|https://openjdk.java.net/jeps/320] > The CI job is http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-jdk-11/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3068) Byteman can not submit or remove the scripts when running TestCommitMarkableResourceFailActivate

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3068?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-3068: ----------------------------------- Assignee: Tom Jenkinson (was: Amos Feng) > Byteman can not submit or remove the scripts when running TestCommitMarkableResourceFailActivate > ------------------------------------------------------------------------------------------------ > > Key: JBTM-3068 > URL: https://issues.jboss.org/browse/JBTM-3068 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA, Testing > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Minor > > {code} > [ERROR] testFailAfterPrepare(com.hp.mwtests.ts.jta.commitmarkable.TestCommitMarkableResourceFailActivate) Time elapsed: 2.782 s <<< ERROR! > java.lang.Exception: > The remote byteman agent reported an error: > ERROR failed to find loaded rule with name Fail first phase2Commit > ERROR failed to find loaded rule with name Return not inflight > ERROR No rule scripts to remove > at org.jboss.byteman.agent.submit.Submit$Comm.readResponse(Submit.java:966) > at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:790) > at org.jboss.byteman.agent.submit.Submit.deleteScripts(Submit.java:697) > at org.jboss.byteman.agent.submit.Submit.deleteRulesFromFiles(Submit.java:649) > at org.jboss.byteman.contrib.bmunit.BMUnit.unloadScriptFile(BMUnit.java:259) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$7.evaluate(BMUnitRunner.java:296) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:263) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:97) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3068) Byteman can not submit or remove the scripts when running TestCommitMarkableResourceFailActivate

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3068?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3068. ------------------------------- Resolution: Done > Byteman can not submit or remove the scripts when running TestCommitMarkableResourceFailActivate > ------------------------------------------------------------------------------------------------ > > Key: JBTM-3068 > URL: https://issues.jboss.org/browse/JBTM-3068 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA, Testing > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Minor > > {code} > [ERROR] testFailAfterPrepare(com.hp.mwtests.ts.jta.commitmarkable.TestCommitMarkableResourceFailActivate) Time elapsed: 2.782 s <<< ERROR! > java.lang.Exception: > The remote byteman agent reported an error: > ERROR failed to find loaded rule with name Fail first phase2Commit > ERROR failed to find loaded rule with name Return not inflight > ERROR No rule scripts to remove > at org.jboss.byteman.agent.submit.Submit$Comm.readResponse(Submit.java:966) > at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:790) > at org.jboss.byteman.agent.submit.Submit.deleteScripts(Submit.java:697) > at org.jboss.byteman.agent.submit.Submit.deleteRulesFromFiles(Submit.java:649) > at org.jboss.byteman.contrib.bmunit.BMUnit.unloadScriptFile(BMUnit.java:259) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$7.evaluate(BMUnitRunner.java:296) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:263) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:97) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3068) Byteman can not submit or remove the scripts when running TestCommitMarkableResourceFailActivate

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3068?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-3068: ------------------------------------- To workaround it I have changed the JDK9 job to run _after_ the normal job and removed polling. > Byteman can not submit or remove the scripts when running TestCommitMarkableResourceFailActivate > ------------------------------------------------------------------------------------------------ > > Key: JBTM-3068 > URL: https://issues.jboss.org/browse/JBTM-3068 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA, Testing > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > {code} > [ERROR] testFailAfterPrepare(com.hp.mwtests.ts.jta.commitmarkable.TestCommitMarkableResourceFailActivate) Time elapsed: 2.782 s <<< ERROR! > java.lang.Exception: > The remote byteman agent reported an error: > ERROR failed to find loaded rule with name Fail first phase2Commit > ERROR failed to find loaded rule with name Return not inflight > ERROR No rule scripts to remove > at org.jboss.byteman.agent.submit.Submit$Comm.readResponse(Submit.java:966) > at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:790) > at org.jboss.byteman.agent.submit.Submit.deleteScripts(Submit.java:697) > at org.jboss.byteman.agent.submit.Submit.deleteRulesFromFiles(Submit.java:649) > at org.jboss.byteman.contrib.bmunit.BMUnit.unloadScriptFile(BMUnit.java:259) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$7.evaluate(BMUnitRunner.java:296) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:263) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:97) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3068) Byteman can not submit or remove the scripts when running TestCommitMarkableResourceFailActivate

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3068?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-3068: ------------------------------------- I think it is because they were running at identical times 16-Oct-2018 00:00 and interfered with each other. The reason catelyn can run two jobs simulateously is to allow us to send the kill commands but it seems to cause conflicts like this > Byteman can not submit or remove the scripts when running TestCommitMarkableResourceFailActivate > ------------------------------------------------------------------------------------------------ > > Key: JBTM-3068 > URL: https://issues.jboss.org/browse/JBTM-3068 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA, Testing > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > {code} > [ERROR] testFailAfterPrepare(com.hp.mwtests.ts.jta.commitmarkable.TestCommitMarkableResourceFailActivate) Time elapsed: 2.782 s <<< ERROR! > java.lang.Exception: > The remote byteman agent reported an error: > ERROR failed to find loaded rule with name Fail first phase2Commit > ERROR failed to find loaded rule with name Return not inflight > ERROR No rule scripts to remove > at org.jboss.byteman.agent.submit.Submit$Comm.readResponse(Submit.java:966) > at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:790) > at org.jboss.byteman.agent.submit.Submit.deleteScripts(Submit.java:697) > at org.jboss.byteman.agent.submit.Submit.deleteRulesFromFiles(Submit.java:649) > at org.jboss.byteman.contrib.bmunit.BMUnit.unloadScriptFile(BMUnit.java:259) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$7.evaluate(BMUnitRunner.java:296) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$6.evaluate(BMUnitRunner.java:263) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.byteman.contrib.bmunit.BMUnitRunner$1.evaluate(BMUnitRunner.java:97) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2832) Blacktie TestTPGetRely::test_tpgetrply_with_TPGETANY fail

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2832?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2832: -------------------------------- Attachment: CIfailure.zip > Blacktie TestTPGetRely::test_tpgetrply_with_TPGETANY fail > --------------------------------------------------------- > > Key: JBTM-2832 > URL: https://issues.jboss.org/browse/JBTM-2832 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.later > > Attachments: CIfailure.zip > > > [exec] 1) test: TestTPGetRply::test_tpgetrply_with_TPGETANY (F) line: 272 C:\hudson\workspace\narayana-catelyn\blacktie\xatmi\src\test\cpp\TestTPGetRply.cxx > [exec] assertion failed > [exec] - Expression: _w12pq_u > [exec] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 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 reassigned JBTM-2824: ----------------------------------- Assignee: Amos Feng (was: Michael Musgrove) > 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: Major > Fix For: 5.later > > > 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, 6 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 updated JBTM-2824: -------------------------------- Priority: Critical (was: Major) > 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.later > > > 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, 6 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 October 2018