December 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3089) LRA code improvements

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3089?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-3089: ---------------------------------------- All exceptions should contain some text for easier tracking the error and a message logged. Items marked as TODO should be analysed to determine whether or not a separate JIRA is called for. > LRA code improvements > --------------------- > > Key: JBTM-3089 > URL: https://issues.jboss.org/browse/JBTM-3089 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Remove TODO comments from the code and replace with JIRA issues. > Ensure that the message string in all occurrences of GenericLRAException are meaningful. > Remove all commented out pieces of code. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3090) LRA TCK failures need to report more context to facilitate debugging

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3090: -------------------------------------- Summary: LRA TCK failures need to report more context to facilitate debugging Key: JBTM-3090 URL: https://issues.jboss.org/browse/JBTM-3090 Project: JBoss Transaction Manager Issue Type: Task Components: LRA Affects Versions: 5.9.2.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The TCK test failure message reports > failures.forEach(f -> System.out.printf("%s%n", f)); where f is the failure reason. There is also a verbose option which prints out the stack trace where the failure was reported. But in some failure cases these two pieces of information are insufficient to debug the failure. It would be nice if the resources that participated in the test also logged information which could be reported for more effective analysis of the reasons for the failure. This last requirement may affect the TCK itself so the code in the eclipse microprofile-lra repo should be analysed as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3051) LRA test timeLimit failure on JDK 9

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3051?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3051: ----------------------------------- Summary: LRA test timeLimit failure on JDK 9 (was: LRA test timeLimitRequiredLRA failure on JDK 9) > LRA test timeLimit failure on JDK 9 > ----------------------------------- > > Key: JBTM-3051 > URL: https://issues.jboss.org/browse/JBTM-3051 > 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 > > > Whilst fixing issue JBTM-2942 I noticed that the test timeLimitRequiredLRA fails consistently with the reason: > {quote} > 2018-08-14 11:38:00,244 INFO [stdout] (pool-7-thread-1) testName.getMethodName(): WARNING: test did not close http://localhost:8080/lra-coordinator/0_ffff0a3f00d6_245c07ef_5b72b0d1_104 > {quote} > I have temporarily disabled the test in the TCK runner: > {quote} > rts/lra/lra-tck/tck/src/main/java/org/eclipse/microprofile/lra/tck/RunTck.java > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3051) LRA test timeLimitRequiredLRA failure on JDK 9

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3051?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-3051: ---------------------------------------- The test has been renamed timeLimit and it still fails with the message: "http://localhost:8080/activities/timeLimit: timeLimit: compensate should have been called" > LRA test timeLimitRequiredLRA failure on JDK 9 > ---------------------------------------------- > > Key: JBTM-3051 > URL: https://issues.jboss.org/browse/JBTM-3051 > 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 > > > Whilst fixing issue JBTM-2942 I noticed that the test timeLimitRequiredLRA fails consistently with the reason: > {quote} > 2018-08-14 11:38:00,244 INFO [stdout] (pool-7-thread-1) testName.getMethodName(): WARNING: test did not close http://localhost:8080/lra-coordinator/0_ffff0a3f00d6_245c07ef_5b72b0d1_104 > {quote} > I have temporarily disabled the test in the TCK runner: > {quote} > rts/lra/lra-tck/tck/src/main/java/org/eclipse/microprofile/lra/tck/RunTck.java > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2942) LRA tests failed when building with the JDK9

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2942?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2942: ----------------------------------- Comment: was deleted (was: timeLimit TCK test also failed with the message: "http://localhost:8080/activities/timeLimit: timeLimit: compensate should have been called" ) > LRA tests failed when building with the JDK9 > -------------------------------------------- > > Key: JBTM-2942 > URL: https://issues.jboss.org/browse/JBTM-2942 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Amos Feng > Assignee: Michael Musgrove > Priority: Major > Labels: jdk9 > > The lra-test still failed with java.lang.IllegalArgumentException when deploying the war. It looks like the wildfly-swarm does support the JDK9 currently. Also I find 1 and 2 with the same issues. > 1. https://stackoverflow.com/questions/46449735/wildfly-swarm-deployment-cra... > 2. https://stackoverflow.com/questions/42990017/illegalargumentexception-whi... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3089) LRA code improvements

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3089: -------------------------------------- Summary: LRA code improvements Key: JBTM-3089 URL: https://issues.jboss.org/browse/JBTM-3089 Project: JBoss Transaction Manager Issue Type: Task Components: LRA Affects Versions: 5.9.2.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next Remove TODO comments from the code and replace with JIRA issues. Ensure that the message string in all occurrences of GenericLRAException are meaningful. Remove all commented out pieces of code. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3088) NPE in Recovery Manager

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3088?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-3088: ------------------------------------- It looks to me like one of the recovery helpers is returning a null. But there is not enough detail here to make a proper assesment of whether there is an issue here or not. I will close it as there is not enough information but please can you open a thread on https://developer.jboss.org/en/jbosstm/content?filterID=contentstatus[pub... so we can try to work though the possible causes with you and if necessary re-open this issue with more details. > NPE in Recovery Manager > ----------------------- > > Key: JBTM-3088 > URL: https://issues.jboss.org/browse/JBTM-3088 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.9.0.Final > Reporter: Vadim Lotarev > Priority: Major > > NPE happens during Recovery: > Dec 12 00:01:54.559 WARN [][Periodic Recovery] ARJUNA016009: Caught: (com.arjuna.ats.jta:) > java.lang.NullPointerException > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:713) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:494) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:245) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3088) NPE in Recovery Manager

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3088?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3088. ------------------------------- Resolution: Incomplete Description > NPE in Recovery Manager > ----------------------- > > Key: JBTM-3088 > URL: https://issues.jboss.org/browse/JBTM-3088 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.9.0.Final > Reporter: Vadim Lotarev > Priority: Major > > NPE happens during Recovery: > Dec 12 00:01:54.559 WARN [][Periodic Recovery] ARJUNA016009: Caught: (com.arjuna.ats.jta:) > java.lang.NullPointerException > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:713) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:494) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:245) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3088) NPE in Recovery Manager

by Vadim Lotarev (Jira)

Vadim Lotarev created JBTM-3088: ----------------------------------- Summary: NPE in Recovery Manager Key: JBTM-3088 URL: https://issues.jboss.org/browse/JBTM-3088 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Affects Versions: 5.9.0.Final Reporter: Vadim Lotarev NPE happens during Recovery: Dec 12 00:01:54.559 WARN [][Periodic Recovery] ARJUNA016009: Caught: (com.arjuna.ats.jta:) java.lang.NullPointerException at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:713) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:494) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:245) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) ~[narayana-jta-5.9.0.Final.jar.9186195290256057980.jar:5.9.0.Final (revision: f0935)] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2912) Upgrade JMS transactional driver to JMS 2.0

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-2912?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2912: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Upgrade JMS transactional driver to JMS 2.0 > ------------------------------------------- > > Key: JBTM-2912 > URL: https://issues.jboss.org/browse/JBTM-2912 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JMS > Reporter: Tom Jenkinson > Priority: Major > Fix For: 5.next > > > The transactional driver was implemented for JMS API 1.1. We should upgrade to 2.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years

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