From issues at jboss.org Mon Dec 3 10:54:00 2018 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Mon, 3 Dec 2018 10:54:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3074) No test cleanup for STM taxonomy tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3074: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > No test cleanup for STM taxonomy tests > --------------------------------------- > > Key: JBTM-3074 > URL: https://issues.jboss.org/browse/JBTM-3074 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > Attachments: stm.dump > > > The tests added by JBTM-3058 are missing clean up actions . Some of the tests launch new threads and if they hang on one test they may cause subsequent tests to hang resulting in a stalled CI run (see attached file for an example). The after test clean up should report the failures and then clean up so that subsequent tests can execute. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Dec 3 20:43:00 2018 From: issues at jboss.org (Amos Feng (Jira)) Date: Mon, 3 Dec 2018 20:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3084) QA tests fail with the JDK9 In-Reply-To: References: Message-ID: Amos Feng created JBTM-3084: ------------------------------- Summary: QA tests fail with the JDK9 Key: JBTM-3084 URL: https://issues.jboss.org/browse/JBTM-3084 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Reporter: Amos Feng Assignee: Amos Feng It seems the checking of the ant.jdk.version is not right. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Dec 3 20:57:00 2018 From: issues at jboss.org (Amos Feng (Jira)) Date: Mon, 3 Dec 2018 20:57:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3084) QA tests fail with the JDK9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Amos Feng created pull request #1390 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > QA tests fail with the JDK9 > --------------------------- > > Key: JBTM-3084 > URL: https://issues.jboss.org/browse/JBTM-3084 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Major > > It seems the checking of the ant.jdk.version is not right. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 02:56:00 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Tue, 4 Dec 2018 02:56:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3079) InboundBridge recovery aborts live transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3079: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > InboundBridge recovery aborts live transactions > ----------------------------------------------- > > Key: JBTM-3079 > URL: https://issues.jboss.org/browse/JBTM-3079 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.5.32.Final, 5.9.0.Final > Environment: EAP 7.1.5 / 5.5.32.Final > Reporter: Jonathan Halliday > Assignee: Tom Jenkinson > Priority: Critical > Attachments: jbtm3079.patch > > > During a recovery pass, the InboundBridgeRecoveryManager scans for subordinate XA branches that may need cleanup. The filtering process applied by checkXid correctly excludes tx that are not owned by the bridge, but fails to ignore those that are owned but also still live. Therefore, a race condition exists such that the recovery process may incorrectly abort a branch if invoked between the prepare and commit steps, resulting in data corruption relative to other committed branches from the parent i.e. Heuristic outcomes. > TRACE [org.jboss.jbossts.txbridge] (TaskWorker-3) BridgeDurableParticipant.prepare(Xid=< 131080, 35, 64, ... >) > TRACE [org.jboss.jbossts.txbridge] (Periodic Recovery) rolling back orphaned subordinate tx < 131080, 35, 64, ... > > ERROR [org.jboss.jbossts.txbridge] (TaskWorker-8) ARJUNA033004: commit on Xid=< 131080, 35, 64, ... > failed: javax.transaction.xa.XAException > It is necessary to enhance checkXid to validate against known live tx. The easiest way would seem to be to have the InboundBridgeManager singleton hold a lookup table of live tx, effectively a secondary index into its existing collection of InboundBridges, against which the recovery system can validate the in-doubt Xid. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 05:37:00 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 05:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3084) QA tests fail with the JDK9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3084: -------------------------------- Fix Version/s: 5.next > QA tests fail with the JDK9 > --------------------------- > > Key: JBTM-3084 > URL: https://issues.jboss.org/browse/JBTM-3084 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Major > Fix For: 5.next > > > It seems the checking of the ant.jdk.version is not right. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 05:37:00 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 05:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3084) QA tests fail with the JDK9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3084: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > QA tests fail with the JDK9 > --------------------------- > > Key: JBTM-3084 > URL: https://issues.jboss.org/browse/JBTM-3084 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Major > Fix For: 5.next > > > It seems the checking of the ant.jdk.version is not right. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:01:00 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Tue, 4 Dec 2018 06:01:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3085) Compensations test fail because of WildFly module changes In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-3085: ------------------------------------- Summary: Compensations test fail because of WildFly module changes Key: JBTM-3085 URL: https://issues.jboss.org/browse/JBTM-3085 Project: JBoss Transaction Manager Issue Type: Bug Components: Compensations Affects Versions: 5.9.0.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka There was change in module dependencies for compensations (see at https://issues.jboss.org/browse/WFLY-11421) which requires changes into testsuite of compensations. Currently the narayana CI XTS tests are failing. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:00 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3084) QA tests fail with the JDK9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3084. ------------------------------- > QA tests fail with the JDK9 > --------------------------- > > Key: JBTM-3084 > URL: https://issues.jboss.org/browse/JBTM-3084 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Major > Fix For: 5.9.1.Final > > > It seems the checking of the ant.jdk.version is not right. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3076) Upgrade the arquillian core and wildfly-arquillian-container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3076. ------------------------------- > Upgrade the arquillian core and wildfly-arquillian-container > ------------------------------------------------------------ > > Key: JBTM-3076 > URL: https://issues.jboss.org/browse/JBTM-3076 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Major > Fix For: 5.9.1.Final > > > The RTS AS integration failed and these two artifacts need to be upgraded. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3074) No test cleanup for STM taxonomy tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3074. ------------------------------- > No test cleanup for STM taxonomy tests > --------------------------------------- > > Key: JBTM-3074 > URL: https://issues.jboss.org/browse/JBTM-3074 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.1.Final > > Attachments: stm.dump > > > The tests added by JBTM-3058 are missing clean up actions . Some of the tests launch new threads and if they hang on one test they may cause subsequent tests to hang resulting in a stalled CI run (see attached file for an example). The after test clean up should report the failures and then clean up so that subsequent tests can execute. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3066) Starting a nested LRA via the client API leaves the parent as the current context In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3066. ------------------------------- > Starting a nested LRA via the client API leaves the parent as the current context > --------------------------------------------------------------------------------- > > Key: JBTM-3066 > URL: https://issues.jboss.org/browse/JBTM-3066 > 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.9.1.Final > > > If an LRA is associated with a thread and that thread then starts a new LRA then the new one is nested under the first. When using the LRAClient API to start the child LRA the resulting context is left as the parent. This is wrong since the thread should now operate in the context of the nested LRA. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3064) After a crash active LRA's are left in a limbo state In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3064. ------------------------------- > After a crash active LRA's are left in a limbo state > ---------------------------------------------------- > > Key: JBTM-3064 > URL: https://issues.jboss.org/browse/JBTM-3064 > 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.9.1.Final > > > If an LRA coordinator crashes with active LRA's (ie ones that have not yet been asked to finish) then when the coordinator is restarted they do not appear in the coordinators list so they cannot be ended. > The fix is to ensure that the LRA periodic recovery module adds them back into the coordinators list of active LRA's. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3063) Include a simple LRA quickstart showing difference between using a proxy and CDI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3063. ------------------------------- > Include a simple LRA quickstart showing difference between using a proxy and CDI > -------------------------------------------------------------------------------- > > Key: JBTM-3063 > URL: https://issues.jboss.org/browse/JBTM-3063 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.9.1.Final > > > Participants can join LRAs either via [annotations|https://github.com/eclipse/microprofile-lra/tree/master/api/src/main/java/org/eclipse/microprofile/lra/annotation] or via [a registration API|https://github.com/eclipse/microprofile-lra/blob/master/api/src/main/java/org/eclipse/microprofile/lra/participant/LRAParticipant.java]. There should be a simple quickstart that demonstrates the difference between the two options. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3055) Clarify title of the manual which describes functionality available in a known product In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3055. ------------------------------- > Clarify title of the manual which describes functionality available in a known product > -------------------------------------------------------------------------------------- > > Key: JBTM-3055 > URL: https://issues.jboss.org/browse/JBTM-3055 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Priority: Major > Fix For: 5.9.1.Final > > > Currently the manual states "Narayana Product Documentation" whereas in fact that section of documentation describes the functionality that is available in the Red Hat JBoss EAP product. The manual title could be clearer here. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3053) Narayana log should be enhanced for information what are nodes the node name orphan filter takes care of In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3053. ------------------------------- > Narayana log should be enhanced for information what are nodes the node name orphan filter takes care of > -------------------------------------------------------------------------------------------------------- > > Key: JBTM-3053 > URL: https://issues.jboss.org/browse/JBTM-3053 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.9.1.Final > > > Based on my investigation of logs at WFWIP-118 I found out I'm not able to (easily) find what are node names that the recovery considers to be responsible for. > The orphan filter {{NodeNameXAResourceOrphanFilter}} checks the node name sealed in the {{Xid}} to be part of the list {{_xaRecoveryNodes}} > https://github.com/jbosstm/narayana/blob/5.9.0.Final/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/NodeNameXAResourceOrphanFilter.java#L72 > But what is the content of the list is not recorded in the log anywhere. I think setting up the environmental bean with this information should be logged at debug level to be possible to find it > https://github.com/jbosstm/narayana/blob/5.9.0.Final/ArjunaJTA/jta/classes/com/arjuna/ats/jta/common/JTAEnvironmentBean.java#L411 -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3052) Update to latest version of jboss-parent due to codecoverage plugin incompatibilities In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3052. ------------------------------- > Update to latest version of jboss-parent due to codecoverage plugin incompatibilities > ------------------------------------------------------------------------------------- > > Key: JBTM-3052 > URL: https://issues.jboss.org/browse/JBTM-3052 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Major > Fix For: 5.9.1.Final > > > This is trying to use the version released in June of maven-project-info-reports-plugin which seems incompatible with the version of the site plugin we are using. I can see from a previous build that 2.9 works so lets revert to that version? > {code} > /home/jenkins/workspace/narayana-codeCoverage/tools/maven/bin/mvn -s tools/maven/conf/settings.xml -Dbpa=centos54x64 -Dorson.jar.location=/home/jenkins/workspace/narayana-codeCoverage/ext/ site clean install site -f XTS/localjunit/xtstest/pom.xml -B -Parq -Dorg.jboss.remoting-jmx.timeout=300 > OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > [INFO] Scanning for projects... > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building Narayana: XTS localjunit xtstest 5.9.1.Final-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-site-plugin:3.4:site (default-site) @ xtstest --- > [WARNING] Report plugin org.apache.maven.plugins:maven-project-info-reports-plugin has an empty version. > [WARNING] > [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. > [WARNING] > [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-project-info-reports-plugin/maven-metadata.xml > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/maven-metadata.xml > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/maven-metadata.xml (948 B at 4.8 KB/sec) > [INFO] Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-project-info-reports-plugin/maven-metadata.xml (471 B at 0.8 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.0/maven-project-info-reports-plugin-3.0.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.0/maven-project-info-reports-plugin-3.0.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.0/maven-project-info-reports-plugin-3.0.0.pom (20 KB at 1064.7 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.0/maven-project-info-reports-plugin-3.0.0.jar > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.0/maven-project-info-reports-plugin-3.0.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/3.0.0/maven-project-info-reports-plugin-3.0.0.jar (294 KB at 8378.8 KB/sec) > [INFO] configuring report plugin org.apache.maven.plugins:maven-project-info-reports-plugin:3.0.0 > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/reporting/maven-reporting-impl/3.0.0/maven-reporting-impl-3.0.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/3.0.0/maven-reporting-impl-3.0.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/3.0.0/maven-reporting-impl-3.0.0.pom (8 KB at 743.3 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-sink-api/1.7/doxia-sink-api-1.7.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.7/doxia-sink-api-1.7.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.7/doxia-sink-api-1.7.pom (2 KB at 186.9 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia/1.7/doxia-1.7.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.7/doxia-1.7.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.7/doxia-1.7.pom (15 KB at 1354.0 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-logging-api/1.7/doxia-logging-api-1.7.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-logging-api/1.7/doxia-logging-api-1.7.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-logging-api/1.7/doxia-logging-api-1.7.pom (2 KB at 150.0 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-decoration-model/1.7.4/doxia-decoration-model-1.7.4.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.7.4/doxia-decoration-model-1.7.4.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.7.4/doxia-decoration-model-1.7.4.pom (4 KB at 414.3 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-sitetools/1.7.4/doxia-sitetools-1.7.4.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sitetools/1.7.4/doxia-sitetools-1.7.4.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sitetools/1.7.4/doxia-sitetools-1.7.4.pom (15 KB at 1571.9 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-core/1.7/doxia-core-1.7.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-core/1.7/doxia-core-1.7.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-core/1.7/doxia-core-1.7.pom (4 KB at 496.0 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-site-renderer/1.7.4/doxia-site-renderer-1.7.4.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.7.4/doxia-site-renderer-1.7.4.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.7.4/doxia-site-renderer-1.7.4.pom (7 KB at 725.2 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-skin-model/1.7.4/doxia-skin-model-1.7.4.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-skin-model/1.7.4/doxia-skin-model-1.7.4.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-skin-model/1.7.4/doxia-skin-model-1.7.4.pom (3 KB at 118.2 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-module-xhtml/1.7/doxia-module-xhtml-1.7.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-module-xhtml/1.7/doxia-module-xhtml-1.7.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-module-xhtml/1.7/doxia-module-xhtml-1.7.pom (2 KB at 199.1 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-modules/1.7/doxia-modules-1.7.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-modules/1.7/doxia-modules-1.7.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-modules/1.7/doxia-modules-1.7.pom (3 KB at 320.1 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/codehaus/plexus/plexus-velocity/1.2/plexus-velocity-1.2.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-velocity/1.2/plexus-velocity-1.2.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-velocity/1.2/plexus-velocity-1.2.pom (3 KB at 344.4 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/shared/maven-shared-jar/1.2/maven-shared-jar-1.2.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-shared-jar/1.2/maven-shared-jar-1.2.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-shared-jar/1.2/maven-shared-jar-1.2.pom (5 KB at 538.3 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/bcel/bcel/6.2/bcel-6.2.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/bcel/bcel/6.2/bcel-6.2.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/bcel/bcel/6.2/bcel-6.2.pom (20 KB at 1750.8 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-api/1.10.0/maven-scm-api-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-api/1.10.0/maven-scm-api-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-api/1.10.0/maven-scm-api-1.10.0.pom (2 KB at 198.1 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm/1.10.0/maven-scm-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm/1.10.0/maven-scm-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm/1.10.0/maven-scm-1.10.0.pom (26 KB at 2302.9 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-manager-plexus/1.10.0/maven-scm-manager-plexus-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-manager-plexus/1.10.0/maven-scm-manager-plexus-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-manager-plexus/1.10.0/maven-scm-manager-plexus-1.10.0.pom (3 KB at 243.5 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-managers/1.10.0/maven-scm-managers-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-managers/1.10.0/maven-scm-managers-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-managers/1.10.0/maven-scm-managers-1.10.0.pom (2 KB at 166.0 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-hg/1.10.0/maven-scm-provider-hg-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-hg/1.10.0/maven-scm-provider-hg-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-hg/1.10.0/maven-scm-provider-hg-1.10.0.pom (3 KB at 291.5 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-providers/1.10.0/maven-scm-providers-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-providers/1.10.0/maven-scm-providers-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-providers/1.10.0/maven-scm-providers-1.10.0.pom (4 KB at 503.6 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-perforce/1.10.0/maven-scm-provider-perforce-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-perforce/1.10.0/maven-scm-provider-perforce-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-perforce/1.10.0/maven-scm-provider-perforce-1.10.0.pom (3 KB at 279.2 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-starteam/1.10.0/maven-scm-provider-starteam-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-starteam/1.10.0/maven-scm-provider-starteam-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-starteam/1.10.0/maven-scm-provider-starteam-1.10.0.pom (3 KB at 104.1 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-svn-commons/1.10.0/maven-scm-provider-svn-commons-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-svn-commons/1.10.0/maven-scm-provider-svn-commons-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-svn-commons/1.10.0/maven-scm-provider-svn-commons-1.10.0.pom (3 KB at 246.9 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-providers-svn/1.10.0/maven-scm-providers-svn-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-providers-svn/1.10.0/maven-scm-providers-svn-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-providers-svn/1.10.0/maven-scm-providers-svn-1.10.0.pom (3 KB at 267.1 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-svnexe/1.10.0/maven-scm-provider-svnexe-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-svnexe/1.10.0/maven-scm-provider-svnexe-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-svnexe/1.10.0/maven-scm-provider-svnexe-1.10.0.pom (3 KB at 295.7 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.10.0/maven-scm-provider-cvs-commons-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.10.0/maven-scm-provider-cvs-commons-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.10.0/maven-scm-provider-cvs-commons-1.10.0.pom (3 KB at 259.5 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-providers-cvs/1.10.0/maven-scm-providers-cvs-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-providers-cvs/1.10.0/maven-scm-providers-cvs-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-providers-cvs/1.10.0/maven-scm-providers-cvs-1.10.0.pom (2 KB at 214.2 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-cvsexe/1.10.0/maven-scm-provider-cvsexe-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvsexe/1.10.0/maven-scm-provider-cvsexe-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvsexe/1.10.0/maven-scm-provider-cvsexe-1.10.0.pom (3 KB at 301.3 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-cvsjava/1.10.0/maven-scm-provider-cvsjava-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvsjava/1.10.0/maven-scm-provider-cvsjava-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvsjava/1.10.0/maven-scm-provider-cvsjava-1.10.0.pom (3 KB at 293.5 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/netbeans/lib/cvsclient/20060125/cvsclient-20060125.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/netbeans/lib/cvsclient/20060125/cvsclient-20060125.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/netbeans/lib/cvsclient/20060125/cvsclient-20060125.pom (459 B at 56.0 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/ch/ethz/ganymed/ganymed-ssh2/build210/ganymed-ssh2-build210.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/ch/ethz/ganymed/ganymed-ssh2/build210/ganymed-ssh2-build210.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/ch/ethz/ganymed/ganymed-ssh2/build210/ganymed-ssh2-build210.pom (710 B at 99.1 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-git-commons/1.10.0/maven-scm-provider-git-commons-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-git-commons/1.10.0/maven-scm-provider-git-commons-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-git-commons/1.10.0/maven-scm-provider-git-commons-1.10.0.pom (3 KB at 295.5 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-providers-git/1.10.0/maven-scm-providers-git-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-providers-git/1.10.0/maven-scm-providers-git-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-providers-git/1.10.0/maven-scm-providers-git-1.10.0.pom (3 KB at 309.6 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-gitexe/1.10.0/maven-scm-provider-gitexe-1.10.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-gitexe/1.10.0/maven-scm-provider-gitexe-1.10.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-gitexe/1.10.0/maven-scm-provider-gitexe-1.10.0.pom (3 KB at 318.0 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-sink-api/1.8/doxia-sink-api-1.8.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.8/doxia-sink-api-1.8.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.8/doxia-sink-api-1.8.pom (2 KB at 186.9 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia/1.8/doxia-1.8.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.8/doxia-1.8.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia/1.8/doxia-1.8.pom (18 KB at 1612.6 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-logging-api/1.8/doxia-logging-api-1.8.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-logging-api/1.8/doxia-logging-api-1.8.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-logging-api/1.8/doxia-logging-api-1.8.pom (2 KB at 214.3 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/codehaus/plexus/plexus-container-default/1.7.1/plexus-container-default-1.7.1.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-container-default/1.7.1/plexus-container-default-1.7.1.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-container-default/1.7.1/plexus-container-default-1.7.1.pom (3 KB at 384.3 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-core/1.8/doxia-core-1.8.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-core/1.8/doxia-core-1.8.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-core/1.8/doxia-core-1.8.pom (5 KB at 589.0 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-decoration-model/1.8.1/doxia-decoration-model-1.8.1.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.8.1/doxia-decoration-model-1.8.1.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.8.1/doxia-decoration-model-1.8.1.pom (4 KB at 403.6 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-sitetools/1.8.1/doxia-sitetools-1.8.1.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sitetools/1.8.1/doxia-sitetools-1.8.1.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-sitetools/1.8.1/doxia-sitetools-1.8.1.pom (15 KB at 1567.8 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-site-renderer/1.8.1/doxia-site-renderer-1.8.1.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.8.1/doxia-site-renderer-1.8.1.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.8.1/doxia-site-renderer-1.8.1.pom (7 KB at 906.1 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-skin-model/1.8.1/doxia-skin-model-1.8.1.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-skin-model/1.8.1/doxia-skin-model-1.8.1.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-skin-model/1.8.1/doxia-skin-model-1.8.1.pom (3 KB at 360.0 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-module-xhtml/1.8/doxia-module-xhtml-1.8.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-module-xhtml/1.8/doxia-module-xhtml-1.8.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-module-xhtml/1.8/doxia-module-xhtml-1.8.pom (2 KB at 267.7 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-modules/1.8/doxia-modules-1.8.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-modules/1.8/doxia-modules-1.8.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-modules/1.8/doxia-modules-1.8.pom (3 KB at 320.1 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-integration-tools/1.8.1/doxia-integration-tools-1.8.1.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-integration-tools/1.8.1/doxia-integration-tools-1.8.1.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-integration-tools/1.8.1/doxia-integration-tools-1.8.1.pom (6 KB at 725.6 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/codehaus/plexus/plexus-i18n/1.0-beta-10/plexus-i18n-1.0-beta-10.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-i18n/1.0-beta-10/plexus-i18n-1.0-beta-10.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-i18n/1.0-beta-10/plexus-i18n-1.0-beta-10.pom (3 KB at 289.5 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/codehaus/plexus/plexus-interpolation/1.25/plexus-interpolation-1.25.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-interpolation/1.25/plexus-interpolation-1.25.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-interpolation/1.25/plexus-interpolation-1.25.pom (3 KB at 369.3 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/codehaus/plexus/plexus/5.1/plexus-5.1.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus/5.1/plexus-5.1.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus/5.1/plexus-5.1.pom (22 KB at 1831.4 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/wagon/wagon-http-lightweight/3.1.0/wagon-http-lightweight-3.1.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-http-lightweight/3.1.0/wagon-http-lightweight-3.1.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-http-lightweight/3.1.0/wagon-http-lightweight-3.1.0.pom (3 KB at 322.0 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/wagon/wagon-providers/3.1.0/wagon-providers-3.1.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-providers/3.1.0/wagon-providers-3.1.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-providers/3.1.0/wagon-providers-3.1.0.pom (3 KB at 392.0 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/wagon/wagon/3.1.0/wagon-3.1.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon/3.1.0/wagon-3.1.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon/3.1.0/wagon-3.1.0.pom (21 KB at 1087.8 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/wagon/wagon-http-shared/3.1.0/wagon-http-shared-3.1.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-http-shared/3.1.0/wagon-http-shared-3.1.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-http-shared/3.1.0/wagon-http-shared-3.1.0.pom (3 KB at 316.8 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.pom (8 KB at 888.7 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/httpcomponents/httpclient/4.5.5/httpclient-4.5.5.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.5.5/httpclient-4.5.5.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpclient/4.5.5/httpclient-4.5.5.pom (7 KB at 870.1 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/httpcomponents/httpcomponents-client/4.5.5/httpcomponents-client-4.5.5.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.5.5/httpcomponents-client-4.5.5.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-client/4.5.5/httpcomponents-client-4.5.5.pom (16 KB at 1680.6 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/httpcomponents/httpcomponents-parent/10/httpcomponents-parent-10.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-parent/10/httpcomponents-parent-10.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-parent/10/httpcomponents-parent-10.pom (33 KB at 3286.5 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/httpcomponents/httpcore/4.4.9/httpcore-4.4.9.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore/4.4.9/httpcore-4.4.9.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcore/4.4.9/httpcore-4.4.9.pom (5 KB at 708.7 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/httpcomponents/httpcomponents-core/4.4.9/httpcomponents-core-4.4.9.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-core/4.4.9/httpcomponents-core-4.4.9.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-core/4.4.9/httpcomponents-core-4.4.9.pom (14 KB at 1881.1 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/httpcomponents/httpcomponents-parent/9/httpcomponents-parent-9.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-parent/9/httpcomponents-parent-9.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/httpcomponents/httpcomponents-parent/9/httpcomponents-parent-9.pom (34 KB at 3339.5 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/slf4j/slf4j-api/1.7.25/slf4j-api-1.7.25.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/slf4j/slf4j-api/1.7.25/slf4j-api-1.7.25.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/slf4j/slf4j-api/1.7.25/slf4j-api-1.7.25.pom (4 KB at 467.9 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/wagon/wagon-provider-api/3.1.0/wagon-provider-api-3.1.0.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-provider-api/3.1.0/wagon-provider-api-3.1.0.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-provider-api/3.1.0/wagon-provider-api-3.1.0.pom (2 KB at 266.6 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/commons-validator/commons-validator/1.6/commons-validator-1.6.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/commons-validator/commons-validator/1.6/commons-validator-1.6.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/commons-validator/commons-validator/1.6/commons-validator-1.6.pom (12 KB at 1469.7 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/commons-digester/commons-digester/1.8.1/commons-digester-1.8.1.pom > [INFO] Downloading: https://repo.maven.apache.org/maven2/commons-digester/commons-digester/1.8.1/commons-digester-1.8.1.pom > [INFO] Downloaded: https://repo.maven.apache.org/maven2/commons-digester/commons-digester/1.8.1/commons-digester-1.8.1.pom (10 KB at 1224.1 KB/sec) > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/reporting/maven-reporting-impl/3.0.0/maven-reporting-impl-3.0.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/shared/maven-shared-jar/1.2/maven-shared-jar-1.2.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/commons-collections/commons-collections/3.1/commons-collections-3.1.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/bcel/bcel/6.2/bcel-6.2.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-api/1.10.0/maven-scm-api-1.10.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-manager-plexus/1.10.0/maven-scm-manager-plexus-1.10.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-hg/1.10.0/maven-scm-provider-hg-1.10.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-perforce/1.10.0/maven-scm-provider-perforce-1.10.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-starteam/1.10.0/maven-scm-provider-starteam-1.10.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-svn-commons/1.10.0/maven-scm-provider-svn-commons-1.10.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-svnexe/1.10.0/maven-scm-provider-svnexe-1.10.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.10.0/maven-scm-provider-cvs-commons-1.10.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-cvsexe/1.10.0/maven-scm-provider-cvsexe-1.10.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-cvsjava/1.10.0/maven-scm-provider-cvsjava-1.10.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/netbeans/lib/cvsclient/20060125/cvsclient-20060125.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/ch/ethz/ganymed/ganymed-ssh2/build210/ganymed-ssh2-build210.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-git-commons/1.10.0/maven-scm-provider-git-commons-1.10.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/scm/maven-scm-provider-gitexe/1.10.0/maven-scm-provider-gitexe-1.10.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-logging-api/1.8/doxia-logging-api-1.8.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-core/1.8/doxia-core-1.8.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-decoration-model/1.8.1/doxia-decoration-model-1.8.1.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-skin-model/1.8.1/doxia-skin-model-1.8.1.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-module-xhtml/1.8/doxia-module-xhtml-1.8.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/codehaus/plexus/plexus-velocity/1.2/plexus-velocity-1.2.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/doxia/doxia-integration-tools/1.8.1/doxia-integration-tools-1.8.1.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/codehaus/plexus/plexus-i18n/1.0-beta-10/plexus-i18n-1.0-beta-10.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/codehaus/plexus/plexus-interpolation/1.25/plexus-interpolation-1.25.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/wagon/wagon-http-lightweight/3.1.0/wagon-http-lightweight-3.1.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/wagon/wagon-http-shared/3.1.0/wagon-http-shared-3.1.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/wagon/wagon-provider-api/3.1.0/wagon-provider-api-3.1.0.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/commons-validator/commons-validator/1.6/commons-validator-1.6.jar > [INFO] Downloading: http://repository.jboss.org/nexus/content/groups/public/commons-digester/commons-digester/1.8.1/commons-digester-1.8.1.jar > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/3.0.0/maven-reporting-impl-3.0.0.jar > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-shared-jar/1.2/maven-shared-jar-1.2.jar > [INFO] Downloading: https://repo.maven.apache.org/maven2/commons-collections/commons-collections/3.1/commons-collections-3.1.jar > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/bcel/bcel/6.2/bcel-6.2.jar > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-api/1.10.0/maven-scm-api-1.10.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/shared/maven-shared-jar/1.2/maven-shared-jar-1.2.jar (38 KB at 2888.4 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-manager-plexus/1.10.0/maven-scm-manager-plexus-1.10.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-impl/3.0.0/maven-reporting-impl-3.0.0.jar (18 KB at 897.2 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-hg/1.10.0/maven-scm-provider-hg-1.10.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-manager-plexus/1.10.0/maven-scm-manager-plexus-1.10.0.jar (11 KB at 535.1 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-perforce/1.10.0/maven-scm-provider-perforce-1.10.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-api/1.10.0/maven-scm-api-1.10.0.jar (108 KB at 4124.3 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-starteam/1.10.0/maven-scm-provider-starteam-1.10.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-hg/1.10.0/maven-scm-provider-hg-1.10.0.jar (68 KB at 2164.1 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-svn-commons/1.10.0/maven-scm-provider-svn-commons-1.10.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-perforce/1.10.0/maven-scm-provider-perforce-1.10.0.jar (85 KB at 2638.9 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-svnexe/1.10.0/maven-scm-provider-svnexe-1.10.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-starteam/1.10.0/maven-scm-provider-starteam-1.10.0.jar (72 KB at 2034.0 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.10.0/maven-scm-provider-cvs-commons-1.10.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-svn-commons/1.10.0/maven-scm-provider-svn-commons-1.10.0.jar (38 KB at 961.9 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvsexe/1.10.0/maven-scm-provider-cvsexe-1.10.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-svnexe/1.10.0/maven-scm-provider-svnexe-1.10.0.jar (80 KB at 1798.4 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvsjava/1.10.0/maven-scm-provider-cvsjava-1.10.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.10.0/maven-scm-provider-cvs-commons-1.10.0.jar (78 KB at 1684.6 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/netbeans/lib/cvsclient/20060125/cvsclient-20060125.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/commons-collections/commons-collections/3.1/commons-collections-3.1.jar (547 KB at 11622.5 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/ch/ethz/ganymed/ganymed-ssh2/build210/ganymed-ssh2-build210.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvsexe/1.10.0/maven-scm-provider-cvsexe-1.10.0.jar (31 KB at 619.1 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-git-commons/1.10.0/maven-scm-provider-git-commons-1.10.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/bcel/bcel/6.2/bcel-6.2.jar (659 KB at 12191.2 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-gitexe/1.10.0/maven-scm-provider-gitexe-1.10.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-cvsjava/1.10.0/maven-scm-provider-cvsjava-1.10.0.jar (45 KB at 817.5 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-logging-api/1.8/doxia-logging-api-1.8.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-git-commons/1.10.0/maven-scm-provider-git-commons-1.10.0.jar (35 KB at 590.1 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-core/1.8/doxia-core-1.8.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-logging-api/1.8/doxia-logging-api-1.8.jar (12 KB at 189.4 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.8.1/doxia-decoration-model-1.8.1.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/scm/maven-scm-provider-gitexe/1.10.0/maven-scm-provider-gitexe-1.10.0.jar (68 KB at 1089.0 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-skin-model/1.8.1/doxia-skin-model-1.8.1.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/ch/ethz/ganymed/ganymed-ssh2/build210/ganymed-ssh2-build210.jar (240 KB at 3795.1 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-module-xhtml/1.8/doxia-module-xhtml-1.8.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-skin-model/1.8.1/doxia-skin-model-1.8.1.jar (16 KB at 226.4 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-velocity/1.2/plexus-velocity-1.2.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.8.1/doxia-decoration-model-1.8.1.jar (61 KB at 857.9 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-integration-tools/1.8.1/doxia-integration-tools-1.8.1.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-module-xhtml/1.8/doxia-module-xhtml-1.8.jar (18 KB at 246.4 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-i18n/1.0-beta-10/plexus-i18n-1.0-beta-10.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-core/1.8/doxia-core-1.8.jar (165 KB at 2247.0 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-interpolation/1.25/plexus-interpolation-1.25.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/netbeans/lib/cvsclient/20060125/cvsclient-20060125.jar (605 KB at 7949.0 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-http-lightweight/3.1.0/wagon-http-lightweight-3.1.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-velocity/1.2/plexus-velocity-1.2.jar (8 KB at 102.6 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-http-shared/3.1.0/wagon-http-shared-3.1.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-i18n/1.0-beta-10/plexus-i18n-1.0-beta-10.jar (12 KB at 151.3 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/doxia/doxia-integration-tools/1.8.1/doxia-integration-tools-1.8.1.jar (46 KB at 589.2 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-provider-api/3.1.0/wagon-provider-api-3.1.0.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-http-lightweight/3.1.0/wagon-http-lightweight-3.1.0.jar (17 KB at 203.4 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/commons-validator/commons-validator/1.6/commons-validator-1.6.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-interpolation/1.25/plexus-interpolation-1.25.jar (84 KB at 1003.9 KB/sec) > [INFO] Downloading: https://repo.maven.apache.org/maven2/commons-digester/commons-digester/1.8.1/commons-digester-1.8.1.jar > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-http-shared/3.1.0/wagon-http-shared-3.1.0.jar (36 KB at 409.0 KB/sec) > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-provider-api/3.1.0/wagon-provider-api-3.1.0.jar (54 KB at 613.5 KB/sec) > [INFO] Downloaded: https://repo.maven.apache.org/maven2/commons-digester/commons-digester/1.8.1/commons-digester-1.8.1.jar (143 KB at 1471.0 KB/sec) > [INFO] Downloaded: https://repo.maven.apache.org/maven2/commons-validator/commons-validator/1.6/commons-validator-1.6.jar (182 KB at 1854.2 KB/sec) > [INFO] Downloaded: https://repo.maven.apache.org/maven2/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar (384 KB at 3870.3 KB/sec) > [WARNING] Error injecting: org.apache.maven.report.projectinfo.CiManagementReport > java.lang.NoClassDefFoundError: org/apache/maven/doxia/siterenderer/DocumentContent > at java.lang.Class.getDeclaredConstructors0(Native Method) > at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671) > at java.lang.Class.getDeclaredConstructors(Class.java:2020) > at com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:245) > at com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:99) > at com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:658) > at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:882) > at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:805) > at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:282) > at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:214) > at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:1006) > at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1038) > at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1001) > at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051) > at org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48) > at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81) > at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:53) > at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:65) > at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115) > at org.eclipse.sisu.bean.BeanScheduler$Activator.onProvision(BeanScheduler.java:176) > at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:126) > at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68) > at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:63) > at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:45) > at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) > at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092) > at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) > at org.eclipse.sisu.inject.Guice4$1.get(Guice4.java:162) > at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:81) > at org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:51) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:263) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:255) > at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:517) > at org.apache.maven.reporting.exec.DefaultMavenReportExecutor.getConfiguredMavenReport(DefaultMavenReportExecutor.java:332) > at org.apache.maven.reporting.exec.DefaultMavenReportExecutor.buildReportPlugin(DefaultMavenReportExecutor.java:282) > at org.apache.maven.reporting.exec.DefaultMavenReportExecutor.buildMavenReports(DefaultMavenReportExecutor.java:151) > at org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.getReports(AbstractSiteRenderingMojo.java:239) > at org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:124) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > 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) > Caused by: java.lang.ClassNotFoundException: org.apache.maven.doxia.siterenderer.DocumentContent > at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) > ... 60 more > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 29.562 s > [INFO] Finished at: 2018-08-20T03:29:07+00:00 > [INFO] Final Memory: 37M/1979M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project xtstest: Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site failed: A required class was missing while executing org.apache.maven.plugins:maven-site-plugin:3.4:site: org/apache/maven/doxia/siterenderer/DocumentContent > [ERROR] ----------------------------------------------------- > [ERROR] realm = plugin>org.apache.maven.plugins:maven-site-plugin:3.4 > [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > [ERROR] urls[0] = file:/home/jenkins/.m2/repository/org/apache/maven/plugins/maven-site-plugin/3.4/maven-site-plugin-3.4.jar > [ERROR] urls[1] = file:/home/jenkins/.m2/repository/org/apache/maven/reporting/maven-reporting-exec/1.2/maven-reporting-exec-1.2.jar > [ERROR] urls[2] = file:/home/jenkins/.m2/repository/org/apache/maven/reporting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar > [ERROR] urls[3] = file:/home/jenkins/.m2/repository/org/apache/maven/shared/maven-shared-utils/0.3/maven-shared-utils-0.3.jar > [ERROR] urls[4] = file:/home/jenkins/.m2/repository/com/google/code/findbugs/jsr305/2.0.1/jsr305-2.0.1.jar > [ERROR] urls[5] = file:/home/jenkins/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar > [ERROR] urls[6] = file:/home/jenkins/.m2/repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar > [ERROR] urls[7] = file:/home/jenkins/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar > [ERROR] urls[8] = file:/home/jenkins/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar > [ERROR] urls[9] = file:/home/jenkins/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar > [ERROR] urls[10] = file:/home/jenkins/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar > [ERROR] urls[11] = file:/home/jenkins/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar > [ERROR] urls[12] = file:/home/jenkins/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar > [ERROR] urls[13] = file:/home/jenkins/.m2/repository/org/apache/maven/maven-archiver/2.4.2/maven-archiver-2.4.2.jar > [ERROR] urls[14] = file:/home/jenkins/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.6/doxia-sink-api-1.6.jar > [ERROR] urls[15] = file:/home/jenkins/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.6/doxia-logging-api-1.6.jar > [ERROR] urls[16] = file:/home/jenkins/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar > [ERROR] urls[17] = file:/home/jenkins/.m2/repository/org/apache/maven/doxia/doxia-core/1.6/doxia-core-1.6.jar > [ERROR] urls[18] = file:/home/jenkins/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar > [ERROR] urls[19] = file:/home/jenkins/.m2/repository/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.jar > [ERROR] urls[20] = file:/home/jenkins/.m2/repository/org/apache/httpcomponents/httpclient/4.0.2/httpclient-4.0.2.jar > [ERROR] urls[21] = file:/home/jenkins/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar > [ERROR] urls[22] = file:/home/jenkins/.m2/repository/commons-codec/commons-codec/1.3/commons-codec-1.3.jar > [ERROR] urls[23] = file:/home/jenkins/.m2/repository/org/apache/httpcomponents/httpcore/4.0.1/httpcore-4.0.1.jar > [ERROR] urls[24] = file:/home/jenkins/.m2/repository/xmlunit/xmlunit/1.5/xmlunit-1.5.jar > [ERROR] urls[25] = file:/home/jenkins/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.6/doxia-module-xhtml-1.6.jar > [ERROR] urls[26] = file:/home/jenkins/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.6/doxia-module-apt-1.6.jar > [ERROR] urls[27] = file:/home/jenkins/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.6/doxia-module-xdoc-1.6.jar > [ERROR] urls[28] = file:/home/jenkins/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.6/doxia-module-fml-1.6.jar > [ERROR] urls[29] = file:/home/jenkins/.m2/repository/org/apache/maven/doxia/doxia-module-markdown/1.6/doxia-module-markdown-1.6.jar > [ERROR] urls[30] = file:/home/jenkins/.m2/repository/org/pegdown/pegdown/1.2.1/pegdown-1.2.1.jar > [ERROR] urls[31] = file:/home/jenkins/.m2/repository/org/parboiled/parboiled-java/1.1.4/parboiled-java-1.1.4.jar > [ERROR] urls[32] = file:/home/jenkins/.m2/repository/org/parboiled/parboiled-core/1.1.4/parboiled-core-1.1.4.jar > [ERROR] urls[33] = file:/home/jenkins/.m2/repository/org/ow2/asm/asm/4.1/asm-4.1.jar > [ERROR] urls[34] = file:/home/jenkins/.m2/repository/org/ow2/asm/asm-tree/4.1/asm-tree-4.1.jar > [ERROR] urls[35] = file:/home/jenkins/.m2/repository/org/ow2/asm/asm-analysis/4.1/asm-analysis-4.1.jar > [ERROR] urls[36] = file:/home/jenkins/.m2/repository/org/ow2/asm/asm-util/4.1/asm-util-4.1.jar > [ERROR] urls[37] = file:/home/jenkins/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.jar > [ERROR] urls[38] = file:/home/jenkins/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.6/doxia-decoration-model-1.6.jar > [ERROR] urls[39] = file:/home/jenkins/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.6/doxia-site-renderer-1.6.jar > [ERROR] urls[40] = file:/home/jenkins/.m2/repository/org/apache/velocity/velocity-tools/2.0/velocity-tools-2.0.jar > [ERROR] urls[41] = file:/home/jenkins/.m2/repository/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar > [ERROR] urls[42] = file:/home/jenkins/.m2/repository/commons-digester/commons-digester/1.8/commons-digester-1.8.jar > [ERROR] urls[43] = file:/home/jenkins/.m2/repository/commons-chain/commons-chain/1.1/commons-chain-1.1.jar > [ERROR] urls[44] = file:/home/jenkins/.m2/repository/commons-validator/commons-validator/1.3.1/commons-validator-1.3.1.jar > [ERROR] urls[45] = file:/home/jenkins/.m2/repository/dom4j/dom4j/1.1/dom4j-1.1.jar > [ERROR] urls[46] = file:/home/jenkins/.m2/repository/sslext/sslext/1.2-0/sslext-1.2-0.jar > [ERROR] urls[47] = file:/home/jenkins/.m2/repository/org/apache/struts/struts-core/1.3.8/struts-core-1.3.8.jar > [ERROR] urls[48] = file:/home/jenkins/.m2/repository/antlr/antlr/2.7.2/antlr-2.7.2.jar > [ERROR] urls[49] = file:/home/jenkins/.m2/repository/org/apache/struts/struts-taglib/1.3.8/struts-taglib-1.3.8.jar > [ERROR] urls[50] = file:/home/jenkins/.m2/repository/org/apache/struts/struts-tiles/1.3.8/struts-tiles-1.3.8.jar > [ERROR] urls[51] = file:/home/jenkins/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar > [ERROR] urls[52] = file:/home/jenkins/.m2/repository/org/apache/maven/doxia/doxia-integration-tools/1.6/doxia-integration-tools-1.6.jar > [ERROR] urls[53] = file:/home/jenkins/.m2/repository/org/codehaus/plexus/plexus-archiver/2.4.3/plexus-archiver-2.4.3.jar > [ERROR] urls[54] = file:/home/jenkins/.m2/repository/org/codehaus/plexus/plexus-io/2.0.8/plexus-io-2.0.8.jar > [ERROR] urls[55] = file:/home/jenkins/.m2/repository/org/apache/commons/commons-compress/1.5/commons-compress-1.5.jar > [ERROR] urls[56] = file:/home/jenkins/.m2/repository/org/tukaani/xz/1.2/xz-1.2.jar > [ERROR] urls[57] = file:/home/jenkins/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar > [ERROR] urls[58] = file:/home/jenkins/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar > [ERROR] urls[59] = file:/home/jenkins/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar > [ERROR] urls[60] = file:/home/jenkins/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar > [ERROR] urls[61] = file:/home/jenkins/.m2/repository/org/codehaus/plexus/plexus-utils/3.0.15/plexus-utils-3.0.15.jar > [ERROR] urls[62] = file:/home/jenkins/.m2/repository/org/mortbay/jetty/jetty/6.1.25/jetty-6.1.25.jar > [ERROR] urls[63] = file:/home/jenkins/.m2/repository/org/mortbay/jetty/servlet-api/2.5-20081211/servlet-api-2.5-20081211.jar > [ERROR] urls[64] = file:/home/jenkins/.m2/repository/org/mortbay/jetty/jetty-util/6.1.25/jetty-util-6.1.25.jar > [ERROR] urls[65] = file:/home/jenkins/.m2/repository/commons-lang/commons-lang/2.5/commons-lang-2.5.jar > [ERROR] urls[66] = file:/home/jenkins/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar > [ERROR] Number of foreign imports: 1 > [ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]] > [ERROR] > [ERROR] -----------------------------------------------------: org.apache.maven.doxia.siterenderer.DocumentContent > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException > JACOCO profile tests failed (http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/41/): XTS localjunit xtstest build failed > XTS localjunit xtstest build failed > Build step 'Execute shell' marked build as failure > Archiving artifacts > Finished: FAILURE > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3050) CMRIntegrationTest consistently fails on CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3050. ------------------------------- > CMRIntegrationTest consistently fails on CI > ------------------------------------------- > > Key: JBTM-3050 > URL: https://issues.jboss.org/browse/JBTM-3050 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Ondra Chaloupka > Priority: Blocker > Fix For: 5.9.1.Final > > > Test com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest is failing on our CI cluster, for example: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/PROFILE=MAIN,jdk=jdk8.latest,label=linux/239/ > fails with the output: > {quote} > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.962 sec <<< FAILURE! - in com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest > com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest Time elapsed: 4.962 sec <<< ERROR! > java.lang.RuntimeException: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "WFLYCTL0216: Management resource '[(\"deployment\" => \"test.war\")]' not found" > Caused by: org.jboss.as.arquillian.container.ManagementClient$UnSuccessfulOperationException: "WFLYCTL0216: Management resource '[(\"deployment\" => \"test.war\")]' not found" > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3048) Some AbstractRecord test classes return invalid TwoPhaseOutcome values In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3048. ------------------------------- > Some AbstractRecord test classes return invalid TwoPhaseOutcome values > ---------------------------------------------------------------------- > > Key: JBTM-3048 > URL: https://issues.jboss.org/browse/JBTM-3048 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.9.1.Final > > > The test classes > arjuna/tests/classes/com/hp/mwtests/ts/arjuna/atomicaction/AtomicActionUnitTest.java > arjuna/tests/classes/com/hp/mwtests/ts/arjuna/atomicaction/TxStatsSystemErrorUnitTest.java > contain inner class implementations of AbstractRecord that return invalid values from the action lifecycle methods. For example: > {code} > public int topLevelCommit() {return 0;} > {code} > which maps to TwoPhaseOutcome.PREPARE_OK which is wrong. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3045) JTA CDI regression (or Standalone JTA 1.2 Quickstart failure) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3045. ------------------------------- > JTA CDI regression (or Standalone JTA 1.2 Quickstart failure) > ------------------------------------------------------------- > > Key: JBTM-3045 > URL: https://issues.jboss.org/browse/JBTM-3045 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Priority: Critical > Fix For: 5.9.1.Final > > > The recent changes to our JTA CDI support (https://issues.jboss.org/browse/JBTM-3044) have either caused a regression or the Standalone JTA 1.2 Quickstart needs updating. The failure is: > {quote} > testMandatoryTransactionWithExistingTransaction(org.jboss.narayana.quickstarts.jta.TestCase) Time elapsed: 0.536 sec <<< ERROR! > javax.enterprise.inject.CreationException: Not a compound name: TransactionManager > {quote} > See for example CI run http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-quickstarts/159/console > If the issue does turn out to be a regression then the priority needs to be marked as Critical. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3044) Decouple TransactionContext from JNDI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3044. ------------------------------- > Decouple TransactionContext from JNDI > ------------------------------------- > > Key: JBTM-3044 > URL: https://issues.jboss.org/browse/JBTM-3044 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Affects Versions: 5.9.0.Final > Reporter: Laird Nelson > Assignee: Laird Nelson > Priority: Major > Fix For: 5.9.1.Final > > > I've submitted a [pull request|https://github.com/jbosstm/narayana/pull/1346] that makes the CDI pieces of the Narayana project play more nicely with dependency injection in general. > There has been a [lengthy discussion|https://developer.jboss.org/thread/278367] of the issues. > [~tomjenkinson] indicated I should file an issue here to track it, so here it is. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3043) REST-AT to JTA Bridge Quickstart failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3043. ------------------------------- > REST-AT to JTA Bridge Quickstart failing > ---------------------------------------- > > Key: JBTM-3043 > URL: https://issues.jboss.org/browse/JBTM-3043 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.9.1.Final > > > ------------------------------------------------------- > Running org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest > Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 6.973 sec <<< FAILURE! - in org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest > testCommitWithTwoTasks(org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest) Time elapsed: 0.8 sec <<< FAILURE! > java.lang.AssertionError: expected:<201> but was:<500> > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.createTask(TaskResourceTest.java:190) > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.testCommitWithTwoTasks(TaskResourceTest.java:147) > testRollback(org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest) Time elapsed: 0.094 sec <<< FAILURE! > java.lang.AssertionError: expected:<201> but was:<500> > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.createTask(TaskResourceTest.java:190) > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.testRollback(TaskResourceTest.java:130) > testCommit(org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest) Time elapsed: 0.066 sec <<< FAILURE! > java.lang.AssertionError: expected:<201> but was:<500> > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.createTask(TaskResourceTest.java:190) > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.testCommit(TaskResourceTest.java:111) > testRollbackWithTwoTasks(org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest) Time elapsed: 0.063 sec <<< FAILURE! > java.lang.AssertionError: expected:<201> but was:<500> > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.createTask(TaskResourceTest.java:190) > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.testRollbackWithTwoTasks(TaskResourceTest.java:169) -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:02:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:02:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3041) Include a test to run the microprofile-lra TCK In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3041. ------------------------------- > Include a test to run the microprofile-lra TCK > ---------------------------------------------- > > Key: JBTM-3041 > URL: https://issues.jboss.org/browse/JBTM-3041 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.1.Final > > > The narayana implementation of the LRA spec should include a test to validate that it conforms to the TCK at https://github.com/eclipse/microprofile-lra/tree/master/tck -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3030) Moving the tomcat-jta to the JWS web-servers repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3030. ------------------------------- > Moving the tomcat-jta to the JWS web-servers repo > ------------------------------------------------- > > Key: JBTM-3030 > URL: https://issues.jboss.org/browse/JBTM-3030 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tomcat > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Major > Fix For: 5.9.1.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3029) SpecIT.timeLimitRequiredLRA failed on Mac CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3029. ------------------------------- > SpecIT.timeLimitRequiredLRA failed on Mac CI > -------------------------------------------- > > Key: JBTM-3029 > URL: https://issues.jboss.org/browse/JBTM-3029 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.8.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.1.Final > > > Failed on CI run http://172.17.130.4:8083/job/narayana-mac/PROFILE=MAIN,jdk=jdk8.latest,label=mac/423/console > The test does a timed wait on a condition which eventually times out. The test may just need tweaking or alternatively a more sophisticated test may be required. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2824) Check that the changes for JDK-9 support still build with JDK-8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2824. ------------------------------- > 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.9.1.Final > > > 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) From issues at jboss.org Tue Dec 4 06:03:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3073) Do not mandate JAX-RS annotations on @Compensate/@Complete methods In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3073: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > Do not mandate JAX-RS annotations on @Compensate/@Complete methods > ------------------------------------------------------------------ > > Key: JBTM-3073 > URL: https://issues.jboss.org/browse/JBTM-3073 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Cloned from [https://github.com/eclipse/microprofile-lra/issues/35|http://example.com]: > It is up to the implementation on how the Compensate methods are called. > This could be through JAX-RS calls but this should not be the only way (although an implementation will probably only implement one method). This makes it easier to use the 'events' way of coordination. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3072) Add a test to verify the behaviour of LRA.Type.REQUIRES_NEW combined with LRA.delayClose In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3072: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > 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 > Priority: Major > 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) From issues at jboss.org Tue Dec 4 06:03:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3071) Windows automation of the LRA examples quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3071: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > Windows automation of the LRA examples quickstarts > -------------------------------------------------- > > Key: JBTM-3071 > URL: https://issues.jboss.org/browse/JBTM-3071 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The LRA examples quickstarts (https://issues.jboss.org/browse/JBTM-3063) contain a bash script to run the examples. We need the equivalent for running on Windows. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3062) Include a test for LRA context propagation across a "non-LRA aware" service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3062: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > Include a test for LRA context propagation across a "non-LRA aware" service > --------------------------------------------------------------------------- > > Key: JBTM-3062 > URL: https://issues.jboss.org/browse/JBTM-3062 > 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 > > > If a microservice A that wants to participate in an LRA and calls microservice B (which does not have specific LRA behaviour) and service A in turn calls microservice C (which does have specific LRA behaviour), then B should not need to be annotated with @LRA. A test is needed for this behaviour. > This issue relates to https://github.com/eclipse/microprofile-lra/issues/7 -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3065) Check that starting LRA's via CDI and API in the same method works In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3065: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > Check that starting LRA's via CDI and API in the same method works > ------------------------------------------------------------------ > > Key: JBTM-3065 > URL: https://issues.jboss.org/browse/JBTM-3065 > 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 > > > The LRA spec supports starting LRA's via a Java API or via Java annotations. If the two approaches are used together in the same resource method then the LRA started via the API should be nested inside the one started by an annotation. > If the annotated class also contains @Compensate and @Complete annotations (which means that the resource should join the outer LRA) and the resource method Joins the nested LRA then the resource should receive callbacks for both the outer and nested LRA's. > The following code shows an example: > {code} > @PUT > @LRA(LRA.Type.REQUIRES_NEW) // starts a new LRA on entry > public String doInTransaction() { > URL lraId = lraClient.startLRA(...); // starts a nested LRA > lraClient.join(...) // join the nested LRA > lraClient.closeLRA(lraId); // close the nested LRA > // assert that the nested callbacks were invoked > // assert that the callbacks for the outer LRA have not been called yet > } > {code} > Similar comments apply if the resource joins via the LRAManagement API: > {code} > @Inject > private LRAManagement lraManagement; > public String doInTransaction() { > lraManagement.joinLRA(this, lraId, 0L, TimeUnit.SECONDS); > // etc > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3058) Add STM tests that verify nested transactions are closed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3058: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > Add STM tests that verify nested transactions are closed > -------------------------------------------------------- > > Key: JBTM-3058 > URL: https://issues.jboss.org/browse/JBTM-3058 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM, Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > STM implements "Closed Nested Transactions" as opposed to Flattened or Open. We need a test which demonstrates that nested transactions follow the closed model. > Furthermore, STM implementations can differ in how transactional code and non-transactional code are isolated from each other (with respect to visibility of updates during a transaction). Add a test that verifies that we use the "Weak Isolation" model. > Details of the expected behaviour is covered in the Sept 2018 jbossts blog entitled "[Tips on how to evaluate STM implementations|http://example.com|https://jbossts.blogspot.com/2018/09/tips-on-how-to-evaluate-stm.html]" -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3051) LRA test timeLimitRequiredLRA failure on JDK 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3051: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > 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) From issues at jboss.org Tue Dec 4 06:03:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3046) REST-AT PerformanceTest occasionally hangs on Windows CI runs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3046: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > REST-AT PerformanceTest occasionally hangs on Windows CI runs > ------------------------------------------------------------- > > Key: JBTM-3046 > URL: https://issues.jboss.org/browse/JBTM-3046 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > Attachments: threaddump.txt > > > The test runs from the rts/at/tx/pom.xml module (org.jboss.narayana.rts:restat). The hanging thread seems to be a coordinator request to start an inVM REST-AT transaction. The coordinator is running in an Undertow container and the failing test is org.jboss.jbossts.star.test.PerformanceTest > See the attachment for the stacktraces. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3042) API to get detailed LRA information should not include stats type data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3042: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > API to get detailed LRA information should not include stats type data > ---------------------------------------------------------------------- > > Key: JBTM-3042 > URL: https://issues.jboss.org/browse/JBTM-3042 > 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 > > > The interface to obtain information about an LRA [1] includes data such as when the LRA was started and ended. This type of information is more appropriate to monitoring and statistics gathering rather than core LRA info. Not all implementations may want to / be able to report these accurately so perhaps move them to an extended optional interface > [1] https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-client/src/main/java/io/narayana/lra/client/LRAInfoImpl.java#L90 -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:02 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3020) Add ability for resources to indicate XA_RDONLY on end In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3020: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > Add ability for resources to indicate XA_RDONLY on end > ------------------------------------------------------ > > Key: JBTM-3020 > URL: https://issues.jboss.org/browse/JBTM-3020 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: David Lloyd > Assignee: Ondra Chaloupka > Priority: Major > Fix For: 5.next > > > As discussed in WFLY-10258 and https://developer.jboss.org/message/982097, this request is to add the ability for an XAResource to indicate (on end) that it has no committable work, which would act as a hint to order that XAResource at an earlier point of prepare processing, which will in turn increase the chances of a 1PC optimization occurring. > As expressed in the forum thread, the mechanism should not interfere with compatibility. One possible way to do this would be to introduce an enhanced subinterface of XAResource which includes a method like this: > {code:java} > int endWithResult(Xid xid, int flags) throws XAException; > {code} > The method behaves semantically identically to {{XAResource#end}} , except it would be allowed to return {{XA_RDONLY}} or {{XA_OK}}. A value of {{XA_RDONLY}} would indicate that the resource expects to return {{XA_RDONLY}} in response to a {{prepare}} call, whereas a value of {{XA_OK}} indicates that the resource's future {{prepare}} result cannot yet be decided or will be {{XA_OK}}. An invalid result should probably behave equivalently to an {{XAException}} being thrown by the {{end}} method. {{XAER_RMERR}} seems like a reasonable error code for this case. An alternative strategy would be to treat an invalid return value as being equivalent to {{XA_OK}}. > Since it's a subinterface of {{XAResource}}, it could also define the following default method: > {code:java} > default void end(Xid xid, int flags) throws XAException { > endWithResult(xid, flags); > } > {code} > This method would not need to be called by the TM, but would correctly satisfy the {{XAResource}} contract without requiring the user to implement the redundant method. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:02 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3019) Testsuite: Docker controller leaves stray volumes and fills up disk space unnecessairly over time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3019: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > Testsuite: Docker controller leaves stray volumes and fills up disk space unnecessairly over time > ------------------------------------------------------------------------------------------------- > > Key: JBTM-3019 > URL: https://issues.jboss.org/browse/JBTM-3019 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.8.1.Final > Environment: Docker enabled Jenkins slaves > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Priority: Minor > Fix For: 5.next > > > h3. Problem > The Docker controller that allocates databases as Docker containers cleans up containers and does not leave unnecessary images: > {code} > [root at karm-centos7-x86-64 ~]# docker images > REPOSITORY TAG IMAGE ID CREATED SIZE > docker.io/postgres 9.4 26bd9b04b948 6 days ago 232 MB > docker.io/postgres 10 0965cdc98045 6 days ago 234 MB > docker.io/postgres ed5db6e669ff 7 weeks ago 263 MB > docker.io/postgres 30121e967865 7 weeks ago 289 MB > [root at karm-centos7-x86-64 ~]# docker ps -a > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > [root at karm-centos7-x86-64 ~]# > {code} > Although it leaves stray container volumes for some reason: > {code} > [root at karm-centos7-x86-64 ~]# du -hs /var/lib/docker-latest/volumes > 15G /var/lib/docker-latest/volumes > [root at karm-centos7-x86-64 ~]# docker volume ls -qf dangling=true | wc -l > 409 > {code} > It unnecessarily clogs the slaves' disk space. The 15G of garbage has been created over dozens and dozens of builds with at least two containers each, but it shouldn't be happening anyway. > h3. Call to action > Review whether [removeContainerCmd|https://github.com/jbosstm/narayana/blob/master/tools/src/main/java/io/narayana/db/PostgreContainerAllocator.java#L264] is supposed to be enough to not only remove the container but to also remove its volume. > h3. Workaround > {code} > docker volume prune > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:02 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2968) Some JTS quickstarts run with JacORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2968: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > Some JTS quickstarts run with JacORB > ------------------------------------ > > Key: JBTM-2968 > URL: https://issues.jboss.org/browse/JBTM-2968 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Some of the JTS quickstarts are using JacORB. The narayana project has since changed the default ORB (OpenJDK ORB) so we should change the quickstarts to use the new default. The affected poms are: > ArjunaJTS/pom.xml > ArjunaJTS/standalone/pom.xml > ArjunaJTS/trailmap/pom.xml -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:02 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2967) Some quickstarts are not tested in CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2967: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > Some quickstarts are not tested in CI > ------------------------------------- > > Key: JBTM-2967 > URL: https://issues.jboss.org/browse/JBTM-2967 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Most quickstarts used to ship with a run.[sh|bat] script for running the quickstart and we used to test them in CI by executing the run script. At some point we changed the CI script (scripts/hudson/quickstart.sh) to just run the pom instead (./build.sh -B clean install). Since not all poms execute their run script we aren't getting full CI coverage. > This JIRA is to go through each quickstart and ensure the the pom does indeed exercise the quickstart. > The following poms do execute a run script > transactionaldriver-jpa-and-tomcat/pom.xml > rts/at/simple/pom.xml > rts/lra/lra-test/pom.xml > ArjunaJTS/interop/glassfish/pom.xml > transactionaldriver-and-tomcat/pom.xml > spring/camel-with-narayana-spring-boot/pom.xml > The following quickstarts contain run scripts: > transactionaldriver-jpa-and-tomcat/run.sh > ArjunaCore/txoj/run.sh > jboss-as/build/target/wildfly-9.0.0.CR1-SNAPSHOT/bin/run.sh > ArjunaJTA/object_store/run.sh > ArjunaJTA/maven/run.sh > ArjunaJTA/recovery/run.sh > ArjunaJTA/javax_transaction/run.sh > rts/at/undertow/run.sh > rts/at/recovery/recovery2/run.sh > rts/at/recovery/recovery1/run.sh > rts/at/simple/run.sh > rts/at/service/service2b/run.sh > rts/at/service/service2/run.sh > rts/at/service/service1b/run.sh > rts/at/service/service1/run.sh > rts/at/demo/run.sh > rts/lra/run.sh > ArjunaJTS/standalone/run.sh > ArjunaJTS/interop/glassfish/run.sh > ArjunaJTS/recovery/run.sh -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:03:02 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2912) Upgrade JMS transactional driver to JMS 2.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2912: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.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) From issues at jboss.org Tue Dec 4 06:03:02 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Tue, 4 Dec 2018 06:03:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2867) Investigate un-_workList protected access to _work object In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2867: -------------------------------- Fix Version/s: 5.next (was: 5.9.1.Final) > Investigate un-_workList protected access to _work object > --------------------------------------------------------- > > Key: JBTM-2867 > URL: https://issues.jboss.org/browse/JBTM-2867 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Major > Fix For: 5.next > > > During investigation of JBTM-2865 it was detected that the _work object can be accessed outside of the _workList synchronized block. Notably this seems to be a .remove() operation on it which can mutate the struct and may cause issues. > For example, this looks wrong: > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef20978dc5d30ac5c2/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/CacheStore.java#L703 > If > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef20978dc5d30ac5c2/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/CacheStore.java#L187 -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 4 06:21:01 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Tue, 4 Dec 2018 06:21:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3085) Compensations test fail because of WildFly module changes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1392 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Compensations test fail because of WildFly module changes > --------------------------------------------------------- > > Key: JBTM-3085 > URL: https://issues.jboss.org/browse/JBTM-3085 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Affects Versions: 5.9.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Major > > There was change in module dependencies for compensations (see at https://issues.jboss.org/browse/WFLY-11421) which requires changes into testsuite of compensations. > Currently the narayana CI XTS tests are failing. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Dec 5 05:04:00 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Wed, 5 Dec 2018 05:04:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3085) Compensations test fail because of WildFly module changes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3085: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Compensations test fail because of WildFly module changes > --------------------------------------------------------- > > Key: JBTM-3085 > URL: https://issues.jboss.org/browse/JBTM-3085 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Affects Versions: 5.9.0.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Major > > There was change in module dependencies for compensations (see at https://issues.jboss.org/browse/WFLY-11421) which requires changes into testsuite of compensations. > Currently the narayana CI XTS tests are failing. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Thu Dec 6 12:37:00 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Thu, 6 Dec 2018 12:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3079) InboundBridge recovery aborts live transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3079: -------------------------------- Fix Version/s: 5.next 5.5.34.Final > InboundBridge recovery aborts live transactions > ----------------------------------------------- > > Key: JBTM-3079 > URL: https://issues.jboss.org/browse/JBTM-3079 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.5.32.Final, 5.9.0.Final > Environment: EAP 7.1.5 / 5.5.32.Final > Reporter: Jonathan Halliday > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 5.5.34.Final, 5.next > > Attachments: jbtm3079.patch > > > During a recovery pass, the InboundBridgeRecoveryManager scans for subordinate XA branches that may need cleanup. The filtering process applied by checkXid correctly excludes tx that are not owned by the bridge, but fails to ignore those that are owned but also still live. Therefore, a race condition exists such that the recovery process may incorrectly abort a branch if invoked between the prepare and commit steps, resulting in data corruption relative to other committed branches from the parent i.e. Heuristic outcomes. > TRACE [org.jboss.jbossts.txbridge] (TaskWorker-3) BridgeDurableParticipant.prepare(Xid=< 131080, 35, 64, ... >) > TRACE [org.jboss.jbossts.txbridge] (Periodic Recovery) rolling back orphaned subordinate tx < 131080, 35, 64, ... > > ERROR [org.jboss.jbossts.txbridge] (TaskWorker-8) ARJUNA033004: commit on Xid=< 131080, 35, 64, ... > failed: javax.transaction.xa.XAException > It is necessary to enhance checkXid to validate against known live tx. The easiest way would seem to be to have the InboundBridgeManager singleton hold a lookup table of live tx, effectively a secondary index into its existing collection of InboundBridges, against which the recovery system can validate the in-doubt Xid. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Thu Dec 6 12:38:00 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Thu, 6 Dec 2018 12:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3034) CMR recovery wrongly handles commit and rollback In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-3034: --------------------------------- > CMR recovery wrongly handles commit and rollback > ------------------------------------------------- > > Key: JBTM-3034 > URL: https://issues.jboss.org/browse/JBTM-3034 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.8.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Major > Fix For: 5.5.33.Final, 5.9.0.Final > > Attachments: JBTM-3034-xarm-to-query-cmrrm.diff > > > The recovery of CMR works wrongly. > For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. > # cmr resource prepare (no real action on the local transction) > # xa resource prepare (prepared in real as XA) > # cmr resource commit (commiting the local transaction) > # JVM crash > # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. > This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. > This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Thu Dec 6 12:38:00 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Thu, 6 Dec 2018 12:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3034) CMR recovery wrongly handles commit and rollback In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-3034: -------------------------------- Fix Version/s: 5.5.33.Final > CMR recovery wrongly handles commit and rollback > ------------------------------------------------- > > Key: JBTM-3034 > URL: https://issues.jboss.org/browse/JBTM-3034 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.8.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Major > Fix For: 5.5.33.Final, 5.9.0.Final > > Attachments: JBTM-3034-xarm-to-query-cmrrm.diff > > > The recovery of CMR works wrongly. > For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. > # cmr resource prepare (no real action on the local transction) > # xa resource prepare (prepared in real as XA) > # cmr resource commit (commiting the local transaction) > # JVM crash > # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. > This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. > This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Thu Dec 6 12:38:01 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Thu, 6 Dec 2018 12:38:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3034) CMR recovery wrongly handles commit and rollback In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-3034. ------------------------------- Resolution: Done > CMR recovery wrongly handles commit and rollback > ------------------------------------------------- > > Key: JBTM-3034 > URL: https://issues.jboss.org/browse/JBTM-3034 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.8.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Major > Fix For: 5.9.0.Final, 5.5.33.Final > > Attachments: JBTM-3034-xarm-to-query-cmrrm.diff > > > The recovery of CMR works wrongly. > For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. > # cmr resource prepare (no real action on the local transction) > # xa resource prepare (prepared in real as XA) > # cmr resource commit (commiting the local transaction) > # JVM crash > # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. > This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. > This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Sat Dec 8 03:07:00 2018 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Sat, 8 Dec 2018 03:07:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3086) dependentLRA test failure In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-3086: -------------------------------------- Summary: dependentLRA test failure Key: JBTM-3086 URL: https://issues.jboss.org/browse/JBTM-3086 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.9.1.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The TCK test [dependentLRA|https://github.com/eclipse/microprofile-lra/blob/master/tck/src/main/java/org/eclipse/microprofile/lra/tck/TckTests.java#L461] in the microprofile-lra test suite fails if [terminal attribute of the LRA annotation|https://github.com/eclipse/microprofile-lra/blob/master/api/src/main/java/org/eclipse/microprofile/lra/annotation/LRA.java#L176] is set to true. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Sat Dec 8 03:07:00 2018 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Sat, 8 Dec 2018 03:07:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3086) dependentLRA test failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3086: ----------------------------------- Description: The TCK test [dependentLRA|https://github.com/eclipse/microprofile-lra/blob/master/tck/src/main/java/org/eclipse/microprofile/lra/tck/TckTests.java#L461] in the microprofile-lra test suite fails if the [terminal attribute of the LRA annotation|https://github.com/eclipse/microprofile-lra/blob/master/api/src/main/java/org/eclipse/microprofile/lra/annotation/LRA.java#L176] is set to true. (was: The TCK test [dependentLRA|https://github.com/eclipse/microprofile-lra/blob/master/tck/src/main/java/org/eclipse/microprofile/lra/tck/TckTests.java#L461] in the microprofile-lra test suite fails if [terminal attribute of the LRA annotation|https://github.com/eclipse/microprofile-lra/blob/master/api/src/main/java/org/eclipse/microprofile/lra/annotation/LRA.java#L176] is set to true.) > dependentLRA test failure > ------------------------- > > Key: JBTM-3086 > URL: https://issues.jboss.org/browse/JBTM-3086 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The TCK test [dependentLRA|https://github.com/eclipse/microprofile-lra/blob/master/tck/src/main/java/org/eclipse/microprofile/lra/tck/TckTests.java#L461] in the microprofile-lra test suite fails if the [terminal attribute of the LRA annotation|https://github.com/eclipse/microprofile-lra/blob/master/api/src/main/java/org/eclipse/microprofile/lra/annotation/LRA.java#L176] is set to true. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Sat Dec 8 03:18:00 2018 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Sat, 8 Dec 2018 03:18:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3086) dependentLRA test failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672310#comment-13672310 ] Michael Musgrove commented on JBTM-3086: ---------------------------------------- The test is invokes a method annotated with LRA NOT_SUPPORTED and the method then starts an LRA via the API. This LRA should be available to the caller when the annotated method completes. However [microprofile lra issue 40|https://github.com/eclipse/microprofile-lra/issues/40] changed the default behaviour of the `terminal` attribute of an LRA which uncovered this bug since now the LRA started via the client API is incorrectly closed by the implementation (see the ServerLRAFilter JAX-RS filter). > dependentLRA test failure > ------------------------- > > Key: JBTM-3086 > URL: https://issues.jboss.org/browse/JBTM-3086 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The TCK test [dependentLRA|https://github.com/eclipse/microprofile-lra/blob/master/tck/src/main/java/org/eclipse/microprofile/lra/tck/TckTests.java#L461] in the microprofile-lra test suite fails if the [terminal attribute of the LRA annotation|https://github.com/eclipse/microprofile-lra/blob/master/api/src/main/java/org/eclipse/microprofile/lra/annotation/LRA.java#L176] is set to true. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Dec 11 05:17:00 2018 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Tue, 11 Dec 2018 05:17:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-3087: -------------------------------------- Summary: Ensure the LRA implementation is up to date Key: JBTM-3087 URL: https://issues.jboss.org/browse/JBTM-3087 Project: JBoss Transaction Manager Issue Type: Task Components: LRA Affects Versions: 5.9.1.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Thu Dec 13 08:43:00 2018 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Thu, 13 Dec 2018 08:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #1395 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:01 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3079) InboundBridge recovery aborts live transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka closed JBTM-3079. --------------------------------- > InboundBridge recovery aborts live transactions > ----------------------------------------------- > > Key: JBTM-3079 > URL: https://issues.jboss.org/browse/JBTM-3079 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.5.32.Final, 5.9.0.Final > Environment: EAP 7.1.5 / 5.5.32.Final > Reporter: Jonathan Halliday > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 5.5.34.Final, 5.9.2.Final > > Attachments: jbtm3079.patch > > > During a recovery pass, the InboundBridgeRecoveryManager scans for subordinate XA branches that may need cleanup. The filtering process applied by checkXid correctly excludes tx that are not owned by the bridge, but fails to ignore those that are owned but also still live. Therefore, a race condition exists such that the recovery process may incorrectly abort a branch if invoked between the prepare and commit steps, resulting in data corruption relative to other committed branches from the parent i.e. Heuristic outcomes. > TRACE [org.jboss.jbossts.txbridge] (TaskWorker-3) BridgeDurableParticipant.prepare(Xid=< 131080, 35, 64, ... >) > TRACE [org.jboss.jbossts.txbridge] (Periodic Recovery) rolling back orphaned subordinate tx < 131080, 35, 64, ... > > ERROR [org.jboss.jbossts.txbridge] (TaskWorker-8) ARJUNA033004: commit on Xid=< 131080, 35, 64, ... > failed: javax.transaction.xa.XAException > It is necessary to enhance checkXid to validate against known live tx. The easiest way would seem to be to have the InboundBridgeManager singleton hold a lookup table of live tx, effectively a secondary index into its existing collection of InboundBridges, against which the recovery system can validate the in-doubt Xid. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:01 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3087: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:02 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3086) dependentLRA test failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3086: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > dependentLRA test failure > ------------------------- > > Key: JBTM-3086 > URL: https://issues.jboss.org/browse/JBTM-3086 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The TCK test [dependentLRA|https://github.com/eclipse/microprofile-lra/blob/master/tck/src/main/java/org/eclipse/microprofile/lra/tck/TckTests.java#L461] in the microprofile-lra test suite fails if the [terminal attribute of the LRA annotation|https://github.com/eclipse/microprofile-lra/blob/master/api/src/main/java/org/eclipse/microprofile/lra/annotation/LRA.java#L176] is set to true. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:02 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3073) Do not mandate JAX-RS annotations on @Compensate/@Complete methods In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3073: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Do not mandate JAX-RS annotations on @Compensate/@Complete methods > ------------------------------------------------------------------ > > Key: JBTM-3073 > URL: https://issues.jboss.org/browse/JBTM-3073 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Cloned from [https://github.com/eclipse/microprofile-lra/issues/35|http://example.com]: > It is up to the implementation on how the Compensate methods are called. > This could be through JAX-RS calls but this should not be the only way (although an implementation will probably only implement one method). This makes it easier to use the 'events' way of coordination. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:02 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3072) Add a test to verify the behaviour of LRA.Type.REQUIRES_NEW combined with LRA.delayClose In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3072: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > 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 > Priority: Major > 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) From issues at jboss.org Fri Dec 14 07:36:03 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3071) Windows automation of the LRA examples quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3071: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Windows automation of the LRA examples quickstarts > -------------------------------------------------- > > Key: JBTM-3071 > URL: https://issues.jboss.org/browse/JBTM-3071 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The LRA examples quickstarts (https://issues.jboss.org/browse/JBTM-3063) contain a bash script to run the examples. We need the equivalent for running on Windows. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:03 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3065) Check that starting LRA's via CDI and API in the same method works In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3065: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Check that starting LRA's via CDI and API in the same method works > ------------------------------------------------------------------ > > Key: JBTM-3065 > URL: https://issues.jboss.org/browse/JBTM-3065 > 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 > > > The LRA spec supports starting LRA's via a Java API or via Java annotations. If the two approaches are used together in the same resource method then the LRA started via the API should be nested inside the one started by an annotation. > If the annotated class also contains @Compensate and @Complete annotations (which means that the resource should join the outer LRA) and the resource method Joins the nested LRA then the resource should receive callbacks for both the outer and nested LRA's. > The following code shows an example: > {code} > @PUT > @LRA(LRA.Type.REQUIRES_NEW) // starts a new LRA on entry > public String doInTransaction() { > URL lraId = lraClient.startLRA(...); // starts a nested LRA > lraClient.join(...) // join the nested LRA > lraClient.closeLRA(lraId); // close the nested LRA > // assert that the nested callbacks were invoked > // assert that the callbacks for the outer LRA have not been called yet > } > {code} > Similar comments apply if the resource joins via the LRAManagement API: > {code} > @Inject > private LRAManagement lraManagement; > public String doInTransaction() { > lraManagement.joinLRA(this, lraId, 0L, TimeUnit.SECONDS); > // etc > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:03 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3062) Include a test for LRA context propagation across a "non-LRA aware" service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3062: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Include a test for LRA context propagation across a "non-LRA aware" service > --------------------------------------------------------------------------- > > Key: JBTM-3062 > URL: https://issues.jboss.org/browse/JBTM-3062 > 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 > > > If a microservice A that wants to participate in an LRA and calls microservice B (which does not have specific LRA behaviour) and service A in turn calls microservice C (which does have specific LRA behaviour), then B should not need to be annotated with @LRA. A test is needed for this behaviour. > This issue relates to https://github.com/eclipse/microprofile-lra/issues/7 -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:03 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3058) Add STM tests that verify nested transactions are closed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3058: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Add STM tests that verify nested transactions are closed > -------------------------------------------------------- > > Key: JBTM-3058 > URL: https://issues.jboss.org/browse/JBTM-3058 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM, Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > STM implements "Closed Nested Transactions" as opposed to Flattened or Open. We need a test which demonstrates that nested transactions follow the closed model. > Furthermore, STM implementations can differ in how transactional code and non-transactional code are isolated from each other (with respect to visibility of updates during a transaction). Add a test that verifies that we use the "Weak Isolation" model. > Details of the expected behaviour is covered in the Sept 2018 jbossts blog entitled "[Tips on how to evaluate STM implementations|http://example.com|https://jbossts.blogspot.com/2018/09/tips-on-how-to-evaluate-stm.html]" -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:03 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3051) LRA test timeLimitRequiredLRA failure on JDK 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3051: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > 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) From issues at jboss.org Fri Dec 14 07:36:03 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3046) REST-AT PerformanceTest occasionally hangs on Windows CI runs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3046: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > REST-AT PerformanceTest occasionally hangs on Windows CI runs > ------------------------------------------------------------- > > Key: JBTM-3046 > URL: https://issues.jboss.org/browse/JBTM-3046 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > Attachments: threaddump.txt > > > The test runs from the rts/at/tx/pom.xml module (org.jboss.narayana.rts:restat). The hanging thread seems to be a coordinator request to start an inVM REST-AT transaction. The coordinator is running in an Undertow container and the failing test is org.jboss.jbossts.star.test.PerformanceTest > See the attachment for the stacktraces. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:03 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3042) API to get detailed LRA information should not include stats type data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3042: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > API to get detailed LRA information should not include stats type data > ---------------------------------------------------------------------- > > Key: JBTM-3042 > URL: https://issues.jboss.org/browse/JBTM-3042 > 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 > > > The interface to obtain information about an LRA [1] includes data such as when the LRA was started and ended. This type of information is more appropriate to monitoring and statistics gathering rather than core LRA info. Not all implementations may want to / be able to report these accurately so perhaps move them to an extended optional interface > [1] https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-client/src/main/java/io/narayana/lra/client/LRAInfoImpl.java#L90 -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:04 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3020) Add ability for resources to indicate XA_RDONLY on end In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3020: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Add ability for resources to indicate XA_RDONLY on end > ------------------------------------------------------ > > Key: JBTM-3020 > URL: https://issues.jboss.org/browse/JBTM-3020 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: David Lloyd > Assignee: Ondra Chaloupka > Priority: Major > Fix For: 5.next > > > As discussed in WFLY-10258 and https://developer.jboss.org/message/982097, this request is to add the ability for an XAResource to indicate (on end) that it has no committable work, which would act as a hint to order that XAResource at an earlier point of prepare processing, which will in turn increase the chances of a 1PC optimization occurring. > As expressed in the forum thread, the mechanism should not interfere with compatibility. One possible way to do this would be to introduce an enhanced subinterface of XAResource which includes a method like this: > {code:java} > int endWithResult(Xid xid, int flags) throws XAException; > {code} > The method behaves semantically identically to {{XAResource#end}} , except it would be allowed to return {{XA_RDONLY}} or {{XA_OK}}. A value of {{XA_RDONLY}} would indicate that the resource expects to return {{XA_RDONLY}} in response to a {{prepare}} call, whereas a value of {{XA_OK}} indicates that the resource's future {{prepare}} result cannot yet be decided or will be {{XA_OK}}. An invalid result should probably behave equivalently to an {{XAException}} being thrown by the {{end}} method. {{XAER_RMERR}} seems like a reasonable error code for this case. An alternative strategy would be to treat an invalid return value as being equivalent to {{XA_OK}}. > Since it's a subinterface of {{XAResource}}, it could also define the following default method: > {code:java} > default void end(Xid xid, int flags) throws XAException { > endWithResult(xid, flags); > } > {code} > This method would not need to be called by the TM, but would correctly satisfy the {{XAResource}} contract without requiring the user to implement the redundant method. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:04 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3019) Testsuite: Docker controller leaves stray volumes and fills up disk space unnecessairly over time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-3019: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Testsuite: Docker controller leaves stray volumes and fills up disk space unnecessairly over time > ------------------------------------------------------------------------------------------------- > > Key: JBTM-3019 > URL: https://issues.jboss.org/browse/JBTM-3019 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.8.1.Final > Environment: Docker enabled Jenkins slaves > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > Priority: Minor > Fix For: 5.next > > > h3. Problem > The Docker controller that allocates databases as Docker containers cleans up containers and does not leave unnecessary images: > {code} > [root at karm-centos7-x86-64 ~]# docker images > REPOSITORY TAG IMAGE ID CREATED SIZE > docker.io/postgres 9.4 26bd9b04b948 6 days ago 232 MB > docker.io/postgres 10 0965cdc98045 6 days ago 234 MB > docker.io/postgres ed5db6e669ff 7 weeks ago 263 MB > docker.io/postgres 30121e967865 7 weeks ago 289 MB > [root at karm-centos7-x86-64 ~]# docker ps -a > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > [root at karm-centos7-x86-64 ~]# > {code} > Although it leaves stray container volumes for some reason: > {code} > [root at karm-centos7-x86-64 ~]# du -hs /var/lib/docker-latest/volumes > 15G /var/lib/docker-latest/volumes > [root at karm-centos7-x86-64 ~]# docker volume ls -qf dangling=true | wc -l > 409 > {code} > It unnecessarily clogs the slaves' disk space. The 15G of garbage has been created over dozens and dozens of builds with at least two containers each, but it shouldn't be happening anyway. > h3. Call to action > Review whether [removeContainerCmd|https://github.com/jbosstm/narayana/blob/master/tools/src/main/java/io/narayana/db/PostgreContainerAllocator.java#L264] is supposed to be enough to not only remove the container but to also remove its volume. > h3. Workaround > {code} > docker volume prune > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:04 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2968) Some JTS quickstarts run with JacORB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2968: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Some JTS quickstarts run with JacORB > ------------------------------------ > > Key: JBTM-2968 > URL: https://issues.jboss.org/browse/JBTM-2968 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Some of the JTS quickstarts are using JacORB. The narayana project has since changed the default ORB (OpenJDK ORB) so we should change the quickstarts to use the new default. The affected poms are: > ArjunaJTS/pom.xml > ArjunaJTS/standalone/pom.xml > ArjunaJTS/trailmap/pom.xml -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:36:04 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:36:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2967) Some quickstarts are not tested in CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2967: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Some quickstarts are not tested in CI > ------------------------------------- > > Key: JBTM-2967 > URL: https://issues.jboss.org/browse/JBTM-2967 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Most quickstarts used to ship with a run.[sh|bat] script for running the quickstart and we used to test them in CI by executing the run script. At some point we changed the CI script (scripts/hudson/quickstart.sh) to just run the pom instead (./build.sh -B clean install). Since not all poms execute their run script we aren't getting full CI coverage. > This JIRA is to go through each quickstart and ensure the the pom does indeed exercise the quickstart. > The following poms do execute a run script > transactionaldriver-jpa-and-tomcat/pom.xml > rts/at/simple/pom.xml > rts/lra/lra-test/pom.xml > ArjunaJTS/interop/glassfish/pom.xml > transactionaldriver-and-tomcat/pom.xml > spring/camel-with-narayana-spring-boot/pom.xml > The following quickstarts contain run scripts: > transactionaldriver-jpa-and-tomcat/run.sh > ArjunaCore/txoj/run.sh > jboss-as/build/target/wildfly-9.0.0.CR1-SNAPSHOT/bin/run.sh > ArjunaJTA/object_store/run.sh > ArjunaJTA/maven/run.sh > ArjunaJTA/recovery/run.sh > ArjunaJTA/javax_transaction/run.sh > rts/at/undertow/run.sh > rts/at/recovery/recovery2/run.sh > rts/at/recovery/recovery1/run.sh > rts/at/simple/run.sh > rts/at/service/service2b/run.sh > rts/at/service/service2/run.sh > rts/at/service/service1b/run.sh > rts/at/service/service1/run.sh > rts/at/demo/run.sh > rts/lra/run.sh > ArjunaJTS/standalone/run.sh > ArjunaJTS/interop/glassfish/run.sh > ArjunaJTS/recovery/run.sh -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 07:37:00 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2912) Upgrade JMS transactional driver to JMS 2.0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Fri Dec 14 07:37:00 2018 From: issues at jboss.org (Ondra Chaloupka (Jira)) Date: Fri, 14 Dec 2018 07:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2867) Investigate un-_workList protected access to _work object In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2867: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Investigate un-_workList protected access to _work object > --------------------------------------------------------- > > Key: JBTM-2867 > URL: https://issues.jboss.org/browse/JBTM-2867 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Major > Fix For: 5.next > > > During investigation of JBTM-2865 it was detected that the _work object can be accessed outside of the _workList synchronized block. Notably this seems to be a .remove() operation on it which can mutate the struct and may cause issues. > For example, this looks wrong: > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef20978dc5d30ac5c2/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/CacheStore.java#L703 > If > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef20978dc5d30ac5c2/ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/CacheStore.java#L187 -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Dec 14 08:21:00 2018 From: issues at jboss.org (Vadim Lotarev (Jira)) Date: Fri, 14 Dec 2018 08:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3088) NPE in Recovery Manager In-Reply-To: References: Message-ID: 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) From issues at jboss.org Fri Dec 14 09:11:00 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Fri, 14 Dec 2018 09:11:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3088) NPE in Recovery Manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674843#comment-13674843 ] 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[published]~objecttype~objecttype[thread] 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) From issues at jboss.org Fri Dec 14 09:11:00 2018 From: issues at jboss.org (Tom Jenkinson (Jira)) Date: Fri, 14 Dec 2018 09:11:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3088) NPE in Recovery Manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Wed Dec 19 09:35:01 2018 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Wed, 19 Dec 2018 09:35:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3089) LRA code improvements In-Reply-To: References: Message-ID: 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) From issues at jboss.org Wed Dec 19 10:03:04 2018 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Wed, 19 Dec 2018 10:03:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2942) LRA tests failed when building with the JDK9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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-crash-with-java-9 > 2. https://stackoverflow.com/questions/42990017/illegalargumentexception-while-starting-wildfly-swarm-provided-custom-main-meth -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Dec 19 10:03:07 2018 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Wed, 19 Dec 2018 10:03:07 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3051) LRA test timeLimitRequiredLRA failure on JDK 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676405#comment-13676405 ] 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) From issues at jboss.org Wed Dec 19 10:04:00 2018 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Wed, 19 Dec 2018 10:04:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3051) LRA test timeLimit failure on JDK 9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) From issues at jboss.org Thu Dec 20 13:52:00 2018 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Thu, 20 Dec 2018 13:52:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3090) LRA TCK failures need to report more context to facilitate debugging In-Reply-To: References: Message-ID: 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) From issues at jboss.org Thu Dec 20 13:53:00 2018 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Thu, 20 Dec 2018 13:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3089) LRA code improvements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676881#comment-13676881 ] 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)