January 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3226) Byteman rule check failure with version 4.0.9

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3226?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3226: ----------------------------------- Fix Version/s: 5.10.2.Final (was: 5.10.1.Final) > Byteman rule check failure with version 4.0.9 > --------------------------------------------- > > Key: JBTM-3226 > URL: https://issues.redhat.com/browse/JBTM-3226 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.10.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.10.2.Final > > > Our byteman scripts fail rule checking when using byteman version 4.0.9: > {quote} > [ERROR] Failed to execute goal org.jboss.byteman:byteman-rulecheck-maven-plugin:4.0.9:rulecheck (rulecheck) on project arjuna: Execution rulecheck of goal org.jboss.byteman:byteman-rulecheck-maven-plugin:4.0.9:r > ulecheck failed.: NullPointerException -> [Help 1] > [ERROR] > {quote} > The byteman bug report is issue https://issues.jboss.org/browse/BYTEMAN-392 > The byteman upgrade was introduced by pull request 1530 (https://github.com/jbosstm/narayana/pull/1530) > The issue occurs whenever a byteman script contains more that one rule (so the workaround is to only have single rule scripts). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3231) LRA recovery test fails after restart on JDK11

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3231?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3231: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done PR passed so resolving for now. If the crash tests fail again then we can reopen this PR. > LRA recovery test fails after restart on JDK11 > ---------------------------------------------- > > Key: JBTM-3231 > URL: https://issues.redhat.com/browse/JBTM-3231 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.10.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > CI testing: > LRACoordinatorTestCase=testRecovery2 fails to restart the container after crashing via byteman on JDK11. Seems to be intermittent on Amsterdam CI and more consistent on Upshift, for example: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/552/ > https://ci-master-jenkins-csb-narayana.cloud.paas.psi.redhat.com/job/nara... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3231) LRA recovery test fails after restart on JDK11

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3231?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3231: ----------------------------------- Fix Version/s: 5.10.2.Final (was: 5.next) > LRA recovery test fails after restart on JDK11 > ---------------------------------------------- > > Key: JBTM-3231 > URL: https://issues.redhat.com/browse/JBTM-3231 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.10.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.10.2.Final > > > CI testing: > LRACoordinatorTestCase=testRecovery2 fails to restart the container after crashing via byteman on JDK11. Seems to be intermittent on Amsterdam CI and more consistent on Upshift, for example: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/552/ > https://ci-master-jenkins-csb-narayana.cloud.paas.psi.redhat.com/job/nara... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3244) Upgrade Arquillian OSGI Karaf to 2.2.2

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3244?page=com.atlassian.jira.plugin... ] Thomas Jenkinson updated JBTM-3244: ----------------------------------- Summary: Upgrade Arquillian OSGI Karaf to 2.2.2 (was: Upgrade version of arquillian core) > Upgrade Arquillian OSGI Karaf to 2.2.2 > -------------------------------------- > > Key: JBTM-3244 > URL: https://issues.redhat.com/browse/JBTM-3244 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: OSGi > Affects Versions: 5.10.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.10.2.Final > > > The OSGi build is failing on master due to a failure to obtain an arquillian artefact: > Caused by: java.io.IOException: Server returned HTTP response code: 501 for URL: http://repo1.maven.org/maven2/org/jboss/arquillian/osgi/arquillian-osgi-b... > For example see this build output: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/575/PROFILE=MAIN,... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3244) Upgrade version of arquillian core

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3244?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when Michael Musgrove created pull request #1552 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade version of arquillian core > ---------------------------------- > > Key: JBTM-3244 > URL: https://issues.redhat.com/browse/JBTM-3244 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: OSGi > Affects Versions: 5.10.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.10.2.Final > > > The OSGi build is failing on master due to a failure to obtain an arquillian artefact: > Caused by: java.io.IOException: Server returned HTTP response code: 501 for URL: http://repo1.maven.org/maven2/org/jboss/arquillian/osgi/arquillian-osgi-b... > For example see this build output: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/575/PROFILE=MAIN,... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3244) Upgrade version of arquillian core

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3244: -------------------------------------- Summary: Upgrade version of arquillian core Key: JBTM-3244 URL: https://issues.redhat.com/browse/JBTM-3244 Project: JBoss Transaction Manager Issue Type: Component Upgrade Components: OSGi Affects Versions: 5.10.1.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.10.2.Final The OSGi build is failing on master due to a failure to obtain an arquillian artefact: Caused by: java.io.IOException: Server returned HTTP response code: 501 for URL: http://repo1.maven.org/maven2/org/jboss/arquillian/osgi/arquillian-osgi-b... For example see this build output: http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/575/PROFILE=MAIN,... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2777) Investigate the osgi test failure with the JDK 9

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-2777?page=com.atlassian.jira.plugin... ] Thomas Jenkinson reopened JBTM-2777: ------------------------------------ Assignee: (was: Zheng Feng) > Investigate the osgi test failure with the JDK 9 > ------------------------------------------------ > > Key: JBTM-2777 > URL: https://issues.redhat.com/browse/JBTM-2777 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Build System > Reporter: Zheng Feng > Priority: Minor > Labels: jdk9 > > The arquillian can not start the karaf. > {code} > -Djava.endorsed.dirs=/home/zhfeng/work/zhfeng/narayana-jdk9/osgi/jta/target/apache-karaf-minimal-4.0.5/lib/endorsed is not supported. Endorsed standards and standalone APIs > in modular form will be supported via the concept of upgradeable modules. > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-741?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-741: ---------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.redhat.com/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Priority: Minor > Fix For: 5.next > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1699) Changes to the transaction SPI

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-1699?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-1699: ----------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > Changes to the transaction SPI > ------------------------------ > > Key: JBTM-1699 > URL: https://issues.redhat.com/browse/JBTM-1699 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > Original Estimate: 1 week, 3 days > Remaining Estimate: 1 week, 3 days > > wildfly is using a number of our internal com.arjuna interfaces which we would like to resolve by providing the same functionality in the transactions SPI. > Additionally the current SPI contains a number of unused classes which need removing. > I have created https://github.com/jbosstm/jboss-transaction-spi to manage the changes. To avoid any potential confusion and to make it clear who is responsible for the SPI we will be changing the package names. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-1107?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-1107: ----------------------------------- Fix Version/s: 5.next (was: 5.10.2.Final) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.redhat.com/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations > Reporter: Thomas Jenkinson > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > > *Background* > Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers will be invoked in case of the system crash. > *Requirements* > # Make handlers persistable (CompensationHandler, ConfirmationHandler, TransactionLoggedHandler). > ## Require Serializable interface. > ## Create PersistableHandler interface (similar to PersistableParticipant in RTS integration). > # Make participant persistable (ParticipantImpl, LocalParticipant, RemoteParticipant). > ## Make transaction identifier persistable (converting it to String should work). > ## Implement PersistableParticipant in ParticipantImpl. > ## Investigate if PARTICIPANT_COUNTERS in ParticipatnImpl have to be updated. > # Make compensation scoped beans persistable. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 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 January 2020