From issues at jboss.org Sun Feb 4 22:00:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Sun, 4 Feb 2018 22:00:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2989) Replace to use the DBCP2 in the spring quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Amos Feng created pull request #220 in GitHub --------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Replace to use the DBCP2 in the spring quickstarts > -------------------------------------------------- > > Key: JBTM-2989 > URL: https://issues.jboss.org/browse/JBTM-2989 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > It could be helpful to replace the transational driver when using with the spring. The transactional driver might be only used in the standalone. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 5 10:15:00 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 5 Feb 2018 10:15:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2988) Update activemq-artemis in the performance repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #43 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Update activemq-artemis in the performance repo > ----------------------------------------------- > > Key: JBTM-2988 > URL: https://issues.jboss.org/browse/JBTM-2988 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > Make sure that the artemis dependency in the performance repo matches what we use on master. So we are currently on 1.5.5.jbossorg-008 so change in the pom in our performance repo to use this version. > Important: make sure that we also *replace* the native AIO library which is located in ArjunaJTA/jta/etc -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 5 16:46:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 5 Feb 2018 16:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2986) Cannot build LRA on IBM JDK 8:lra-test: An Ant BuildException has occurred, looking for non-existing bin/jps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1275 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Cannot build LRA on IBM JDK 8:lra-test: An Ant BuildException has occurred, looking for non-existing bin/jps > ------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2986 > URL: https://issues.jboss.org/browse/JBTM-2986 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.2.Final > Environment: IBM JDK 8 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > Fix For: 5.7.2.Final > > Attachments: maven.log.zip > > > I would like to build and test Narayana on IBM JDK and it seems the LRA test module is looking for {{jps}} that doesn't exist on IBM JDK. There should be some profile/wrapper to skip or port this part so as it works on IBM JDK without an explicit path to bin/jps. > See [^maven.log.zip]. > h3. Excerpt > {noformat} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (stop) > on project lra-test: An Ant BuildException has occured: Execute failed: > java.io.IOException: Cannot run program "/qa/tools/opt/x86_64/ibm-java-80/bin/jps" > (in directory "/opt/workspace/workspace/jws5-narayana-smoke-linux/cb703450/rts/lra/lra-test"): > error=2, No such file or directory > [ERROR] around Ant part ...... > @ 4:63 in /opt/workspace/workspace/jws5-narayana-smoke-linux/cb703450/rts/lra/lra-test/target/antrun/build-main.xml > {noformat} > I tried to "workaround" it temporarily with {{-DskipTests -Dmaven.test.skip=true}}; no luck. > WDYT? -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 5 17:55:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 5 Feb 2018 17:55:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2928) Provide WS-AT Integration with .NET In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1276 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Provide WS-AT Integration with .NET > ----------------------------------- > > Key: JBTM-2928 > URL: https://issues.jboss.org/browse/JBTM-2928 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: J?rg B?sner > > Provide WS-AT integration for .NET -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 6 09:52:00 2018 From: issues at jboss.org (Jonathan Halliday (JIRA)) Date: Tue, 6 Feb 2018 09:52:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2990) ThreadUtil performance improvement In-Reply-To: References: Message-ID: Jonathan Halliday created JBTM-2990: --------------------------------------- Summary: ThreadUtil performance improvement Key: JBTM-2990 URL: https://issues.jboss.org/browse/JBTM-2990 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Transaction Core Affects Versions: 5.7.2.Final Reporter: Jonathan Halliday Assignee: Jonathan Halliday Priority: Minor The ThreadUtil changes introduced for the bug fix under JBTM-2673, cause lock contention on the static WeakHashMap under high load. The proposed fix is to partially reintroduce the earlier behavior of caching the value in a ThreadLocal, since the dominant use case is pooled threads repeatedly looking up their own identity. The global lookup capability introduced for the fix remains necessary for less common use cases, but the locking can be taken off the critical path for most workloads. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 6 10:08:00 2018 From: issues at jboss.org (Anonymous (JIRA)) Date: Tue, 6 Feb 2018 10:08:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2990) ThreadUtil performance improvement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when jhalliday created pull request #1277 in GitHub ---------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > ThreadUtil performance improvement > ---------------------------------- > > Key: JBTM-2990 > URL: https://issues.jboss.org/browse/JBTM-2990 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.7.2.Final > Reporter: Jonathan Halliday > Assignee: Jonathan Halliday > Priority: Minor > > The ThreadUtil changes introduced for the bug fix under JBTM-2673, cause lock contention on the static WeakHashMap under high load. > The proposed fix is to partially reintroduce the earlier behavior of caching the value in a ThreadLocal, since the dominant use case is pooled threads repeatedly looking up their own identity. The global lookup capability introduced for the fix remains necessary for less common use cases, but the locking can be taken off the critical path for most workloads. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Feb 7 07:02:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 7 Feb 2018 07:02:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2987) Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529894#comment-13529894 ] Tom Jenkinson commented on JBTM-2987: ------------------------------------- [~alon3392] - just checking that you are primIl on github? > Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager > -------------------------------------------------------------------------------------- > > Key: JBTM-2987 > URL: https://issues.jboss.org/browse/JBTM-2987 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Affects Versions: 5.7.2.Final > Reporter: Alon Greenland > > As discussed in https://developer.jboss.org/thread/266729, when Recovery Manager executes xaResource.rollback(xid), if it receives error code XAER_NOTA it is not really an error or warning. > Currently it is logged as warning. It can be logged with debug level instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Sun Feb 11 23:12:00 2018 From: issues at jboss.org (Alon Greenland (JIRA)) Date: Sun, 11 Feb 2018 23:12:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2987) Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531435#comment-13531435 ] Alon Greenland commented on JBTM-2987: -------------------------------------- yes > Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager > -------------------------------------------------------------------------------------- > > Key: JBTM-2987 > URL: https://issues.jboss.org/browse/JBTM-2987 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Affects Versions: 5.7.2.Final > Reporter: Alon Greenland > > As discussed in https://developer.jboss.org/thread/266729, when Recovery Manager executes xaResource.rollback(xid), if it receives error code XAER_NOTA it is not really an error or warning. > Currently it is logged as warning. It can be logged with debug level instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 12 03:22:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 12 Feb 2018 03:22:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2986) Cannot build LRA on IBM JDK 8:lra-test: An Ant BuildException has occurred, looking for non-existing bin/jps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2986: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Cannot build LRA on IBM JDK 8:lra-test: An Ant BuildException has occurred, looking for non-existing bin/jps > ------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2986 > URL: https://issues.jboss.org/browse/JBTM-2986 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.2.Final > Environment: IBM JDK 8 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > Fix For: 5.7.2.Final > > Attachments: maven.log.zip > > > I would like to build and test Narayana on IBM JDK and it seems the LRA test module is looking for {{jps}} that doesn't exist on IBM JDK. There should be some profile/wrapper to skip or port this part so as it works on IBM JDK without an explicit path to bin/jps. > See [^maven.log.zip]. > h3. Excerpt > {noformat} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.8:run (stop) > on project lra-test: An Ant BuildException has occured: Execute failed: > java.io.IOException: Cannot run program "/qa/tools/opt/x86_64/ibm-java-80/bin/jps" > (in directory "/opt/workspace/workspace/jws5-narayana-smoke-linux/cb703450/rts/lra/lra-test"): > error=2, No such file or directory > [ERROR] around Ant part ...... > @ 4:63 in /opt/workspace/workspace/jws5-narayana-smoke-linux/cb703450/rts/lra/lra-test/target/antrun/build-main.xml > {noformat} > I tried to "workaround" it temporarily with {{-DskipTests -Dmaven.test.skip=true}}; no luck. > WDYT? -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 12 12:22:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Feb 2018 12:22:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2991) Deprecate old StartXAResource interface - it is in SPI now In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2991: ----------------------------------- Summary: Deprecate old StartXAResource interface - it is in SPI now Key: JBTM-2991 URL: https://issues.jboss.org/browse/JBTM-2991 Project: JBoss Transaction Manager Issue Type: Bug Components: Transaction Core Reporter: Tom Jenkinson -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 12 12:22:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Feb 2018 12:22:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2991) Deprecate old StartXAResource interface - it is in SPI now In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2991: -------------------------------- Issue Type: Task (was: Bug) > Deprecate old StartXAResource interface - it is in SPI now > ---------------------------------------------------------- > > Key: JBTM-2991 > URL: https://issues.jboss.org/browse/JBTM-2991 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 12 12:23:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Feb 2018 12:23:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2991) Deprecate old StartXAResource interface - it is in SPI now In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2991: -------------------------------- Description: All support for this was moved to org.jboss.tm.FirstResource in the SPI > Deprecate old StartXAResource interface - it is in SPI now > ---------------------------------------------------------- > > Key: JBTM-2991 > URL: https://issues.jboss.org/browse/JBTM-2991 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > > All support for this was moved to org.jboss.tm.FirstResource in the SPI -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 12 12:23:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Feb 2018 12:23:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2991) Deprecate old StartXAResource interface In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2991: -------------------------------- Summary: Deprecate old StartXAResource interface (was: Deprecate old StartXAResource interface - it is in SPI now) > Deprecate old StartXAResource interface > --------------------------------------- > > Key: JBTM-2991 > URL: https://issues.jboss.org/browse/JBTM-2991 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > > All support for this was moved to org.jboss.tm.FirstResource in the SPI -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 12 12:25:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 12 Feb 2018 12:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2991) Deprecate old StartXAResource interface In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #1279 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Deprecate old StartXAResource interface > --------------------------------------- > > Key: JBTM-2991 > URL: https://issues.jboss.org/browse/JBTM-2991 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > > All support for this was moved to org.jboss.tm.FirstResource in the SPI -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 13 11:33:00 2018 From: issues at jboss.org (Michal Karm Babacek (JIRA)) Date: Tue, 13 Feb 2018 11:33:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar In-Reply-To: References: Message-ID: Michal Karm Babacek created JBTM-2992: ----------------------------------------- Summary: Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar Key: JBTM-2992 URL: https://issues.jboss.org/browse/JBTM-2992 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Affects Versions: 5.7.2.Final Environment: Java 9 Reporter: Michal Karm Babacek Assignee: Ondra Chaloupka Priority: Critical {code} [ERROR] Failed to execute goal on project tomcat-jta: Could not resolve dependencies for project org.jboss.narayana.tomcat:tomcat-jta:jar:5.7.2.Final-SNAPSHOT: Could not find artifact com.sun:tools:jar:1.6 at specified path /file-not-found/tools.jar -> [Help 1] [ERROR] {code} See: StackOverflow and [~ogondza]'s comments -> [link|https://stackoverflow.com/questions/35240134/declare-maven-dependency-on-tools-jar-to-work-on-jdk-9#35244168] -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 13 11:50:00 2018 From: issues at jboss.org (Michal Karm Babacek (JIRA)) Date: Tue, 13 Feb 2018 11:50:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2993) start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds In-Reply-To: References: Message-ID: Michal Karm Babacek created JBTM-2993: ----------------------------------------- Summary: start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds Key: JBTM-2993 URL: https://issues.jboss.org/browse/JBTM-2993 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 5.next Reporter: Michal Karm Babacek Assignee: Ondra Chaloupka I had updated to the latest Narayana master and it broke the build for me on "LRA": See: [log|https://gist.github.com/Karm/2eae842cff57964af65a3341dfae873c] My git head: 40999b11 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 13 11:55:00 2018 From: issues at jboss.org (Michal Karm Babacek (JIRA)) Date: Tue, 13 Feb 2018 11:55:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2993) start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Karm Babacek updated JBTM-2993: -------------------------------------- Workaround Description: {code}sed -i 's/lra-test<\/module>/<\!--lra-test<\/module>-->/g' ./rts/lra/pom.xml{code} Environment: Fedora 26, OpenJDK 8, Maven 3.5.2 > start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds > ------------------------------------------------------------------------------------ > > Key: JBTM-2993 > URL: https://issues.jboss.org/browse/JBTM-2993 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.next > Environment: Fedora 26, OpenJDK 8, Maven 3.5.2 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > > I had updated to the latest Narayana master and it broke the build for me on "LRA": See: [log|https://gist.github.com/Karm/2eae842cff57964af65a3341dfae873c] > My git head: 40999b11 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Feb 14 02:47:00 2018 From: issues at jboss.org (Oliver Gondza (JIRA)) Date: Wed, 14 Feb 2018 02:47:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532818#comment-13532818 ] Oliver Gondza commented on JBTM-2992: ------------------------------------- Have a look at https://github.com/olivergondza/maven-jdk-tools-wrapper, it attempts to shield users from some of that madness. > Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar > ------------------------------------------------------------------------------ > > Key: JBTM-2992 > URL: https://issues.jboss.org/browse/JBTM-2992 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.7.2.Final > Environment: Java 9 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > Priority: Critical > > {code} > [ERROR] Failed to execute goal on project tomcat-jta: > Could not resolve dependencies for project > org.jboss.narayana.tomcat:tomcat-jta:jar:5.7.2.Final-SNAPSHOT: > Could not find artifact > com.sun:tools:jar:1.6 at specified path /file-not-found/tools.jar -> [Help 1] > [ERROR] > {code} > See: StackOverflow and [~ogondza]'s comments -> [link|https://stackoverflow.com/questions/35240134/declare-maven-dependency-on-tools-jar-to-work-on-jdk-9#35244168] -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Feb 14 04:46:01 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 14 Feb 2018 04:46:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2992: ----------------------------------- Assignee: Amos Feng (was: Ondra Chaloupka) > Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar > ------------------------------------------------------------------------------ > > Key: JBTM-2992 > URL: https://issues.jboss.org/browse/JBTM-2992 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.7.2.Final > Environment: Java 9 > Reporter: Michal Karm Babacek > Assignee: Amos Feng > Priority: Critical > > {code} > [ERROR] Failed to execute goal on project tomcat-jta: > Could not resolve dependencies for project > org.jboss.narayana.tomcat:tomcat-jta:jar:5.7.2.Final-SNAPSHOT: > Could not find artifact > com.sun:tools:jar:1.6 at specified path /file-not-found/tools.jar -> [Help 1] > [ERROR] > {code} > See: StackOverflow and [~ogondza]'s comments -> [link|https://stackoverflow.com/questions/35240134/declare-maven-dependency-on-tools-jar-to-work-on-jdk-9#35244168] -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Feb 14 05:21:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 14 Feb 2018 05:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2993) start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532967#comment-13532967 ] Ondra Chaloupka commented on JBTM-2993: --------------------------------------- I tried to switch to maven 3.5.2 (otherwise I use the same environmental setup Fedora 26, OpenJDK8) and it passes on my machine. The Narayana CI seems the same. It could be easily the startup timeout is too small. I haven't recognized the default value is 30 seconds and when checking my laptop the startup time seems to be 21 seconds which is quite near to each other. [~mbabacek]: could you please verify * is there log `lra/lra-test/target/failsafe-reports/lra-coordinator-swarm-startup.log` with some content after the failure? * would be be so kind and change the default timeout on your machine and test with such change? `sed 's||120|' -i lra-test/pom.xml` > start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds > ------------------------------------------------------------------------------------ > > Key: JBTM-2993 > URL: https://issues.jboss.org/browse/JBTM-2993 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.next > Environment: Fedora 26, OpenJDK 8, Maven 3.5.2 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > > I had updated to the latest Narayana master and it broke the build for me on "LRA": See: [log|https://gist.github.com/Karm/2eae842cff57964af65a3341dfae873c] > My git head: 40999b11 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Feb 14 05:21:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 14 Feb 2018 05:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2993) start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532967#comment-13532967 ] Ondra Chaloupka edited comment on JBTM-2993 at 2/14/18 5:20 AM: ---------------------------------------------------------------- I tried to switch to maven 3.5.2 (otherwise I use the same environmental setup Fedora 26, OpenJDK8) and it passes on my machine. The Narayana CI seems the same. It could be easily the startup timeout is too small. I haven't recognized the default value is 30 seconds and when checking my laptop the startup time seems to be 21 seconds which is quite near to each other. [~mbabacek]: could you please verify * is there log {{lra/lra-test/target/failsafe-reports/lra-coordinator-swarm-startup.log}} with some content after the failure? * would be be so kind and change the default timeout on your machine and test with such change? {{sed 's||120|' -i lra-test/pom.xml}} was (Author: ochaloup): I tried to switch to maven 3.5.2 (otherwise I use the same environmental setup Fedora 26, OpenJDK8) and it passes on my machine. The Narayana CI seems the same. It could be easily the startup timeout is too small. I haven't recognized the default value is 30 seconds and when checking my laptop the startup time seems to be 21 seconds which is quite near to each other. [~mbabacek]: could you please verify * is there log `lra/lra-test/target/failsafe-reports/lra-coordinator-swarm-startup.log` with some content after the failure? * would be be so kind and change the default timeout on your machine and test with such change? `sed 's||120|' -i lra-test/pom.xml` > start-swarm-lra-coordinator : failed: Process was not healthy even after 30 seconds > ------------------------------------------------------------------------------------ > > Key: JBTM-2993 > URL: https://issues.jboss.org/browse/JBTM-2993 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.next > Environment: Fedora 26, OpenJDK 8, Maven 3.5.2 > Reporter: Michal Karm Babacek > Assignee: Ondra Chaloupka > > I had updated to the latest Narayana master and it broke the build for me on "LRA": See: [log|https://gist.github.com/Karm/2eae842cff57964af65a3341dfae873c] > My git head: 40999b11 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Sat Feb 17 02:23:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Sat, 17 Feb 2018 02:23:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2969) Make the CDI checker a standalone tool or/and mvn plugin In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1283 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Make the CDI checker a standalone tool or/and mvn plugin > -------------------------------------------------------- > > Key: JBTM-2969 > URL: https://issues.jboss.org/browse/JBTM-2969 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > The way how the checker works now (as CDI extension, needed to be packed inside of the app) is not a good approach and it should work as a standalone tool or better as a maven plugin to verify the annotation in a defined phase. > The current approach needs to be reworked. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Sun Feb 18 18:44:00 2018 From: issues at jboss.org (Stuart Douglas (JIRA)) Date: Sun, 18 Feb 2018 18:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2994) TransactionExtension uses old version of addAnnotatedType which results in warnings being logged In-Reply-To: References: Message-ID: Stuart Douglas created JBTM-2994: ------------------------------------ Summary: TransactionExtension uses old version of addAnnotatedType which results in warnings being logged Key: JBTM-2994 URL: https://issues.jboss.org/browse/JBTM-2994 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Stuart Douglas 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory is deprecated from CDI 1.1! 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNever is deprecated from CDI 1.1! 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNotSupported is deprecated from CDI 1.1! 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired is deprecated from CDI 1.1! 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew is deprecated from CDI 1.1! 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1! -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Sun Feb 18 18:47:00 2018 From: issues at jboss.org (Stuart Douglas (JIRA)) Date: Sun, 18 Feb 2018 18:47:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2994) TransactionExtension uses old version of addAnnotatedType which results in warnings being logged In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Stuart Douglas created pull request #1284 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > TransactionExtension uses old version of addAnnotatedType which results in warnings being logged > ------------------------------------------------------------------------------------------------ > > Key: JBTM-2994 > URL: https://issues.jboss.org/browse/JBTM-2994 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Stuart Douglas > > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNever is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNotSupported is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1! -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 19 10:40:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 19 Feb 2018 10:40:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2994) TransactionExtension uses old version of addAnnotatedType which results in warnings being logged In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2994: -------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Stuart Douglas Resolution: Done > TransactionExtension uses old version of addAnnotatedType which results in warnings being logged > ------------------------------------------------------------------------------------------------ > > Key: JBTM-2994 > URL: https://issues.jboss.org/browse/JBTM-2994 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNever is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNotSupported is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1! -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 20 06:34:00 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 20 Feb 2018 06:34:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2995: -------------------------------------- Summary: RTS InboundBridgeRecoveryTestCase hanging Key: JBTM-2995 URL: https://issues.jboss.org/browse/JBTM-2995 Project: JBoss Transaction Manager Issue Type: Bug Components: REST Affects Versions: 5.7.2.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Critical Fix For: 5.next The following test is hanging: org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l ocal: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) at java.lang.Thread.run(Thread.java:748) Caused by: com.arjuna.ats.arjuna.exceptions.FatalError at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager .getPOA(ORBManager.java:97) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) at java.lang.Thread.run(Thread.java:748) Caused by: com.arjuna.ats.arjuna.exceptions.FatalError at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 20 06:38:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 20 Feb 2018 06:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535642#comment-13535642 ] Tom Jenkinson commented on JBTM-2995: ------------------------------------- I didn't even realise that we supported RTS with JTS? > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 20 07:02:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 20 Feb 2018 07:02:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2996) Change the Narayan CI to use GitHub webhooks instead of a poller job In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-2996: ------------------------------------- Summary: Change the Narayan CI to use GitHub webhooks instead of a poller job Key: JBTM-2996 URL: https://issues.jboss.org/browse/JBTM-2996 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Build System Affects Versions: 5.7.2.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Priority: Minor It would be good to start using gihub webhooks instead of a poller jenkins cron job. Configure the triggers in Jenkins and webhook on github and consider using the plugin https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Feb 21 07:21:00 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 21 Feb 2018 07:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2995: ----------------------------------- Priority: Major (was: Critical) > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Feb 21 07:23:00 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 21 Feb 2018 07:23:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536333#comment-13536333 ] Michael Musgrove commented on JBTM-2995: ---------------------------------------- I have reduced the priority since the CI failure has not recurred (there have 3 successful builds since the hang was seen). > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 04:49:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 23 Feb 2018 04:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2996) Change the Narayan CI to use GitHub webhooks instead of a poller job In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537352#comment-13537352 ] Tom Jenkinson commented on JBTM-2996: ------------------------------------- I like it! I would be tempted to add a comment_on_pull method (copy it from one of the scripts or the narayana.io job: http://narayanaci1.eng.hst.ams2.redhat.com/view/Pulls/job/btny-pulls-narayanaio/configure) to report that we need a committer to approve the comment rather than just exit 0 - at least for now until we remember to do that. > Change the Narayan CI to use GitHub webhooks instead of a poller job > -------------------------------------------------------------------- > > Key: JBTM-2996 > URL: https://issues.jboss.org/browse/JBTM-2996 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Affects Versions: 5.7.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > It would be good to start using gihub webhooks instead of a poller jenkins cron job. > Configure the triggers in Jenkins and webhook on github and consider using the plugin > https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 05:01:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 05:01:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2996) Change the Narayana CI jobs to consider membership of PR author In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2996: ---------------------------------- Summary: Change the Narayana CI jobs to consider membership of PR author (was: Change the Narayan CI to use GitHub webhooks instead of a poller job) > Change the Narayana CI jobs to consider membership of PR author > --------------------------------------------------------------- > > Key: JBTM-2996 > URL: https://issues.jboss.org/browse/JBTM-2996 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Affects Versions: 5.7.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > It would be good to start using gihub webhooks instead of a poller jenkins cron job. > Configure the triggers in Jenkins and webhook on github and consider using the plugin > https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 05:05:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 05:05:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2996) Change the Narayana CI jobs to consider membership of PR author In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537405#comment-13537405 ] Ondra Chaloupka commented on JBTM-2996: --------------------------------------- [~tomjenkinson] ok, thanks. just I'm thinking one point, do you think it's ok to have the function copied over {{*-poller}} jobs or should there be some common shell script file (?) which would be sourced and used? _note: I changed the title of the issue to follow the change which was done._ > Change the Narayana CI jobs to consider membership of PR author > --------------------------------------------------------------- > > Key: JBTM-2996 > URL: https://issues.jboss.org/browse/JBTM-2996 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Affects Versions: 5.7.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > It would be good to start using gihub webhooks instead of a poller jenkins cron job. > Configure the triggers in Jenkins and webhook on github and consider using the plugin > https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 05:40:00 2018 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 23 Feb 2018 05:40:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2996) Change the Narayana CI jobs to consider membership of PR author In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537426#comment-13537426 ] Tom Jenkinson commented on JBTM-2996: ------------------------------------- I would suggest to copy and paste for now. We have a lot of places of copy/paste (comment_on_pull itself being a good example). It would be nice to modularise the whole thing but I don't think now is the time. > Change the Narayana CI jobs to consider membership of PR author > --------------------------------------------------------------- > > Key: JBTM-2996 > URL: https://issues.jboss.org/browse/JBTM-2996 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Affects Versions: 5.7.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > It would be good to start using gihub webhooks instead of a poller jenkins cron job. > Configure the triggers in Jenkins and webhook on github and consider using the plugin > https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 06:37:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 06:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2996) Change the Narayana CI jobs to consider membership of PR author In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537462#comment-13537462 ] Ondra Chaloupka commented on JBTM-2996: --------------------------------------- I distributed the change to all _pulls_ `-poller` jobs. I ended up with the following ```bash export GIT_ACCOUNT=jbosstm export GIT_REPO=narayana export COMMENT_ON_PULL=1 function comment_on_pull { if [ "$COMMENT_ON_PULL" = "" ]; then return; fi PULL_NUMBER=$(echo $GIT_BRANCH | awk -F 'pull' '{ print $2 }' | awk -F '/' '{ print $2 }') if [ "$PULL_NUMBER" != "" ] then JSON="{ \"body\": \"$1\" }" curl -d "$JSON" -ujbosstm-bot:$BOT_PASSWORD https://api.github.com/repos/$GIT_ACCOUNT/$GIT_REPO/issues/$PULL_NUMBER/comments else echo "Not a pull request, so not commenting" fi } PULL_NUMBER=$(echo $GIT_BRANCH | awk -F 'pull' '{ print $2 }' | awk -F '/' '{ print $2 }') PULL_DESCRIPTION=$(curl -ujbosstm-bot:$BOT_PASSWORD -s https://api.github.com/repos/$GIT_ACCOUNT/$GIT_REPO/pulls/$PULL_NUMBER) # https://developer.github.com/v4/reference/enum/commentauthorassociation/ PR_AUTHOR_MEMBERSHIP=$(echo $PULL_DESCRIPTION | sed 's/.*"author_association": "\([^,]*\)".*/\1/') COMMENTS=$(curl -ujbosstm-bot:$BOT_PASSWORD -s https://api.github.com/repos/$GIT_ACCOUNT/$GIT_REPO/issues/$PULL_NUMBER/comments) MEMBERS_COMMENTS=$(printf '%s' "$COMMENTS" | awk '/"author_association"|"body"/ { if(/MEMBER|COLLABORATOR|OWNER/) {getline; print;} }') # if author of the PR is permitted or if the comment on the PR contains text 'TESTIT' written by one of the members if [[ ! $PR_AUTHOR_MEMBERSHIP =~ MEMBER|COLLABORATOR|OWNER|CONTRIBUTOR ]] && [[ ! $MEMBERS_COMMENTS =~ TESTIT ]]; then echo "Author of pull request '$PULL_NUMBER' is not member of github jbosstm organization or member comment needs to contain text 'TESTIT'" printf "membership of PR:\n%s\n" "$PR_AUTHOR_MEMBERSHIP" printf "members comments:\n%s\n" "$MEMBERS_COMMENTS" comment_on_pull ':warning: CI not started.\n\nAuthor is not the '$GIT_REPO' contributor, members of $GIT_ACCOUNT can write comment of text `TESTIT` to permit PR being run.' exit 0 fi ``` > Change the Narayana CI jobs to consider membership of PR author > --------------------------------------------------------------- > > Key: JBTM-2996 > URL: https://issues.jboss.org/browse/JBTM-2996 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Affects Versions: 5.7.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > It would be good to start using gihub webhooks instead of a poller jenkins cron job. > Configure the triggers in Jenkins and webhook on github and consider using the plugin > https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 06:38:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 06:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2996) Change the Narayana CI jobs to consider membership of PR author In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537462#comment-13537462 ] Ondra Chaloupka edited comment on JBTM-2996 at 2/23/18 6:37 AM: ---------------------------------------------------------------- I distributed the change to all _pulls_ `-poller` jobs was (Author: ochaloup): I distributed the change to all _pulls_ `-poller` jobs. I ended up with the following ```bash export GIT_ACCOUNT=jbosstm export GIT_REPO=narayana export COMMENT_ON_PULL=1 function comment_on_pull { if [ "$COMMENT_ON_PULL" = "" ]; then return; fi PULL_NUMBER=$(echo $GIT_BRANCH | awk -F 'pull' '{ print $2 }' | awk -F '/' '{ print $2 }') if [ "$PULL_NUMBER" != "" ] then JSON="{ \"body\": \"$1\" }" curl -d "$JSON" -ujbosstm-bot:$BOT_PASSWORD https://api.github.com/repos/$GIT_ACCOUNT/$GIT_REPO/issues/$PULL_NUMBER/comments else echo "Not a pull request, so not commenting" fi } PULL_NUMBER=$(echo $GIT_BRANCH | awk -F 'pull' '{ print $2 }' | awk -F '/' '{ print $2 }') PULL_DESCRIPTION=$(curl -ujbosstm-bot:$BOT_PASSWORD -s https://api.github.com/repos/$GIT_ACCOUNT/$GIT_REPO/pulls/$PULL_NUMBER) # https://developer.github.com/v4/reference/enum/commentauthorassociation/ PR_AUTHOR_MEMBERSHIP=$(echo $PULL_DESCRIPTION | sed 's/.*"author_association": "\([^,]*\)".*/\1/') COMMENTS=$(curl -ujbosstm-bot:$BOT_PASSWORD -s https://api.github.com/repos/$GIT_ACCOUNT/$GIT_REPO/issues/$PULL_NUMBER/comments) MEMBERS_COMMENTS=$(printf '%s' "$COMMENTS" | awk '/"author_association"|"body"/ { if(/MEMBER|COLLABORATOR|OWNER/) {getline; print;} }') # if author of the PR is permitted or if the comment on the PR contains text 'TESTIT' written by one of the members if [[ ! $PR_AUTHOR_MEMBERSHIP =~ MEMBER|COLLABORATOR|OWNER|CONTRIBUTOR ]] && [[ ! $MEMBERS_COMMENTS =~ TESTIT ]]; then echo "Author of pull request '$PULL_NUMBER' is not member of github jbosstm organization or member comment needs to contain text 'TESTIT'" printf "membership of PR:\n%s\n" "$PR_AUTHOR_MEMBERSHIP" printf "members comments:\n%s\n" "$MEMBERS_COMMENTS" comment_on_pull ':warning: CI not started.\n\nAuthor is not the '$GIT_REPO' contributor, members of $GIT_ACCOUNT can write comment of text `TESTIT` to permit PR being run.' exit 0 fi ``` > Change the Narayana CI jobs to consider membership of PR author > --------------------------------------------------------------- > > Key: JBTM-2996 > URL: https://issues.jboss.org/browse/JBTM-2996 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Affects Versions: 5.7.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > It would be good to start using gihub webhooks instead of a poller jenkins cron job. > Configure the triggers in Jenkins and webhook on github and consider using the plugin > https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 06:38:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 06:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2996) Change the Narayana CI jobs to consider membership of PR author In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2996 started by Ondra Chaloupka. --------------------------------------------- > Change the Narayana CI jobs to consider membership of PR author > --------------------------------------------------------------- > > Key: JBTM-2996 > URL: https://issues.jboss.org/browse/JBTM-2996 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Affects Versions: 5.7.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > It would be good to start using gihub webhooks instead of a poller jenkins cron job. > Configure the triggers in Jenkins and webhook on github and consider using the plugin > https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 06:38:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 06:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2996) Change the Narayana CI jobs to consider membership of PR author In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka resolved JBTM-2996. ----------------------------------- Resolution: Done > Change the Narayana CI jobs to consider membership of PR author > --------------------------------------------------------------- > > Key: JBTM-2996 > URL: https://issues.jboss.org/browse/JBTM-2996 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Affects Versions: 5.7.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > It would be good to start using gihub webhooks instead of a poller jenkins cron job. > Configure the triggers in Jenkins and webhook on github and consider using the plugin > https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 08:16:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 08:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2995: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 08:16:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 08:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2989) Replace to use the DBCP2 in the spring quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2989: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > Replace to use the DBCP2 in the spring quickstarts > -------------------------------------------------- > > Key: JBTM-2989 > URL: https://issues.jboss.org/browse/JBTM-2989 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > It could be helpful to replace the transational driver when using with the spring. The transactional driver might be only used in the standalone. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 08:16:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 08:16:00 -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.8.0.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 > 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.5.0#75005) From issues at jboss.org Fri Feb 23 08:16:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 08:16:00 -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.8.0.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 > 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.5.0#75005) From issues at jboss.org Fri Feb 23 08:16:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 08:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2966) narayana-quickstarts-jts quickstart does not run standalone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2966: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > narayana-quickstarts-jts quickstart does not run standalone > ----------------------------------------------------------- > > Key: JBTM-2966 > URL: https://issues.jboss.org/browse/JBTM-2966 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The recovery quickstart does not run due to missing maven jboss-transaction-spi dependency. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 08:16:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 08:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2965) Unused source directory in the quickstart repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2965: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > Unused source directory in the quickstart repository > ---------------------------------------------------- > > Key: JBTM-2965 > URL: https://issues.jboss.org/browse/JBTM-2965 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > There is an artifact in our quickstart repo that does not look like a quickstart and no other pom in the quickstart and performance repositories references the artifact: > https://github.com/jbosstm/quickstart/tree/master/ArjunaJTS/jta > It has never changed since the initial commit: > {quote} > commit caabc37803bac12e47f4986baca21f9052e14abc > Author: Tom Jenkinson > Date: Tue Oct 2 11:05:51 2012 +0100 > Initial version of a performance comparitor for jts and jta > {quote} > This artefact needs deleting. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 08:16:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 08:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2913) Make the SPI a true dependency of standalone narayana-jta pom.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2913: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > Make the SPI a true dependency of standalone narayana-jta pom.xml > ----------------------------------------------------------------- > > Key: JBTM-2913 > URL: https://issues.jboss.org/browse/JBTM-2913 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > This means that users can simply import the narayana-jta dependency rather than both it and the SPI. > It is useful when being consumed by jbpm for example. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 08:16:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 08:16:01 -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.8.0.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 > 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.5.0#75005) From issues at jboss.org Fri Feb 23 08:16:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 08:16:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2880) Refactor codebase to minimize usage of e.printStackTrace() call and change for using logger In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2880: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > Refactor codebase to minimize usage of e.printStackTrace() call and change for using logger > ------------------------------------------------------------------------------------------- > > Key: JBTM-2880 > URL: https://issues.jboss.org/browse/JBTM-2880 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Affects Versions: 5.5.6.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next > > > The code base uses call `e.printStackTrace()` on several places. That usage should be minimized and used only when it's good reason for it. In general such calls should be replaced printing with `logger`, probably in level `WARN` with some additional information, why the stacktrace is printed - what error occured - included. > By quick check these are places where exception stack trace is printed directly to `stderr`. > {code} > -vertx/shared/src/main/java/ClientVerticle.java- > -vertx/shared/src/main/java/SampleVerticle2.java- > -vertx/shared/src/main/java/SampleVerticle1.java- > osgi/jta/src/main/java/org/jboss/narayana/osgi/jta/internal/ObjStoreBrowserImpl.java > XTS/WSAS/classes/com/arjuna/mwlabs/wsas/UserActivityImple.java > XTS/WSAS/classes/com/arjuna/mwlabs/wsas/activity/ActivityHandleImple.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf11/model/sagas/arjunacore/SagasHLSImple.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf11/model/twophase/arjunacore/TwoPhaseHLSImple.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf/model/sagas/arjunacore/ParticipantRecord.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf/model/sagas/arjunacore/CoordinatorControl.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf/model/twophase/arjunacore/ParticipantRecord.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf/model/twophase/arjunacore/CoordinatorControl.java > XTS/WSCF/classes/com/arjuna/mw/wscf/utils/DomUtil.java > XTS/WSCF/classes/com/arjuna/mw/wscf/protocols/ProtocolManager.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/RegistrarImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/context/ArjunaContextImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/remote/TransactionManagerImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/remote/UserTransactionImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/remote/UserTransactionStandaloneImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/participants/CleanupSynchronization.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/ContextFactoryImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/context/ArjunaContextImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/remote/UserBusinessActivityImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/remote/BusinessActivityManagerImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/remote/BAParticipantManagerImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/remote/UserBusinessActivityStandaloneImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/participants/CleanupSynchronization.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/ContextFactoryImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst/at/participants/DurableTwoPhaseCommitParticipant.java > XTS/localjunit/WSTX11-interop/src/main/java/com/jboss/transaction/txinterop/proxy/ProxyListenerService.java > XTS/localjunit/WSTFSC07-interop/src/main/java/com/jboss/transaction/wstf/proxy/ProxyListenerService.java > XTS/WS-T/dev/src/com/arjuna/schemas/ws/_2005/_10/wsarjtx/TerminationCoordinatorRPCService.java > XTS/WS-T/dev/src/com/arjuna/wst11/stub/CompletionStub.java > XTS/WS-T/dev/src/com/arjuna/wst11/stub/CompletionRPCStub.java > XTS/WS-T/dev/src/com/arjuna/wst11/stub/BusinessActivityTerminatorRPCStub.java > XTS/WS-T/dev/src/com/arjuna/wst11/messaging/TerminationCoordinatorRPCProcessorImpl.java > XTS/WS-T/dev/src/com/arjuna/wst11/messaging/CompletionCoordinatorProcessorImpl.java > XTS/WS-T/dev/src/com/arjuna/wst11/messaging/CompletionCoordinatorRPCProcessorImpl.java > XTS/WS-T/dev/src/com/arjuna/wst11/messaging/TerminationCoordinatorProcessorImpl.java > XTS/WS-C/dev/src/com/arjuna/wsc11/messaging/ActivationCoordinatorProcessorImpl.java > XTS/WS-C/dev/src/com/arjuna/wsc11/messaging/RegistrationCoordinatorProcessorImpl.java > XTS/WS-C/dev/src/com/arjuna/webservices/SoapFault.java > ArjunaJTA/jta/classes/com/arjuna/ats/jta/xa/XidImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/jca/XATerminatorImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/jca/TransactionImporterImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/TransactionImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/subordinate/TransactionImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/SubordinateJTAXAResourceOrphanFilter.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/DirectRecoverableConnection.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/ConnectionManager.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/ProvidedXADataSourceConnection.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/IndirectRecoverableConnection.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/recovery/JDBCXARecovery.java > blacktie/utils/cpp-plugin/src/main/java/org/jboss/narayana/blacktie/plugins/AddCommonSources.java > blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/server/SocketServer.java > blacktie/wildfly-blacktie/subsystem/src/main/java/org/codehaus/stomp/jms/ProtocolConverter.java > blacktie/blacktie-admin-services/src/main/java/org/jboss/narayana/blacktie/administration/core/AdministrationProxy.java > tools/src/main/java/io/narayana/perf/Measurement.java > rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java > rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java > txframework/src/main/java/org/jboss/narayana/txframework/impl/Participant.java > compensations/src/main/java/org/jboss/narayana/compensations/internal/ParticipantInterceptor.java > compensations/src/main/java/org/jboss/narayana/compensations/internal/ParticipantImpl.java > ArjunaCore/arjuna/services/classes/com/arjuna/ats/arjuna/services/recovery/RecoveryManagerService.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/utils/AndroidProcessId.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/abstractrecords/CadaverRecord.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/ShadowingStore.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/CacheStore.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/LogStore.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/AbstractRecord.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/BasicAction.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/common/ObjectStoreEnvironmentBean.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/log/LogBrowser.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/stats/TxPerfGraph.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/OTM.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/StateManager.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/recovery/RecoveryManager.java > ArjunaJTS/integration/src/main/java/com/arjuna/ats/internal/jbossatx/jta/jca/XATerminator.java > ArjunaJTS/integration/src/main/java/com/arjuna/ats/internal/jbossatx/jts/jca/XATerminator.java > ArjunaJTS/integration/src/main/java/com/arjuna/ats/internal/jbossatx/jts/PropagationContextManager.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/jca/XATerminatorImple.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/BaseTransaction.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/subordinate/jca/coordinator/ServerTransaction.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/subordinate/jca/SubordinateAtomicTransaction.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/subordinate/TransactionImple.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/subordinate/SubordinateAtomicTransaction.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/resources/jts/orbspecific/XAResourceRecord.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/recovery/jts/JCAServerTransactionRecoveryModule.java > ArjunaJTS/orbportability/classes/com/arjuna/orbportability/common/ant/IDLCompiler.java > ArjunaJTS/jts/services/classes/com/arjuna/ats/jts/services/transactionserver/TransactionServerService.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/utils/TxStoreLog.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/interposition/ServerControl.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/coordinator/ArjunaTransactionImple.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/jacorb/recoverycoordinators/ORBRunner.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/jacorb/recoverycoordinators/JacOrbRCServiceInit.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/ibmorb/recoverycoordinators/ORBRunner.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/javaidl/recoverycoordinators/ORBRunner.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/CurrentImple.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/TransactionFactoryImple.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/recovery/RecoveryEnablement.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/context/ContextManager.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/resources/ExtendedResourceRecord.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/TransactionServer.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/orbspecific/jacorb/interceptors/interposition/InterpositionClientRequestInterceptorImpl.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/orbspecific/jacorb/interceptors/context/ContextServerRequestInterceptorImpl.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/orbspecific/ibmorb/interceptors/context/ContextServerRequestInterceptorImpl.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/orbspecific/javaidl/interceptors/context/ContextServerRequestInterceptorImpl.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/ExplicitInterposition.java > STM/src/main/java/org/jboss/stm/internal/reflect/InvocationHandler.java > STM/src/main/java/org/jboss/stm/internal/proxy/OptimisticLockManagerProxy.java > STM/src/main/java/org/jboss/stm/internal/proxy/LockManagerProxy.java > STM/src/main/java/org/jboss/stm/internal/optimistic/OptimisticLockRecord.java > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 08:16:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 08:16:01 -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.8.0.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 > 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.5.0#75005) From issues at jboss.org Fri Feb 23 08:16:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 08:16:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2851) Upgrade BlackTie to a version of WildFly that works with JDK9 (when available) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2851: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > Upgrade BlackTie to a version of WildFly that works with JDK9 (when available) > ------------------------------------------------------------------------------ > > Key: JBTM-2851 > URL: https://issues.jboss.org/browse/JBTM-2851 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > The blacktie-admin-service-ear is failed when deploying the ear to the wildfly running with the JDK9. It could be an issue [1] and should be fix in [2]. > So we have to build the openjdk-orb 8.0.8.Beta1-SNAPSHOT or wait it for the final release. > [1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-May/007698.html > [2] https://github.com/jboss/openjdk-orb/pull/4 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Fri Feb 23 08:16:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Fri, 23 Feb 2018 08:16:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2841) HybridSocketEndpointQueue::_send() needs wrapper around apr_socket_send() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2841: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > HybridSocketEndpointQueue::_send() needs wrapper around apr_socket_send() > ------------------------------------------------------------------------- > > Key: JBTM-2841 > URL: https://issues.jboss.org/browse/JBTM-2841 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > tpreturn() seems to non-block send without checking tranfer length. > It needs a wrapper of looping apr_socket_send() until all of the data write to the socket. > similar like [stomp_write_buffer|https://github.com/jbosstm/narayana/blob/c035f66960d189a5b96d1940c9d251a4e2d7b113/blacktie/hybrid/src/main/cpp/stomp.c] -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 04:29:00 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 26 Feb 2018 04:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2997) Ensure that any LRA coordinator can control any LRA In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2997: -------------------------------------- Summary: Ensure that any LRA coordinator can control any LRA Key: JBTM-2997 URL: https://issues.jboss.org/browse/JBTM-2997 Project: JBoss Transaction Manager Issue Type: Feature Request Components: LRA Affects Versions: 5.8.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.later Currently the management of an LRA is restricted to the coordinator that created it. It would be preferable to have the option of allowing any coordinator be able to manage any LRA. The motivation for this feature is to enhance the usability of LRAs in cloud based environments. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 04:59:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 26 Feb 2018 04:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2992: ---------------------------- Priority: Minor (was: Critical) > Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar > ------------------------------------------------------------------------------ > > Key: JBTM-2992 > URL: https://issues.jboss.org/browse/JBTM-2992 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.7.2.Final > Environment: Java 9 > Reporter: Michal Karm Babacek > Assignee: Amos Feng > Priority: Minor > > {code} > [ERROR] Failed to execute goal on project tomcat-jta: > Could not resolve dependencies for project > org.jboss.narayana.tomcat:tomcat-jta:jar:5.7.2.Final-SNAPSHOT: > Could not find artifact > com.sun:tools:jar:1.6 at specified path /file-not-found/tools.jar -> [Help 1] > [ERROR] > {code} > See: StackOverflow and [~ogondza]'s comments -> [link|https://stackoverflow.com/questions/35240134/declare-maven-dependency-on-tools-jar-to-work-on-jdk-9#35244168] -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 08:10:00 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 26 Feb 2018 08:10:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538153#comment-13538153 ] Michael Musgrove commented on JBTM-2995: ---------------------------------------- My supposition is that it is a test environment issue and the run is trying to recovery an old (JTS) log being left around from a previous step in the CI build. I have not been able to reproduce the issue in order to validate my hypothesis. > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 08:22:01 2018 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 26 Feb 2018 08:22:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538163#comment-13538163 ] Michael Musgrove commented on JBTM-2992: ---------------------------------------- [~zhfeng] What was the justification for changing the priority? > Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar > ------------------------------------------------------------------------------ > > Key: JBTM-2992 > URL: https://issues.jboss.org/browse/JBTM-2992 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.7.2.Final > Environment: Java 9 > Reporter: Michal Karm Babacek > Assignee: Amos Feng > Priority: Minor > > {code} > [ERROR] Failed to execute goal on project tomcat-jta: > Could not resolve dependencies for project > org.jboss.narayana.tomcat:tomcat-jta:jar:5.7.2.Final-SNAPSHOT: > Could not find artifact > com.sun:tools:jar:1.6 at specified path /file-not-found/tools.jar -> [Help 1] > [ERROR] > {code} > See: StackOverflow and [~ogondza]'s comments -> [link|https://stackoverflow.com/questions/35240134/declare-maven-dependency-on-tools-jar-to-work-on-jdk-9#35244168] -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 08:32:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 26 Feb 2018 08:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2995: ---------------------------------- Attachment: .surefire.jstack.23019.txt.syntax surefire.jstack.23019.txt wfly.jstack.txt > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: surefire.jstack.23019.txt, wfly.jstack.txt > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 08:32:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 26 Feb 2018 08:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2995: ---------------------------------- Attachment: (was: .surefire.jstack.23019.txt.syntax) > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: surefire.jstack.23019.txt, wfly.jstack.txt > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 08:33:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 26 Feb 2018 08:33:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538179#comment-13538179 ] Ondra Chaloupka commented on JBTM-2995: --------------------------------------- [~mmusgrov] I just uploaded thread dump of the handing threads from my machine. > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: surefire.jstack.23019.txt, wfly.jstack.txt > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 16:36:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 26 Feb 2018 16:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2928) Provide WS-AT Integration with .NET In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2928: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Provide WS-AT Integration with .NET > ----------------------------------- > > Key: JBTM-2928 > URL: https://issues.jboss.org/browse/JBTM-2928 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: J?rg B?sner > > Provide WS-AT integration for .NET -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 16:38:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 26 Feb 2018 16:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2994) TransactionExtension uses old version of addAnnotatedType which results in warnings being logged In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2994: ---------------------------------- Affects Version/s: 5.7.2.Final > TransactionExtension uses old version of addAnnotatedType which results in warnings being logged > ------------------------------------------------------------------------------------------------ > > Key: JBTM-2994 > URL: https://issues.jboss.org/browse/JBTM-2994 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.7.2.Final > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 5.8.0.Final > > > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNever is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNotSupported is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1! -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 16:38:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 26 Feb 2018 16:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2994) TransactionExtension uses old version of addAnnotatedType which results in warnings being logged In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2994: ---------------------------------- Fix Version/s: 5.8.0.Final > TransactionExtension uses old version of addAnnotatedType which results in warnings being logged > ------------------------------------------------------------------------------------------------ > > Key: JBTM-2994 > URL: https://issues.jboss.org/browse/JBTM-2994 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.7.2.Final > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 5.8.0.Final > > > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNever is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNotSupported is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1! -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 16:38:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 26 Feb 2018 16:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2983) Commit failure in WFLY LocalResource does not return error to the caller In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2983: ---------------------------------- Fix Version/s: 5.7.2.Final > Commit failure in WFLY LocalResource does not return error to the caller > ------------------------------------------------------------------------ > > Key: JBTM-2983 > URL: https://issues.jboss.org/browse/JBTM-2983 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.7.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Critical > Fix For: 5.7.2.Final > > > In case that an exception is thrown during one-phase commit of non-XA transaction participant the error is swallowed and not returned to the caller. When tested with WFLY the excpetion is shown in the log, the commit fails but the client thinks that everything worked well. > The relevant part of the exception stacktrace when error on commit occurs is > {code} > at com.mysql.jdbc.ConnectionImpl.commit(ConnectionImpl.java:1549) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnection.commit(LocalManagedConnection.java:96) > at org.jboss.jca.core.tx.jbossts.LocalXAResourceImpl.commit(LocalXAResourceImpl.java:172) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAOnePhaseResource.commit(XAOnePhaseResource.java:120) > at com.arjuna.ats.internal.arjuna.abstractrecords.LastResourceRecord.topLevelPrepare(LastResourceRecord.java:152) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.topLevelOnePhaseCommit(AbstractRecord.java:428) > at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2386) > at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1497) > {code} > It seems that there is issue at > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/resources/arjunacore/XAOnePhaseResource.java#L164 > which does say something about recovery but for one phase nonXA there will be no recovery. > The decision that the {{XAOnePhaseResource}} is used for the txn work is done at > https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/TransactionImple.java#L792 > where depending how the setup of {{jtaEnvironmentBean.setLastResourceOptimisationInterfaceClassName}} was done. This is done in WFLY at > https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java/org/jboss/as/txn/service/JTAEnvironmentBeanService.java#L60 -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 16:39:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 26 Feb 2018 16:39:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2928) Provide WS-AT Integration with .NET In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2928: ---------------------------------- Component/s: XTS > Provide WS-AT Integration with .NET > ----------------------------------- > > Key: JBTM-2928 > URL: https://issues.jboss.org/browse/JBTM-2928 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: XTS > Reporter: J?rg B?sner > > Provide WS-AT integration for .NET -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 16:40:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 26 Feb 2018 16:40:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2928) Provide WS-AT Integration with .NET In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2928: ---------------------------------- Affects Version/s: 5.7.2.Final > Provide WS-AT Integration with .NET > ----------------------------------- > > Key: JBTM-2928 > URL: https://issues.jboss.org/browse/JBTM-2928 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: XTS > Affects Versions: 5.7.2.Final > Reporter: J?rg B?sner > Fix For: 5.8.0.Final > > > Provide WS-AT integration for .NET -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 16:40:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Mon, 26 Feb 2018 16:40:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2928) Provide WS-AT Integration with .NET In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2928: ---------------------------------- Fix Version/s: 5.8.0.Final > Provide WS-AT Integration with .NET > ----------------------------------- > > Key: JBTM-2928 > URL: https://issues.jboss.org/browse/JBTM-2928 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: XTS > Affects Versions: 5.7.2.Final > Reporter: J?rg B?sner > Fix For: 5.8.0.Final > > > Provide WS-AT integration for .NET -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 16:59:00 2018 From: issues at jboss.org (Tomasz Adamski (JIRA)) Date: Mon, 26 Feb 2018 16:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Adamski reassigned JBTM-2995: ------------------------------------ Assignee: Tomasz Adamski (was: Michael Musgrove) > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Tomasz Adamski > Fix For: 5.next > > Attachments: surefire.jstack.23019.txt, wfly.jstack.txt > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 20:57:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 26 Feb 2018 20:57:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538545#comment-13538545 ] Amos Feng commented on JBTM-2992: --------------------------------- [~mmusgrov] I checked the CI jdk9 related jobs and can not find this issue. > Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar > ------------------------------------------------------------------------------ > > Key: JBTM-2992 > URL: https://issues.jboss.org/browse/JBTM-2992 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.7.2.Final > Environment: Java 9 > Reporter: Michal Karm Babacek > Assignee: Amos Feng > Priority: Minor > > {code} > [ERROR] Failed to execute goal on project tomcat-jta: > Could not resolve dependencies for project > org.jboss.narayana.tomcat:tomcat-jta:jar:5.7.2.Final-SNAPSHOT: > Could not find artifact > com.sun:tools:jar:1.6 at specified path /file-not-found/tools.jar -> [Help 1] > [ERROR] > {code} > See: StackOverflow and [~ogondza]'s comments -> [link|https://stackoverflow.com/questions/35240134/declare-maven-dependency-on-tools-jar-to-work-on-jdk-9#35244168] -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 21:01:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 26 Feb 2018 21:01:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538546#comment-13538546 ] Amos Feng commented on JBTM-2992: --------------------------------- [~mbabacek] [~ogondza] We have the [narayana jdk9-experimental|https://github.com/jbosstm/narayana/tree/jdk9-experimental] and can you test with this branch ? Also can you provide the full build log ? > Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar > ------------------------------------------------------------------------------ > > Key: JBTM-2992 > URL: https://issues.jboss.org/browse/JBTM-2992 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.7.2.Final > Environment: Java 9 > Reporter: Michal Karm Babacek > Assignee: Amos Feng > Priority: Minor > > {code} > [ERROR] Failed to execute goal on project tomcat-jta: > Could not resolve dependencies for project > org.jboss.narayana.tomcat:tomcat-jta:jar:5.7.2.Final-SNAPSHOT: > Could not find artifact > com.sun:tools:jar:1.6 at specified path /file-not-found/tools.jar -> [Help 1] > [ERROR] > {code} > See: StackOverflow and [~ogondza]'s comments -> [link|https://stackoverflow.com/questions/35240134/declare-maven-dependency-on-tools-jar-to-work-on-jdk-9#35244168] -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Mon Feb 26 21:02:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 26 Feb 2018 21:02:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2992) Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538546#comment-13538546 ] Amos Feng edited comment on JBTM-2992 at 2/26/18 9:01 PM: ---------------------------------------------------------- [~mbabacek] and [~ogondza], we have the [narayana jdk9-experimental|https://github.com/jbosstm/narayana/tree/jdk9-experimental] and can you test with this branch ? Also can you provide the full build log ? was (Author: zhfeng): [~mbabacek] [~ogondza] We have the [narayana jdk9-experimental|https://github.com/jbosstm/narayana/tree/jdk9-experimental] and can you test with this branch ? Also can you provide the full build log ? > Narayana TS does not run with JDK 9 due to unsatisfied dependency on tools.jar > ------------------------------------------------------------------------------ > > Key: JBTM-2992 > URL: https://issues.jboss.org/browse/JBTM-2992 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.7.2.Final > Environment: Java 9 > Reporter: Michal Karm Babacek > Assignee: Amos Feng > Priority: Minor > > {code} > [ERROR] Failed to execute goal on project tomcat-jta: > Could not resolve dependencies for project > org.jboss.narayana.tomcat:tomcat-jta:jar:5.7.2.Final-SNAPSHOT: > Could not find artifact > com.sun:tools:jar:1.6 at specified path /file-not-found/tools.jar -> [Help 1] > [ERROR] > {code} > See: StackOverflow and [~ogondza]'s comments -> [link|https://stackoverflow.com/questions/35240134/declare-maven-dependency-on-tools-jar-to-work-on-jdk-9#35244168] -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 05:04:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 05:04:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka reassigned JBTM-2995: ------------------------------------- Assignee: Ondra Chaloupka (was: Tomasz Adamski) > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Ondra Chaloupka > Fix For: 5.next > > Attachments: surefire.jstack.23019.txt, wfly.jstack.txt > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 05:26:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 05:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538672#comment-13538672 ] Ondra Chaloupka commented on JBTM-2995: --------------------------------------- I was able to reproduce this on my local machine thus I was trying to check the existence of the JTS log and I think there isn't. I think the reason is in wrong implementation of {{TransactionImporterImple}}. When the failure happens the jts version is in serve ({{com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple}}). That's because of race condition of transaction manager instance being used. The {{SubordinationManager}} decides based on the transaction manager implementation is setup in {{JTAEnvironmentBean}} (https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/jca/SubordinationManager.java#L144). At time the {{JTAEnvironmentBeanService}} is started (https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java/org/jboss/as/txn/service/JTAEnvironmentBeanService.java#L60) the content of the {{transactionManagerClassName}} is setup (https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/jta/common/JTAEnvironmentBean.java#L54) based on the {{jbossts-properties.xml}} from https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/narayana-jts-idlj/src/main/resources/jbossts-properties.xml#L149 where jts transaction manager is configured. Then recovery manager service is started and before the setup to the JTA transaction manager, by definition taken from {{standalone.xml}} in WFLY, is done (https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java/org/jboss/as/txn/service/ArjunaTransactionManagerService.java#L102) the recovery already starts (https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java/org/jboss/as/txn/subsystem/TransactionSubsystemAdd.java#L243) and uses jts importer which fails of not having ORB configured. My debugging output {code} 2018-02-26 23:46:49,050 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 2.0.0.Final starting 2018-02-26 23:46:49,111 INFO [stdout] (MSC service thread 1-8) >>> ochaloup >>> : setting the txn manager: com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple -> 2018-02-26 23:46:49,112 ERROR [stderr] (MSC service thread 1-8) java.lang.Exception: Stack trace 2018-02-26 23:46:49,113 ERROR [stderr] (MSC service thread 1-8) at java.lang.Thread.dumpStack(Thread.java:1336) 2018-02-26 23:46:49,113 ERROR [stderr] (MSC service thread 1-8) at com.arjuna.ats.jta.common.JTAEnvironmentBean.setTransactionManagerClassName(JTAEnvironmentBean.java:167) 2018-02-26 23:46:49,113 ERROR [stderr] (MSC service thread 1-8) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 2018-02-26 23:46:49,113 ERROR [stderr] (MSC service thread 1-8) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 2018-02-26 23:46:49,114 ERROR [stderr] (MSC service thread 1-8) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 2018-02-26 23:46:49,114 ERROR [stderr] (MSC service thread 1-8) at java.lang.reflect.Method.invoke(Method.java:498) 2018-02-26 23:46:49,114 ERROR [stderr] (MSC service thread 1-8) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.handleSimpleProperty(BeanPopulator.java:298) 2018-02-26 23:46:49,114 ERROR [stderr] (MSC service thread 1-8) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:172) 2018-02-26 23:46:49,114 ERROR [stderr] (MSC service thread 1-8) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:87) 2018-02-26 23:46:49,115 ERROR [stderr] (MSC service thread 1-8) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:53) 2018-02-26 23:46:49,115 ERROR [stderr] (MSC service thread 1-8) at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42) 2018-02-26 23:46:49,115 ERROR [stderr] (MSC service thread 1-8) at org.jboss.as.txn.service.JTAEnvironmentBeanService.start(JTAEnvironmentBeanService.java:60) 2018-02-26 23:46:49,116 ERROR [stderr] (MSC service thread 1-8) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) 2018-02-26 23:46:49,116 ERROR [stderr] (MSC service thread 1-8) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) 2018-02-26 23:46:49,116 ERROR [stderr] (MSC service thread 1-8) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) 2018-02-26 23:46:49,116 ERROR [stderr] (MSC service thread 1-8) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) 2018-02-26 23:46:49,117 ERROR [stderr] (MSC service thread 1-8) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) 2018-02-26 23:46:49,118 ERROR [stderr] (MSC service thread 1-8) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) 2018-02-26 23:46:49,119 ERROR [stderr] (MSC service thread 1-8) at java.lang.Thread.run(Thread.java:748) 2018-02-26 23:46:49,125 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0014: Creating file handler for path '/home/ochaloup/jboss/wildfly/dist/target/wildfly-12.0.0.Beta2-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] 2018-02-26 23:46:49,130 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. 2018-02-26 23:46:49,132 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting 2018-02-26 23:46:49,352 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 2018-02-26 23:46:49,359 INFO [stdout] (MSC service thread 1-6) >>> ochaloup >>> : setting the txn manager: com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate -> 2018-02-26 23:46:49,360 ERROR [stderr] (MSC service thread 1-6) java.lang.Exception: Stack trace 2018-02-26 23:46:49,360 ERROR [stderr] (MSC service thread 1-6) at java.lang.Thread.dumpStack(Thread.java:1336) 2018-02-26 23:46:49,360 ERROR [stderr] (MSC service thread 1-6) at com.arjuna.ats.jta.common.JTAEnvironmentBean.setTransactionManagerClassName(JTAEnvironmentBean.java:167) 2018-02-26 23:46:49,360 INFO [stdout] (Periodic Recovery) >>> ochaloup >>> txType init: null 2018-02-26 23:46:49,360 ERROR [stderr] (MSC service thread 1-6) at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:102) 2018-02-26 23:46:49,361 ERROR [stderr] (MSC service thread 1-6) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) 2018-02-26 23:46:49,361 ERROR [stderr] (MSC service thread 1-6) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) 2018-02-26 23:46:49,361 ERROR [stderr] (MSC service thread 1-6) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) 2018-02-26 23:46:49,361 ERROR [stderr] (MSC service thread 1-6) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) 2018-02-26 23:46:49,362 ERROR [stderr] (MSC service thread 1-6) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) 2018-02-26 23:46:49,362 ERROR [stderr] (MSC service thread 1-6) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) 2018-02-26 23:46:49,362 ERROR [stderr] (MSC service thread 1-6) at java.lang.Thread.run(Thread.java:748) 2018-02-26 23:46:49,368 INFO [stdout] (Periodic Recovery) >>> ochaloup >>> txType init2: JTS 2018-02-26 23:46:49,369 ERROR [stderr] (Periodic Recovery) java.lang.Exception: Stack trace 2018-02-26 23:46:49,369 ERROR [stderr] (Periodic Recovery) at java.lang.Thread.dumpStack(Thread.java:1336) 2018-02-26 23:46:49,369 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.SubordinationManager.initTransactionImporter(SubordinationManager.java:96) 2018-02-26 23:46:49,369 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.SubordinationManager.getTransactionImporter(SubordinationManager.java:46) 2018-02-26 23:46:49,370 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.recovery.arjunacore.SubordinateAtomicActionRecoveryModule.periodicWorkFirstPass(SubordinateAtomicActionRecoveryModule.java:74) 2018-02-26 23:46:49,370 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:765) 2018-02-26 23:46:49,370 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) 2018-02-26 23:46:49,404 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffff0a000009:-5269a529:5a948e53:14 and type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. 2018-02-26 23:46:49,409 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet 2018-02-26 23:46:49,409 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError 2018-02-26 23:46:49,410 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) 2018-02-26 23:46:49,410 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) 2018-02-26 23:46:49,410 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) 2018-02-26 23:46:49,410 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) 2018-02-26 23:46:49,411 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) 2018-02-26 23:46:49,411 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) 2018-02-26 23:46:49,411 WARN [com.arjuna.ats.arjuna] (MSC service thread 1-6) ARJUNA012087: Activate of atomic action with id 0:ffff0a000009:-5269a529:5a948e53:14 and type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. 2018-02-26 23:46:49,411 FATAL [com.arjuna.ats.jts] (MSC service thread 1-6) ARJUNA022006: The ORB has not been initialized yet 2018-02-26 23:46:49,412 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.local: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1706) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) at java.lang.Thread.run(Thread.java:748) Caused by: com.arjuna.ats.arjuna.exceptions.FatalError at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) ... 5 more {code} > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Ondra Chaloupka > Fix For: 5.next > > Attachments: surefire.jstack.23019.txt, wfly.jstack.txt > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 05:30:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 05:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538672#comment-13538672 ] Ondra Chaloupka edited comment on JBTM-2995 at 2/27/18 5:29 AM: ---------------------------------------------------------------- I was able to reproduce this on my local machine thus I was trying to check the existence of the JTS log and I think there isn't. I think the reason is in wrong implementation of {{TransactionImporterImple}}. When the failure happens the jts version is in serve ({{com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple}}). That's because of race condition of transaction manager instance being used. The {{SubordinationManager}} decides based on the transaction manager implementation is setup in {{JTAEnvironmentBean}} (https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/jca/SubordinationManager.java#L144). At time the {{JTAEnvironmentBeanService}} is started (https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java/org/jboss/as/txn/service/JTAEnvironmentBeanService.java#L60) the content of the {{transactionManagerClassName}} is setup (https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/jta/common/JTAEnvironmentBean.java#L54) based on the {{jbossts-properties.xml}} from https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/narayana-jts-idlj/src/main/resources/jbossts-properties.xml#L149 where jts transaction manager is configured. Then recovery manager service is started and before the setup to the JTA transaction manager, by definition taken from {{standalone.xml}} in WFLY, is done (https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java/org/jboss/as/txn/service/ArjunaTransactionManagerService.java#L102) the recovery already starts (https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java/org/jboss/as/txn/subsystem/TransactionSubsystemAdd.java#L243) and uses jts importer which fails of not having ORB configured. My debugging output {code} INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 2.0.0.Final starting INFO [stdout] (MSC service thread 1-8) >>> ochaloup >>> : setting the txn manager: com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple -> ERROR [stderr] (MSC service thread 1-8) java.lang.Exception: Stack trace ERROR [stderr] (MSC service thread 1-8) at java.lang.Thread.dumpStack(Thread.java:1336) ERROR [stderr] (MSC service thread 1-8) at com.arjuna.ats.jta.common.JTAEnvironmentBean.setTransactionManagerClassName(JTAEnvironmentBean.java:167) ERROR [stderr] (MSC service thread 1-8) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ERROR [stderr] (MSC service thread 1-8) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ERROR [stderr] (MSC service thread 1-8) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ERROR [stderr] (MSC service thread 1-8) at java.lang.reflect.Method.invoke(Method.java:498) ERROR [stderr] (MSC service thread 1-8) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.handleSimpleProperty(BeanPopulator.java:298) ERROR [stderr] (MSC service thread 1-8) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:172) ERROR [stderr] (MSC service thread 1-8) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:87) ERROR [stderr] (MSC service thread 1-8) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:53) ERROR [stderr] (MSC service thread 1-8) at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42) ERROR [stderr] (MSC service thread 1-8) at org.jboss.as.txn.service.JTAEnvironmentBeanService.start(JTAEnvironmentBeanService.java:60) ERROR [stderr] (MSC service thread 1-8) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) ERROR [stderr] (MSC service thread 1-8) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) ERROR [stderr] (MSC service thread 1-8) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) ERROR [stderr] (MSC service thread 1-8) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) ERROR [stderr] (MSC service thread 1-8) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) ERROR [stderr] (MSC service thread 1-8) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) ERROR [stderr] (MSC service thread 1-8) at java.lang.Thread.run(Thread.java:748) INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0014: Creating file handler for path '/home/ochaloup/jboss/wildfly/dist/target/wildfly-12.0.0.Beta2-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 INFO [stdout] (MSC service thread 1-6) >>> ochaloup >>> : setting the txn manager: com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate -> ERROR [stderr] (MSC service thread 1-6) java.lang.Exception: Stack trace ERROR [stderr] (MSC service thread 1-6) at java.lang.Thread.dumpStack(Thread.java:1336) ERROR [stderr] (MSC service thread 1-6) at com.arjuna.ats.jta.common.JTAEnvironmentBean.setTransactionManagerClassName(JTAEnvironmentBean.java:167) INFO [stdout] (Periodic Recovery) >>> ochaloup >>> txType init: null ERROR [stderr] (MSC service thread 1-6) at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:102) ERROR [stderr] (MSC service thread 1-6) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) ERROR [stderr] (MSC service thread 1-6) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) ERROR [stderr] (MSC service thread 1-6) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) ERROR [stderr] (MSC service thread 1-6) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) ERROR [stderr] (MSC service thread 1-6) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) ERROR [stderr] (MSC service thread 1-6) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) ERROR [stderr] (MSC service thread 1-6) at java.lang.Thread.run(Thread.java:748) INFO [stdout] (Periodic Recovery) >>> ochaloup >>> txType init2: JTS ERROR [stderr] (Periodic Recovery) java.lang.Exception: Stack trace ERROR [stderr] (Periodic Recovery) at java.lang.Thread.dumpStack(Thread.java:1336) ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.SubordinationManager.initTransactionImporter(SubordinationManager.java:96) ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.SubordinationManager.getTransactionImporter(SubordinationManager.java:46) ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.recovery.arjunacore.SubordinateAtomicActionRecoveryModule.periodicWorkFirstPass(SubordinateAtomicActionRecoveryModule.java:74) ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:765) ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffff0a000009:-5269a529:5a948e53:14 and type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) WARN [com.arjuna.ats.arjuna] (MSC service thread 1-6) ARJUNA012087: Activate of atomic action with id 0:ffff0a000009:-5269a529:5a948e53:14 and type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. FATAL [com.arjuna.ats.jts] (MSC service thread 1-6) ARJUNA022006: The ORB has not been initialized yet ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.local: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1706) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) at java.lang.Thread.run(Thread.java:748) Caused by: com.arjuna.ats.arjuna.exceptions.FatalError at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) ... 5 more {code} was (Author: ochaloup): I was able to reproduce this on my local machine thus I was trying to check the existence of the JTS log and I think there isn't. I think the reason is in wrong implementation of {{TransactionImporterImple}}. When the failure happens the jts version is in serve ({{com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple}}). That's because of race condition of transaction manager instance being used. The {{SubordinationManager}} decides based on the transaction manager implementation is setup in {{JTAEnvironmentBean}} (https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/jca/SubordinationManager.java#L144). At time the {{JTAEnvironmentBeanService}} is started (https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java/org/jboss/as/txn/service/JTAEnvironmentBeanService.java#L60) the content of the {{transactionManagerClassName}} is setup (https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/jta/common/JTAEnvironmentBean.java#L54) based on the {{jbossts-properties.xml}} from https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/narayana-jts-idlj/src/main/resources/jbossts-properties.xml#L149 where jts transaction manager is configured. Then recovery manager service is started and before the setup to the JTA transaction manager, by definition taken from {{standalone.xml}} in WFLY, is done (https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java/org/jboss/as/txn/service/ArjunaTransactionManagerService.java#L102) the recovery already starts (https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java/org/jboss/as/txn/subsystem/TransactionSubsystemAdd.java#L243) and uses jts importer which fails of not having ORB configured. My debugging output {code} 2018-02-26 23:46:49,050 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 2.0.0.Final starting 2018-02-26 23:46:49,111 INFO [stdout] (MSC service thread 1-8) >>> ochaloup >>> : setting the txn manager: com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple -> 2018-02-26 23:46:49,112 ERROR [stderr] (MSC service thread 1-8) java.lang.Exception: Stack trace 2018-02-26 23:46:49,113 ERROR [stderr] (MSC service thread 1-8) at java.lang.Thread.dumpStack(Thread.java:1336) 2018-02-26 23:46:49,113 ERROR [stderr] (MSC service thread 1-8) at com.arjuna.ats.jta.common.JTAEnvironmentBean.setTransactionManagerClassName(JTAEnvironmentBean.java:167) 2018-02-26 23:46:49,113 ERROR [stderr] (MSC service thread 1-8) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 2018-02-26 23:46:49,113 ERROR [stderr] (MSC service thread 1-8) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 2018-02-26 23:46:49,114 ERROR [stderr] (MSC service thread 1-8) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 2018-02-26 23:46:49,114 ERROR [stderr] (MSC service thread 1-8) at java.lang.reflect.Method.invoke(Method.java:498) 2018-02-26 23:46:49,114 ERROR [stderr] (MSC service thread 1-8) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.handleSimpleProperty(BeanPopulator.java:298) 2018-02-26 23:46:49,114 ERROR [stderr] (MSC service thread 1-8) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:172) 2018-02-26 23:46:49,114 ERROR [stderr] (MSC service thread 1-8) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:87) 2018-02-26 23:46:49,115 ERROR [stderr] (MSC service thread 1-8) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:53) 2018-02-26 23:46:49,115 ERROR [stderr] (MSC service thread 1-8) at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42) 2018-02-26 23:46:49,115 ERROR [stderr] (MSC service thread 1-8) at org.jboss.as.txn.service.JTAEnvironmentBeanService.start(JTAEnvironmentBeanService.java:60) 2018-02-26 23:46:49,116 ERROR [stderr] (MSC service thread 1-8) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) 2018-02-26 23:46:49,116 ERROR [stderr] (MSC service thread 1-8) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) 2018-02-26 23:46:49,116 ERROR [stderr] (MSC service thread 1-8) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) 2018-02-26 23:46:49,116 ERROR [stderr] (MSC service thread 1-8) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) 2018-02-26 23:46:49,117 ERROR [stderr] (MSC service thread 1-8) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) 2018-02-26 23:46:49,118 ERROR [stderr] (MSC service thread 1-8) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) 2018-02-26 23:46:49,119 ERROR [stderr] (MSC service thread 1-8) at java.lang.Thread.run(Thread.java:748) 2018-02-26 23:46:49,125 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0014: Creating file handler for path '/home/ochaloup/jboss/wildfly/dist/target/wildfly-12.0.0.Beta2-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] 2018-02-26 23:46:49,130 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. 2018-02-26 23:46:49,132 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting 2018-02-26 23:46:49,352 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 2018-02-26 23:46:49,359 INFO [stdout] (MSC service thread 1-6) >>> ochaloup >>> : setting the txn manager: com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate -> 2018-02-26 23:46:49,360 ERROR [stderr] (MSC service thread 1-6) java.lang.Exception: Stack trace 2018-02-26 23:46:49,360 ERROR [stderr] (MSC service thread 1-6) at java.lang.Thread.dumpStack(Thread.java:1336) 2018-02-26 23:46:49,360 ERROR [stderr] (MSC service thread 1-6) at com.arjuna.ats.jta.common.JTAEnvironmentBean.setTransactionManagerClassName(JTAEnvironmentBean.java:167) 2018-02-26 23:46:49,360 INFO [stdout] (Periodic Recovery) >>> ochaloup >>> txType init: null 2018-02-26 23:46:49,360 ERROR [stderr] (MSC service thread 1-6) at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:102) 2018-02-26 23:46:49,361 ERROR [stderr] (MSC service thread 1-6) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) 2018-02-26 23:46:49,361 ERROR [stderr] (MSC service thread 1-6) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) 2018-02-26 23:46:49,361 ERROR [stderr] (MSC service thread 1-6) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) 2018-02-26 23:46:49,361 ERROR [stderr] (MSC service thread 1-6) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) 2018-02-26 23:46:49,362 ERROR [stderr] (MSC service thread 1-6) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) 2018-02-26 23:46:49,362 ERROR [stderr] (MSC service thread 1-6) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) 2018-02-26 23:46:49,362 ERROR [stderr] (MSC service thread 1-6) at java.lang.Thread.run(Thread.java:748) 2018-02-26 23:46:49,368 INFO [stdout] (Periodic Recovery) >>> ochaloup >>> txType init2: JTS 2018-02-26 23:46:49,369 ERROR [stderr] (Periodic Recovery) java.lang.Exception: Stack trace 2018-02-26 23:46:49,369 ERROR [stderr] (Periodic Recovery) at java.lang.Thread.dumpStack(Thread.java:1336) 2018-02-26 23:46:49,369 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.SubordinationManager.initTransactionImporter(SubordinationManager.java:96) 2018-02-26 23:46:49,369 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.SubordinationManager.getTransactionImporter(SubordinationManager.java:46) 2018-02-26 23:46:49,370 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.recovery.arjunacore.SubordinateAtomicActionRecoveryModule.periodicWorkFirstPass(SubordinateAtomicActionRecoveryModule.java:74) 2018-02-26 23:46:49,370 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:765) 2018-02-26 23:46:49,370 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) 2018-02-26 23:46:49,404 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffff0a000009:-5269a529:5a948e53:14 and type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. 2018-02-26 23:46:49,409 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet 2018-02-26 23:46:49,409 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError 2018-02-26 23:46:49,410 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) 2018-02-26 23:46:49,410 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) 2018-02-26 23:46:49,410 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) 2018-02-26 23:46:49,410 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) 2018-02-26 23:46:49,411 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) 2018-02-26 23:46:49,411 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) 2018-02-26 23:46:49,411 WARN [com.arjuna.ats.arjuna] (MSC service thread 1-6) ARJUNA012087: Activate of atomic action with id 0:ffff0a000009:-5269a529:5a948e53:14 and type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. 2018-02-26 23:46:49,411 FATAL [com.arjuna.ats.jts] (MSC service thread 1-6) ARJUNA022006: The ORB has not been initialized yet 2018-02-26 23:46:49,412 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.local: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1706) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) at java.lang.Thread.run(Thread.java:748) Caused by: com.arjuna.ats.arjuna.exceptions.FatalError at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) ... 5 more {code} > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Ondra Chaloupka > Fix For: 5.next > > Attachments: surefire.jstack.23019.txt, wfly.jstack.txt > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 05:46:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 05:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538689#comment-13538689 ] Ondra Chaloupka commented on JBTM-2995: --------------------------------------- My idea is moving {{JTAEnvironmentBeanService}} initiation and its setup before the recovery service is started: https://github.com/ochaloup/wildfly/commit/7b91b4162826b62733a73bd5d865179a8aeb6710 > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Ondra Chaloupka > Fix For: 5.next > > Attachments: surefire.jstack.23019.txt, wfly.jstack.txt > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 05:49:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 05:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538691#comment-13538691 ] Ondra Chaloupka commented on JBTM-2995: --------------------------------------- [~mmusgrov] would you be fine if I took care of this issue and create a WFLY jira? Would you be so kind and verify my approach? > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Ondra Chaloupka > Fix For: 5.next > > Attachments: surefire.jstack.23019.txt, wfly.jstack.txt > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 06:48:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 06:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2989) Replace to use the DBCP2 in the spring quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538741#comment-13538741 ] Ondra Chaloupka commented on JBTM-2989: --------------------------------------- hi [~zhfeng], do you think this jira can be resolved and closed with fix version 5.8.0.Final? > Replace to use the DBCP2 in the spring quickstarts > -------------------------------------------------- > > Key: JBTM-2989 > URL: https://issues.jboss.org/browse/JBTM-2989 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > It could be helpful to replace the transational driver when using with the spring. The transactional driver might be only used in the standalone. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 06:52:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 06:52:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2966) narayana-quickstarts-jts quickstart does not run standalone In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538746#comment-13538746 ] Ondra Chaloupka commented on JBTM-2966: --------------------------------------- hi [~mmusgrov], checking jiras for the 5.8.0.Final release. As I can see PR being merged, do you think this is fixed and could be marked as resolved with the appropriate fix version? > narayana-quickstarts-jts quickstart does not run standalone > ----------------------------------------------------------- > > Key: JBTM-2966 > URL: https://issues.jboss.org/browse/JBTM-2966 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The recovery quickstart does not run due to missing maven jboss-transaction-spi dependency. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 06:52:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 06:52:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2965) Unused source directory in the quickstart repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538747#comment-13538747 ] Ondra Chaloupka commented on JBTM-2965: --------------------------------------- hi [~mmusgrov], checking jiras for the 5.8.0.Final release. As I can see PR being merged, do you think this is fixed and could be marked as resolved with the appropriate fix version? > Unused source directory in the quickstart repository > ---------------------------------------------------- > > Key: JBTM-2965 > URL: https://issues.jboss.org/browse/JBTM-2965 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > There is an artifact in our quickstart repo that does not look like a quickstart and no other pom in the quickstart and performance repositories references the artifact: > https://github.com/jbosstm/quickstart/tree/master/ArjunaJTS/jta > It has never changed since the initial commit: > {quote} > commit caabc37803bac12e47f4986baca21f9052e14abc > Author: Tom Jenkinson > Date: Tue Oct 2 11:05:51 2012 +0100 > Initial version of a performance comparitor for jts and jta > {quote} > This artefact needs deleting. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 06:53:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 06:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2913) Make the SPI a true dependency of standalone narayana-jta pom.xml In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538748#comment-13538748 ] Ondra Chaloupka commented on JBTM-2913: --------------------------------------- hi [~tomjenkinson], checking jiras for the 5.8.0.Final release. As I can see PRs being merged, do you think this is fixed and could be marked as resolved with the appropriate fix version? > Make the SPI a true dependency of standalone narayana-jta pom.xml > ----------------------------------------------------------------- > > Key: JBTM-2913 > URL: https://issues.jboss.org/browse/JBTM-2913 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > This means that users can simply import the narayana-jta dependency rather than both it and the SPI. > It is useful when being consumed by jbpm for example. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 06:55:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 06:55:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2880) Refactor codebase to minimize usage of e.printStackTrace() call and change for using logger In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2880: ---------------------------------- Fix Version/s: 5.later (was: 5.next) > Refactor codebase to minimize usage of e.printStackTrace() call and change for using logger > ------------------------------------------------------------------------------------------- > > Key: JBTM-2880 > URL: https://issues.jboss.org/browse/JBTM-2880 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Affects Versions: 5.5.6.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.later > > > The code base uses call `e.printStackTrace()` on several places. That usage should be minimized and used only when it's good reason for it. In general such calls should be replaced printing with `logger`, probably in level `WARN` with some additional information, why the stacktrace is printed - what error occured - included. > By quick check these are places where exception stack trace is printed directly to `stderr`. > {code} > -vertx/shared/src/main/java/ClientVerticle.java- > -vertx/shared/src/main/java/SampleVerticle2.java- > -vertx/shared/src/main/java/SampleVerticle1.java- > osgi/jta/src/main/java/org/jboss/narayana/osgi/jta/internal/ObjStoreBrowserImpl.java > XTS/WSAS/classes/com/arjuna/mwlabs/wsas/UserActivityImple.java > XTS/WSAS/classes/com/arjuna/mwlabs/wsas/activity/ActivityHandleImple.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf11/model/sagas/arjunacore/SagasHLSImple.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf11/model/twophase/arjunacore/TwoPhaseHLSImple.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf/model/sagas/arjunacore/ParticipantRecord.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf/model/sagas/arjunacore/CoordinatorControl.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf/model/twophase/arjunacore/ParticipantRecord.java > XTS/WSCF/classes/com/arjuna/mwlabs/wscf/model/twophase/arjunacore/CoordinatorControl.java > XTS/WSCF/classes/com/arjuna/mw/wscf/utils/DomUtil.java > XTS/WSCF/classes/com/arjuna/mw/wscf/protocols/ProtocolManager.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/RegistrarImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/context/ArjunaContextImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/remote/TransactionManagerImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/remote/UserTransactionImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/remote/UserTransactionStandaloneImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/participants/CleanupSynchronization.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/at/ContextFactoryImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/context/ArjunaContextImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/remote/UserBusinessActivityImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/remote/BusinessActivityManagerImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/remote/BAParticipantManagerImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/remote/UserBusinessActivityStandaloneImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/participants/CleanupSynchronization.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst11/ba/ContextFactoryImple.java > XTS/WSTX/classes/com/arjuna/mwlabs/wst/at/participants/DurableTwoPhaseCommitParticipant.java > XTS/localjunit/WSTX11-interop/src/main/java/com/jboss/transaction/txinterop/proxy/ProxyListenerService.java > XTS/localjunit/WSTFSC07-interop/src/main/java/com/jboss/transaction/wstf/proxy/ProxyListenerService.java > XTS/WS-T/dev/src/com/arjuna/schemas/ws/_2005/_10/wsarjtx/TerminationCoordinatorRPCService.java > XTS/WS-T/dev/src/com/arjuna/wst11/stub/CompletionStub.java > XTS/WS-T/dev/src/com/arjuna/wst11/stub/CompletionRPCStub.java > XTS/WS-T/dev/src/com/arjuna/wst11/stub/BusinessActivityTerminatorRPCStub.java > XTS/WS-T/dev/src/com/arjuna/wst11/messaging/TerminationCoordinatorRPCProcessorImpl.java > XTS/WS-T/dev/src/com/arjuna/wst11/messaging/CompletionCoordinatorProcessorImpl.java > XTS/WS-T/dev/src/com/arjuna/wst11/messaging/CompletionCoordinatorRPCProcessorImpl.java > XTS/WS-T/dev/src/com/arjuna/wst11/messaging/TerminationCoordinatorProcessorImpl.java > XTS/WS-C/dev/src/com/arjuna/wsc11/messaging/ActivationCoordinatorProcessorImpl.java > XTS/WS-C/dev/src/com/arjuna/wsc11/messaging/RegistrationCoordinatorProcessorImpl.java > XTS/WS-C/dev/src/com/arjuna/webservices/SoapFault.java > ArjunaJTA/jta/classes/com/arjuna/ats/jta/xa/XidImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/jca/XATerminatorImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/jca/TransactionImporterImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/TransactionImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/subordinate/TransactionImple.java > ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/SubordinateJTAXAResourceOrphanFilter.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/DirectRecoverableConnection.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/ConnectionManager.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/ProvidedXADataSourceConnection.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/IndirectRecoverableConnection.java > ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/recovery/JDBCXARecovery.java > blacktie/utils/cpp-plugin/src/main/java/org/jboss/narayana/blacktie/plugins/AddCommonSources.java > blacktie/jatmibroker-xatmi/src/main/java/org/jboss/narayana/blacktie/jatmibroker/core/server/SocketServer.java > blacktie/wildfly-blacktie/subsystem/src/main/java/org/codehaus/stomp/jms/ProtocolConverter.java > blacktie/blacktie-admin-services/src/main/java/org/jboss/narayana/blacktie/administration/core/AdministrationProxy.java > tools/src/main/java/io/narayana/perf/Measurement.java > rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java > rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java > txframework/src/main/java/org/jboss/narayana/txframework/impl/Participant.java > compensations/src/main/java/org/jboss/narayana/compensations/internal/ParticipantInterceptor.java > compensations/src/main/java/org/jboss/narayana/compensations/internal/ParticipantImpl.java > ArjunaCore/arjuna/services/classes/com/arjuna/ats/arjuna/services/recovery/RecoveryManagerService.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/utils/AndroidProcessId.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/abstractrecords/CadaverRecord.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/ShadowingStore.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/CacheStore.java > ArjunaCore/arjuna/classes/com/arjuna/ats/internal/arjuna/objectstore/LogStore.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/AbstractRecord.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/BasicAction.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/common/ObjectStoreEnvironmentBean.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/log/LogBrowser.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/stats/TxPerfGraph.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/OTM.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/StateManager.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/recovery/RecoveryManager.java > ArjunaJTS/integration/src/main/java/com/arjuna/ats/internal/jbossatx/jta/jca/XATerminator.java > ArjunaJTS/integration/src/main/java/com/arjuna/ats/internal/jbossatx/jts/jca/XATerminator.java > ArjunaJTS/integration/src/main/java/com/arjuna/ats/internal/jbossatx/jts/PropagationContextManager.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/jca/XATerminatorImple.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/BaseTransaction.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/subordinate/jca/coordinator/ServerTransaction.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/subordinate/jca/SubordinateAtomicTransaction.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/subordinate/TransactionImple.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/subordinate/SubordinateAtomicTransaction.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/resources/jts/orbspecific/XAResourceRecord.java > ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/recovery/jts/JCAServerTransactionRecoveryModule.java > ArjunaJTS/orbportability/classes/com/arjuna/orbportability/common/ant/IDLCompiler.java > ArjunaJTS/jts/services/classes/com/arjuna/ats/jts/services/transactionserver/TransactionServerService.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/utils/TxStoreLog.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/interposition/ServerControl.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/coordinator/ArjunaTransactionImple.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/jacorb/recoverycoordinators/ORBRunner.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/jacorb/recoverycoordinators/JacOrbRCServiceInit.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/ibmorb/recoverycoordinators/ORBRunner.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/javaidl/recoverycoordinators/ORBRunner.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/CurrentImple.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/TransactionFactoryImple.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/recovery/RecoveryEnablement.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/context/ContextManager.java > ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/resources/ExtendedResourceRecord.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/TransactionServer.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/orbspecific/jacorb/interceptors/interposition/InterpositionClientRequestInterceptorImpl.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/orbspecific/jacorb/interceptors/context/ContextServerRequestInterceptorImpl.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/orbspecific/ibmorb/interceptors/context/ContextServerRequestInterceptorImpl.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/orbspecific/javaidl/interceptors/context/ContextServerRequestInterceptorImpl.java > ArjunaJTS/jts/classes/com/arjuna/ats/jts/ExplicitInterposition.java > STM/src/main/java/org/jboss/stm/internal/reflect/InvocationHandler.java > STM/src/main/java/org/jboss/stm/internal/proxy/OptimisticLockManagerProxy.java > STM/src/main/java/org/jboss/stm/internal/proxy/LockManagerProxy.java > STM/src/main/java/org/jboss/stm/internal/optimistic/OptimisticLockRecord.java > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 06:58:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 06:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2969) Make the CDI checker a standalone tool or/and mvn plugin In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2969: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.8.0.Final Resolution: Done > Make the CDI checker a standalone tool or/and mvn plugin > -------------------------------------------------------- > > Key: JBTM-2969 > URL: https://issues.jboss.org/browse/JBTM-2969 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 5.8.0.Final > > > The way how the checker works now (as CDI extension, needed to be packed inside of the app) is not a good approach and it should work as a standalone tool or better as a maven plugin to verify the annotation in a defined phase. > The current approach needs to be reworked. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 06:58:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 06:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2969) Make the CDI checker a standalone tool or/and mvn plugin In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka closed JBTM-2969. --------------------------------- > Make the CDI checker a standalone tool or/and mvn plugin > -------------------------------------------------------- > > Key: JBTM-2969 > URL: https://issues.jboss.org/browse/JBTM-2969 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 5.8.0.Final > > > The way how the checker works now (as CDI extension, needed to be packed inside of the app) is not a good approach and it should work as a standalone tool or better as a maven plugin to verify the annotation in a defined phase. > The current approach needs to be reworked. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 06:58:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 06:58:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2994) TransactionExtension uses old version of addAnnotatedType which results in warnings being logged In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka closed JBTM-2994. --------------------------------- > TransactionExtension uses old version of addAnnotatedType which results in warnings being logged > ------------------------------------------------------------------------------------------------ > > Key: JBTM-2994 > URL: https://issues.jboss.org/browse/JBTM-2994 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.7.2.Final > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 5.8.0.Final > > > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorMandatory is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNever is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorNotSupported is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequiresNew is deprecated from CDI 1.1! > 2018-02-16 15:25:58,896 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-4) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) used for class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorSupports is deprecated from CDI 1.1! -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 06:59:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 06:59:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2990) ThreadUtil performance improvement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2990: ---------------------------------- Fix Version/s: 5.8.0.Final > ThreadUtil performance improvement > ---------------------------------- > > Key: JBTM-2990 > URL: https://issues.jboss.org/browse/JBTM-2990 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.7.2.Final > Reporter: Jonathan Halliday > Assignee: Jonathan Halliday > Priority: Minor > Fix For: 5.8.0.Final > > > The ThreadUtil changes introduced for the bug fix under JBTM-2673, cause lock contention on the static WeakHashMap under high load. > The proposed fix is to partially reintroduce the earlier behavior of caching the value in a ThreadLocal, since the dominant use case is pooled threads repeatedly looking up their own identity. The global lookup capability introduced for the fix remains necessary for less common use cases, but the locking can be taken off the critical path for most workloads. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 06:59:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 06:59:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2990) ThreadUtil performance improvement In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2990: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ThreadUtil performance improvement > ---------------------------------- > > Key: JBTM-2990 > URL: https://issues.jboss.org/browse/JBTM-2990 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.7.2.Final > Reporter: Jonathan Halliday > Assignee: Jonathan Halliday > Priority: Minor > Fix For: 5.8.0.Final > > > The ThreadUtil changes introduced for the bug fix under JBTM-2673, cause lock contention on the static WeakHashMap under high load. > The proposed fix is to partially reintroduce the earlier behavior of caching the value in a ThreadLocal, since the dominant use case is pooled threads repeatedly looking up their own identity. The global lookup capability introduced for the fix remains necessary for less common use cases, but the locking can be taken off the critical path for most workloads. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 06:59:02 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 06:59:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2987) Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2987: ---------------------------------- Fix Version/s: 5.8.0.Final > Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager > -------------------------------------------------------------------------------------- > > Key: JBTM-2987 > URL: https://issues.jboss.org/browse/JBTM-2987 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Affects Versions: 5.7.2.Final > Reporter: Alon Greenland > Fix For: 5.8.0.Final > > > As discussed in https://developer.jboss.org/thread/266729, when Recovery Manager executes xaResource.rollback(xid), if it receives error code XAER_NOTA it is not really an error or warning. > Currently it is logged as warning. It can be logged with debug level instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 07:00:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 07:00:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2987) Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2987: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Don't treat XAER_NOTA return code as warning when doing rollback from Recovery Manager > -------------------------------------------------------------------------------------- > > Key: JBTM-2987 > URL: https://issues.jboss.org/browse/JBTM-2987 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Affects Versions: 5.7.2.Final > Reporter: Alon Greenland > Fix For: 5.8.0.Final > > > As discussed in https://developer.jboss.org/thread/266729, when Recovery Manager executes xaResource.rollback(xid), if it receives error code XAER_NOTA it is not really an error or warning. > Currently it is logged as warning. It can be logged with debug level instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 07:06:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 07:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2925) TM jdbc driver list should be enriched with driver name for DB2 driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2925: ---------------------------------- Fix Version/s: 5.7.0.Final > TM jdbc driver list should be enriched with driver name for DB2 driver > ---------------------------------------------------------------------- > > Key: JBTM-2925 > URL: https://issues.jboss.org/browse/JBTM-2925 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Affects Versions: 5.6.4.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.7.0.Final > > > The list of the "supported" jdbc driver names should be enhanced with DB2 driver name which is {{IBM Data Server Driver for JDBC and SQLJ}}. > In case the need to verify the connection metadata you can try to check small tool here > https://github.com/ochaloup/jdbc-driver-load -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 07:06:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 07:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2925) TM jdbc driver list should be enriched with driver name for DB2 driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2925: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TM jdbc driver list should be enriched with driver name for DB2 driver > ---------------------------------------------------------------------- > > Key: JBTM-2925 > URL: https://issues.jboss.org/browse/JBTM-2925 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Affects Versions: 5.6.4.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.7.0.Final > > > The list of the "supported" jdbc driver names should be enhanced with DB2 driver name which is {{IBM Data Server Driver for JDBC and SQLJ}}. > In case the need to verify the connection metadata you can try to check small tool here > https://github.com/ochaloup/jdbc-driver-load -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 07:06:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 07:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2925) TM jdbc driver list should be enriched with driver name for DB2 driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka closed JBTM-2925. --------------------------------- > TM jdbc driver list should be enriched with driver name for DB2 driver > ---------------------------------------------------------------------- > > Key: JBTM-2925 > URL: https://issues.jboss.org/browse/JBTM-2925 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Affects Versions: 5.6.4.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.7.0.Final > > > The list of the "supported" jdbc driver names should be enhanced with DB2 driver name which is {{IBM Data Server Driver for JDBC and SQLJ}}. > In case the need to verify the connection metadata you can try to check small tool here > https://github.com/ochaloup/jdbc-driver-load -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 07:08:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 07:08:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2988) Update activemq-artemis in the performance repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538760#comment-13538760 ] Ondra Chaloupka commented on JBTM-2988: --------------------------------------- hi [~mmusgrov], checking jiras for the 5.8.0.Final release. As I can see PRs being merged, do you think this is fixed and could be marked as resolved with the appropriate fix version? > Update activemq-artemis in the performance repo > ----------------------------------------------- > > Key: JBTM-2988 > URL: https://issues.jboss.org/browse/JBTM-2988 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > Make sure that the artemis dependency in the performance repo matches what we use on master. So we are currently on 1.5.5.jbossorg-008 so change in the pom in our performance repo to use this version. > Important: make sure that we also *replace* the native AIO library which is located in ArjunaJTA/jta/etc -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 07:08:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 07:08:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2621) Tests that rely on the old perf benchmark harness need porting to use JMH In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538761#comment-13538761 ] Ondra Chaloupka commented on JBTM-2621: --------------------------------------- hi [~mmusgrov], checking jiras for the 5.8.0.Final release. As I can see PRs being merged, do you think this is fixed and could be marked as resolved with the appropriate fix version? > Tests that rely on the old perf benchmark harness need porting to use JMH > ------------------------------------------------------------------------- > > Key: JBTM-2621 > URL: https://issues.jboss.org/browse/JBTM-2621 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > The relevant tests are: > com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance1 > com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 > com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance3 > if there are no others then once ported the old performance benchmark harness can be removed. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 07:10:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 07:10:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2991) Deprecate old StartXAResource interface In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2991: ---------------------------------- Fix Version/s: 5.8.0.Final > Deprecate old StartXAResource interface > --------------------------------------- > > Key: JBTM-2991 > URL: https://issues.jboss.org/browse/JBTM-2991 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > Fix For: 5.8.0.Final > > > All support for this was moved to org.jboss.tm.FirstResource in the SPI -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 07:10:01 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 07:10:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2991) Deprecate old StartXAResource interface In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2991: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Deprecate old StartXAResource interface > --------------------------------------- > > Key: JBTM-2991 > URL: https://issues.jboss.org/browse/JBTM-2991 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Reporter: Tom Jenkinson > Fix For: 5.8.0.Final > > > All support for this was moved to org.jboss.tm.FirstResource in the SPI -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Tue Feb 27 09:39:00 2018 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 27 Feb 2018 09:39:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #76 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Ondra Chaloupka > Fix For: 5.next > > Attachments: surefire.jstack.23019.txt, wfly.jstack.txt > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Feb 28 03:28:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 28 Feb 2018 03:28:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2989) Replace to use the DBCP2 in the spring quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539325#comment-13539325 ] Amos Feng commented on JBTM-2989: --------------------------------- yeah, I think it can be resolved. > Replace to use the DBCP2 in the spring quickstarts > -------------------------------------------------- > > Key: JBTM-2989 > URL: https://issues.jboss.org/browse/JBTM-2989 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.8.0.Final > > > It could be helpful to replace the transational driver when using with the spring. The transactional driver might be only used in the standalone. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Feb 28 03:28:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 28 Feb 2018 03:28:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2989) Replace to use the DBCP2 in the spring quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2989: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Replace to use the DBCP2 in the spring quickstarts > -------------------------------------------------- > > Key: JBTM-2989 > URL: https://issues.jboss.org/browse/JBTM-2989 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.8.0.Final > > > It could be helpful to replace the transational driver when using with the spring. The transactional driver might be only used in the standalone. -- This message was sent by Atlassian JIRA (v7.5.0#75005) From issues at jboss.org Wed Feb 28 03:28:00 2018 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 28 Feb 2018 03:28:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2989) Replace to use the DBCP2 in the spring quickstarts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2989: ---------------------------- Fix Version/s: 5.8.0.Final (was: 5.next) > Replace to use the DBCP2 in the spring quickstarts > -------------------------------------------------- > > Key: JBTM-2989 > URL: https://issues.jboss.org/browse/JBTM-2989 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.8.0.Final > > > It could be helpful to replace the transational driver when using with the spring. The transactional driver might be only used in the standalone. -- This message was sent by Atlassian JIRA (v7.5.0#75005)