March 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3265) Failing LRA test FailingParticipantCallsIT#testFailingAfterLRA

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3265: -------------------------------------- Summary: Failing LRA test FailingParticipantCallsIT#testFailingAfterLRA Key: JBTM-3265 URL: https://issues.redhat.com/browse/JBTM-3265 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.10.3.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next FailingParticipantCallsIT.testFailingAfterLRA fails regularly on CI -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3258) Add checkstyle rules to the narayana performance repo

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-3258?page=com.atlassian.jira.plugin... ] Mayank Kunwar updated JBTM-3258: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add checkstyle rules to the narayana performance repo > ----------------------------------------------------- > > Key: JBTM-3258 > URL: https://issues.redhat.com/browse/JBTM-3258 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Performance Testing > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Assignee: Mayank Kunwar > Priority: Major > Fix For: 5.next > > > We use [checkstyle|https://checkstyle.sourceforge.io] on the narayana repo (https://github.com/jbosstm/narayana/blob/master/pom.xml#L368). To maintain consistency we need add and use the same rule set for the [narayana performance repo|https://github.com/jbosstm/performance/tree/master/narayana]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3258) Add checkstyle rules to the narayana performance repo

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-3258?page=com.atlassian.jira.plugin... ] Mayank Kunwar commented on JBTM-3258: ------------------------------------- Under this task, I have added checkstyle rules as mentioned in the description, and have corrected few checkstyle violations in narayana performance repo. > Add checkstyle rules to the narayana performance repo > ----------------------------------------------------- > > Key: JBTM-3258 > URL: https://issues.redhat.com/browse/JBTM-3258 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Performance Testing > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Assignee: Mayank Kunwar > Priority: Major > Fix For: 5.next > > > We use [checkstyle|https://checkstyle.sourceforge.io] on the narayana repo (https://github.com/jbosstm/narayana/blob/master/pom.xml#L368). To maintain consistency we need add and use the same rule set for the [narayana performance repo|https://github.com/jbosstm/performance/tree/master/narayana]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

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

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3088?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3088: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > NPE in Recovery Manager > ----------------------- > > Key: JBTM-3088 > URL: https://issues.redhat.com/browse/JBTM-3088 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.9.0.Final, 5.10.0.Final > Reporter: Vadim Lotarev > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > > 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.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3264) Quickstart XTS SSL quickstart infests the source directory with temporary testing files

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3264?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when Ondrej Chaloupka created pull request #268 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Quickstart XTS SSL quickstart infests the source directory with temporary testing files > --------------------------------------------------------------------------------------- > > Key: JBTM-3264 > URL: https://issues.redhat.com/browse/JBTM-3264 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Quickstarts > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > When running quickstart {{XTS/ssl}} then there are created two new directories directly at {{XTS/ssl/quickstart}} and {{XTS/ssl/wildfly}}. Those are temporary testing files and for that reason should be created under {{target}} directory. When they are placed in the source directory it will be "managed" by git as well and it could make a bit disorder. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3264) Quickstart XTS SSL quickstart infests the source directory with temporary testing files

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3264?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3264: ----------------------------------- Git Pull Request: https://github.com/jbosstm/quickstart/pull/268 > Quickstart XTS SSL quickstart infests the source directory with temporary testing files > --------------------------------------------------------------------------------------- > > Key: JBTM-3264 > URL: https://issues.redhat.com/browse/JBTM-3264 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Quickstarts > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > When running quickstart {{XTS/ssl}} then there are created two new directories directly at {{XTS/ssl/quickstart}} and {{XTS/ssl/wildfly}}. Those are temporary testing files and for that reason should be created under {{target}} directory. When they are placed in the source directory it will be "managed" by git as well and it could make a bit disorder. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3264) Quickstart XTS SSL quickstart infests the source directory with temporary testing files

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created JBTM-3264: -------------------------------------- Summary: Quickstart XTS SSL quickstart infests the source directory with temporary testing files Key: JBTM-3264 URL: https://issues.redhat.com/browse/JBTM-3264 Project: JBoss Transaction Manager Issue Type: Bug Components: Quickstarts Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka When running quickstart {{XTS/ssl}} then there are created two new directories directly at {{XTS/ssl/quickstart}} and {{XTS/ssl/wildfly}}. Those are temporary testing files and for that reason should be created under {{target}} directory. When they are placed in the source directory it will be "managed" by git as well and it could make a bit disorder. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3122) jbosstm/quickstarts tests can't be run with jdk9+

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-3122?page=com.atlassian.jira.plugin... ] Mayank Kunwar updated JBTM-3122: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jbosstm/quickstart/pull/267 > jbosstm/quickstarts tests can't be run with jdk9+ > ------------------------------------------------- > > Key: JBTM-3122 > URL: https://issues.redhat.com/browse/JBTM-3122 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.9.3.Final > Reporter: Ondrej Chaloupka > Assignee: Mayank Kunwar > Priority: Major > > Quickstarts do not run tests with JDK9+. We use the Arquillian that starts the WildFly and for the JDK9+ it requires JVM options to add module permissions (and more). > The quickstarts need to start using a profile, similar how WFLY uses it, that defines jvm args that will be passed to the {{arquillian.xml}}. > See https://github.com/wildfly/wildfly/blob/16.0.0.Final/pom.xml#L7188 > {code} > --add-exports=java.base/sun.nio.ch=ALL-UNNAMED > --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED > --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED > --add-modules=java.se > {code} > The trouble in quickstarts is that we have no parent for the quickstarts so we need to add such profile to all the `pom.xml` files all over the quickstarts. > Maybe we should provide a parent with such settings. We can unify not only this but e.g. ee version used or arquillian version. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3132) Common parent maven module for Narayana quickstarts

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-3132?page=com.atlassian.jira.plugin... ] Mayank Kunwar updated JBTM-3132: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/267 > Common parent maven module for Narayana quickstarts > --------------------------------------------------- > > Key: JBTM-3132 > URL: https://issues.redhat.com/browse/JBTM-3132 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Testing > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Mayank Kunwar > Priority: Major > > It would be beneficial to create a common quickstart maven module. > My intention is to have a one place where we can define: > * common profiles could be defined (one of such profile is Arquillian JDK9+ which defines JVM arguments needed for smooth run of tests, see https://issues.jboss.org/projects/JBTM/issues/JBTM-3122) > * common properties like arquillian version. This has benefit that quickstarts will run faster on CI as there won't be multiple versions to be downloaded. > * common repositories like jboss one > * unified checkstyle definition for all the quickstarts would be coded in one way which makes them easier to read > The quickstarts were designed to be independent on each other. The task is not to unified them. The proposal is about creating a place where a common stuff can be placed to. Otherwise the same configuration needs to be copied to multiple places. Which is hard to maintain > Other projects, e.g. WildFly, use the same approach of common parent, see https://github.com/wildfly/quickstart/blob/master/app-client/pom.xml -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3263) Quickstart ArjunaJTS/interop works only on Narayana CI

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3263?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3263: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/266 > Quickstart ArjunaJTS/interop works only on Narayana CI > ------------------------------------------------------ > > Key: JBTM-3263 > URL: https://issues.redhat.com/browse/JBTM-3263 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Quickstarts > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > The Narayana quickstart `ArjunaJTS/interop` works only on Narayana CI. > (https://github.com/jbosstm/quickstart/tree/5.10.4.Final/ArjunaJTS/interop) > Otherwise it fails with > {code} > + svn checkout https://svn.java.net/svn/glassfish~svn/trunk/main /tmp/ArjunaJTS/interop/glassfish/tmp/glassfish4 > svn: E170011: Repository moved temporarily to 'http://www.oracle.com/splash/java.net/maintenance/index.html' > [ERROR] Command execution failed. > org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) > at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404) > at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166) > at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:804) > at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:751) > at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:313) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2020