June 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3339) ArjunaJTS/interop/glassfish hangs on CI

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3339?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3339: ----------------------------------- Attachment: stacktraces > ArjunaJTS/interop/glassfish hangs on CI > --------------------------------------- > > Key: JBTM-3339 > URL: https://issues.redhat.com/browse/JBTM-3339 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Priority: Minor > Fix For: 6.later > > Attachments: stacktraces > > > The [WildFly to GlassFish interop quickstart|[https://github.com/jbosstm/quickstart/tree/master/ArjunaJTS/i...] hung on CI. I am attaching the stackdumps but it doesn't look like Wilfly started fully so is probably an transient error. Since the quickstart is a demonstrator I am marking the priority as low. If it happens again we might want to increase its priority. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3339) ArjunaJTS/interop/glassfish hangs on CI

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3339: -------------------------------------- Summary: ArjunaJTS/interop/glassfish hangs on CI Key: JBTM-3339 URL: https://issues.redhat.com/browse/JBTM-3339 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator Affects Versions: 5.10.4.Final Reporter: Michael Musgrove Fix For: 6.later The [WildFly to GlassFish interop quickstart|[https://github.com/jbosstm/quickstart/tree/master/ArjunaJTS/i...] hung on CI. I am attaching the stackdumps but it doesn't look like Wilfly started fully so is probably an transient error. Since the quickstart is a demonstrator I am marking the priority as low. If it happens again we might want to increase its priority. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3337) Narayana startup fails when empty system property is provided

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3337?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3337: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > Narayana startup fails when empty system property is provided > ------------------------------------------------------------- > > Key: JBTM-3337 > URL: https://issues.redhat.com/browse/JBTM-3337 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Common > Affects Versions: 5.10.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > Fix For: 5.next > > > When Narayana starts with an empty property then it fails during startup. > This is documented at the JBEAP issue https://issues.redhat.com/browse/JBEAP-19690. > As the [~rchakrab] pointed at the issue the error came from https://github.com/jbosstm/narayana/blob/5.10.5.Final/common/classes/com/... > The error which can be observed is > {code} > testGetWithEmptyPropertyWithStax(com.arjuna.common.tests.propertyservice.EmptyPropertiesFactoryTest) Time elapsed: 0.023 s <<< ERROR! > java.lang.RuntimeException: unable to load properties from /home/ochaloup/Transactions/narayana/common/target/test-classes/properties-factory-test.xml > at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.getPropertiesFromFile(AbstractPropertiesFactory.java:107) > at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.initDefaultProperties(AbstractPropertiesFactory.java:196) > at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.getDefaultProperties(AbstractPropertiesFactory.java:62) > at com.arjuna.common.tests.propertyservice.EmptyPropertiesFactoryTest.testGetWithEmptyPropertyWithStax(EmptyPropertiesFactoryTest.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > 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.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) > Caused by: java.lang.IllegalArgumentException: key can't be empty > at java.lang.System.checkKey(System.java:843) > at java.lang.System.getProperty(System.java:716) > at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.applySystemProperties(AbstractPropertiesFactory.java:125) > at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.getPropertiesFromFile(AbstractPropertiesFactory.java:104) > ... 28 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3335) Upgrade jca + tomcat quickstart (org.jboss.narayana.quickstarts:jca-and-tomcat)

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-3335?page=com.atlassian.jira.plugin... ] Mayank Kunwar reassigned JBTM-3335: ----------------------------------- Assignee: Mayank Kunwar > Upgrade jca + tomcat quickstart (org.jboss.narayana.quickstarts:jca-and-tomcat) > ------------------------------------------------------------------------------- > > Key: JBTM-3335 > URL: https://issues.redhat.com/browse/JBTM-3335 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Quickstarts > Reporter: Michael Musgrove > Assignee: Mayank Kunwar > Priority: Blocker > > The jca + tomcat quickstart is using a very old version of hibernate-validator (org.hibernate:hibernate-validator:5.0.1.Final) and needs updating to use a more recent release. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3335) Upgrade jca + tomcat quickstart (org.jboss.narayana.quickstarts:jca-and-tomcat)

by Anonymous (Jira)

[ https://issues.redhat.com/browse/JBTM-3335?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when Mayank Kunwar created pull request #290 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade jca + tomcat quickstart (org.jboss.narayana.quickstarts:jca-and-tomcat) > ------------------------------------------------------------------------------- > > Key: JBTM-3335 > URL: https://issues.redhat.com/browse/JBTM-3335 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Quickstarts > Reporter: Michael Musgrove > Priority: Blocker > > The jca + tomcat quickstart is using a very old version of hibernate-validator (org.hibernate:hibernate-validator:5.0.1.Final) and needs updating to use a more recent release. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3338) CMR getters should use copy-constructors in JTAEnvironementBean to ensure thread safety

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3338?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3338: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1641 > CMR getters should use copy-constructors in JTAEnvironementBean to ensure thread safety > --------------------------------------------------------------------------------------- > > Key: JBTM-3338 > URL: https://issues.redhat.com/browse/JBTM-3338 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.10.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The CMR getters should use the copy constructors as it's usual in other places in JTAEnvironemtBean. The copy constructor helps the thread safety. > * https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... > * https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... > * https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3338) CMR getters should use copy-constructors in JTAEnvironementBean to ensure thread safety

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3338?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3338: ----------------------------------- Description: The CMR getters should use the copy constructors as it's usual in other places in JTAEnvironemtBean. The copy constructor helps the thread safety. * https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... * https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... * https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... was: The CMR getters should use the copy constructors as it's usual in other places in JTAEnvironemtBean. The copy constructor helps the thread safety. https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... Forum Reference: https://groups.google.com/g/narayana-users/c/Vew6v8hJ91Q > CMR getters should use copy-constructors in JTAEnvironementBean to ensure thread safety > --------------------------------------------------------------------------------------- > > Key: JBTM-3338 > URL: https://issues.redhat.com/browse/JBTM-3338 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.10.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The CMR getters should use the copy constructors as it's usual in other places in JTAEnvironemtBean. The copy constructor helps the thread safety. > * https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... > * https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... > * https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3338) CMR getters should use copy-constructors in JTAEnvironementBean to ensure thread safety

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created JBTM-3338: -------------------------------------- Summary: CMR getters should use copy-constructors in JTAEnvironementBean to ensure thread safety Key: JBTM-3338 URL: https://issues.redhat.com/browse/JBTM-3338 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Affects Versions: 5.10.5.Final Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka The CMR getters should use the copy constructors as it's usual in other places in JTAEnvironemtBean. The copy constructor helps the thread safety. https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... https://github.com/jbosstm/narayana/blob/5.10.4.Final/ArjunaJTA/jta/class... -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3337) Narayana startup fails when empty system property is provided

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3337?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3337: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1639 > Narayana startup fails when empty system property is provided > ------------------------------------------------------------- > > Key: JBTM-3337 > URL: https://issues.redhat.com/browse/JBTM-3337 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Common > Affects Versions: 5.10.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > When Narayana starts with an empty property then it fails during startup. > This is documented at the JBEAP issue https://issues.redhat.com/browse/JBEAP-19690. > As the [~rchakrab] pointed at the issue the error came from https://github.com/jbosstm/narayana/blob/5.10.5.Final/common/classes/com/... > The error which can be observed is > {code} > testGetWithEmptyPropertyWithStax(com.arjuna.common.tests.propertyservice.EmptyPropertiesFactoryTest) Time elapsed: 0.023 s <<< ERROR! > java.lang.RuntimeException: unable to load properties from /home/ochaloup/Transactions/narayana/common/target/test-classes/properties-factory-test.xml > at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.getPropertiesFromFile(AbstractPropertiesFactory.java:107) > at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.initDefaultProperties(AbstractPropertiesFactory.java:196) > at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.getDefaultProperties(AbstractPropertiesFactory.java:62) > at com.arjuna.common.tests.propertyservice.EmptyPropertiesFactoryTest.testGetWithEmptyPropertyWithStax(EmptyPropertiesFactoryTest.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > 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.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) > Caused by: java.lang.IllegalArgumentException: key can't be empty > at java.lang.System.checkKey(System.java:843) > at java.lang.System.getProperty(System.java:716) > at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.applySystemProperties(AbstractPropertiesFactory.java:125) > at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.getPropertiesFromFile(AbstractPropertiesFactory.java:104) > ... 28 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3337) Narayana startup fails when empty system property is provided

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created JBTM-3337: -------------------------------------- Summary: Narayana startup fails when empty system property is provided Key: JBTM-3337 URL: https://issues.redhat.com/browse/JBTM-3337 Project: JBoss Transaction Manager Issue Type: Bug Components: Common Affects Versions: 5.10.5.Final Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka When Narayana starts with an empty property then it fails during startup. This is documented at the JBEAP issue https://issues.redhat.com/browse/JBEAP-19690. As the [~rchakrab] pointed at the issue the error came from https://github.com/jbosstm/narayana/blob/5.10.5.Final/common/classes/com/... The error which can be observed is {code} testGetWithEmptyPropertyWithStax(com.arjuna.common.tests.propertyservice.EmptyPropertiesFactoryTest) Time elapsed: 0.023 s <<< ERROR! java.lang.RuntimeException: unable to load properties from /home/ochaloup/Transactions/narayana/common/target/test-classes/properties-factory-test.xml at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.getPropertiesFromFile(AbstractPropertiesFactory.java:107) at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.initDefaultProperties(AbstractPropertiesFactory.java:196) at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.getDefaultProperties(AbstractPropertiesFactory.java:62) at com.arjuna.common.tests.propertyservice.EmptyPropertiesFactoryTest.testGetWithEmptyPropertyWithStax(EmptyPropertiesFactoryTest.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) 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.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) Caused by: java.lang.IllegalArgumentException: key can't be empty at java.lang.System.checkKey(System.java:843) at java.lang.System.getProperty(System.java:716) at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.applySystemProperties(AbstractPropertiesFactory.java:125) at com.arjuna.common.util.propertyservice.AbstractPropertiesFactory.getPropertiesFromFile(AbstractPropertiesFactory.java:104) ... 28 more {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 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 June 2020