From issues at jboss.org Tue May 2 11:39:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 2 May 2017 11:39:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2892) Calling Subordinate transaction to enlist with empty parameter list ends with IndexOutOfBoundsException In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-2892: ------------------------------------- Summary: Calling Subordinate transaction to enlist with empty parameter list ends with IndexOutOfBoundsException Key: JBTM-2892 URL: https://issues.jboss.org/browse/JBTM-2892 Project: JBoss Transaction Manager Issue Type: Bug Components: JTS Affects Versions: 5.5.24.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Priority: Minor When calling enlist method on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple}} when parameters are defined as empty array the {{IndexOutOfBoundsException}} exception is thrown. The method call I do refer to is https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L517 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 2 12:14:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 2 May 2017 12:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2892) Calling Subordinate transaction to enlist with empty parameter list ends with IndexOutOfBoundsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1173 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Calling Subordinate transaction to enlist with empty parameter list ends with IndexOutOfBoundsException > ------------------------------------------------------------------------------------------------------- > > Key: JBTM-2892 > URL: https://issues.jboss.org/browse/JBTM-2892 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > When calling enlist method on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple}} when parameters are defined as empty array the {{IndexOutOfBoundsException}} exception is thrown. > The method call I do refer to is > https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L517 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 2 12:25:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 2 May 2017 12:25:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2893) JTS subordinate transaction could check Xid format during enlistment to allow it being edited In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-2893: ------------------------------------- Summary: JTS subordinate transaction could check Xid format during enlistment to allow it being edited Key: JBTM-2893 URL: https://issues.jboss.org/browse/JBTM-2893 Project: JBoss Transaction Manager Issue Type: Enhancement Components: JTS Affects Versions: 5.5.24.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka When a subordinate transaction created by Narayana is imported in JTS it's capable to correctly handle only one XAResource being enlisted. When two or more resources are enlisted they all contain the same Xid. That Xid came from what {{TransactionImple}} defines (here is call which is never reached by such txn code: https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3a39e3bc9/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L1760) That behavior is fine when txn is imported from EIS but when is managed by Narayana it should not be problem to generate Xids for each XAResource unique. That behavior makes the issue when recovery should be part of handling. All the resources are "merged" under one record in object log store. That way can't be recovered correctly. This handling is "fixed" in JTA (see https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3a39e3bc9/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/subordinate/TransactionImple.java#L359) where format of xid is checked when enlistment happens. Such thing could be passed to JTS mode too. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 3 11:25:01 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 3 May 2017 11:25:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1174 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 5.later > > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 4 05:54:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 4 May 2017 05:54:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2894) Need to add Javadocs for REST-AT utils (e.g. TxSupport) In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2894: ----------------------------------- Summary: Need to add Javadocs for REST-AT utils (e.g. TxSupport) Key: JBTM-2894 URL: https://issues.jboss.org/browse/JBTM-2894 Project: JBoss Transaction Manager Issue Type: Bug Components: Documentation, REST Reporter: Tom Jenkinson Assignee: Michael Musgrove Priority: Minor This class is not in the Javadocs for Narayana: https://github.com/jbosstm/narayana/blob/master/rts/at/util/src/main/java/org/jboss/jbossts/star/util/TxSupport.java Javadocs over here: http://narayana.io//docs/api/index.html -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 4 05:54:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 4 May 2017 05:54:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2894) Need to add Javadocs for REST-AT utils (e.g. TxSupport) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2894: -------------------------------- Issue Type: Task (was: Bug) > Need to add Javadocs for REST-AT utils (e.g. TxSupport) > ------------------------------------------------------- > > Key: JBTM-2894 > URL: https://issues.jboss.org/browse/JBTM-2894 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation, REST > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > > This class is not in the Javadocs for Narayana: > https://github.com/jbosstm/narayana/blob/master/rts/at/util/src/main/java/org/jboss/jbossts/star/util/TxSupport.java > Javadocs over here: > http://narayana.io//docs/api/index.html -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 4 08:12:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Thu, 4 May 2017 08:12:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2124) Add orphan detection for JTS interposition mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2124: ---------------------------------- Forum Reference: https://developer.jboss.org/message/971565 > Add orphan detection for JTS interposition mode > ----------------------------------------------- > > Key: JBTM-2124 > URL: https://issues.jboss.org/browse/JBTM-2124 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 4.17.17 > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 5.later > > > Currently orphan detection is supported for JTA, not for JTS. Please, add the suport for JTS as well. > The following scenario for JTS causes that the orphan is left in the transaction log store and the prepared resource could held the lock till the time that it's timeouted on the side of the database/jms. > The program flow is following (test run on EAP 6) > enlisting jms xaresource to transaction > sending msg to queue > enlisting xa test resource > preparing jms xaresource > preparing xa test resource > crash JVM at the end of the test XAResource.prepare() > restart app server and recovery is run > During recovery the jms resource is processed correctly because TM found some info in its jts logs. But such info was not saved for test xa resource. The test xa is not rollback. > More info and discussion could be found at: https://bugzilla.redhat.com/show_bug.cgi?id=1064170 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 5 05:41:01 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 5 May 2017 05:41:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2881) STM InvocationHandler swallows application exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #1175 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > STM InvocationHandler swallows application exceptions > ----------------------------------------------------- > > Key: JBTM-2881 > URL: https://issues.jboss.org/browse/JBTM-2881 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.5.6.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The STM implementation intercepts calls on transactional objects (ones that implement interfaces marked with the @Transactional annotation). If the application object throws a business exception it is wrapped in an java.lang.reflect.InvocationTargetException and this is raised. Application code is written to anticipate business exceptions but not java.lang.reflect.InvocationTargetException. > The fix is throw the wrapped business exception instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 5 10:17:00 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 5 May 2017 10:17:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2881) STM InvocationHandler swallows application exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2881: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > STM InvocationHandler swallows application exceptions > ----------------------------------------------------- > > Key: JBTM-2881 > URL: https://issues.jboss.org/browse/JBTM-2881 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.5.6.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The STM implementation intercepts calls on transactional objects (ones that implement interfaces marked with the @Transactional annotation). If the application object throws a business exception it is wrapped in an java.lang.reflect.InvocationTargetException and this is raised. Application code is written to anticipate business exceptions but not java.lang.reflect.InvocationTargetException. > The fix is throw the wrapped business exception instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 8 03:07:00 2017 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 8 May 2017 03:07:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2895) Upgrade the spring-boot framework version of the quickstart In-Reply-To: References: Message-ID: Amos Feng created JBTM-2895: ------------------------------- Summary: Upgrade the spring-boot framework version of the quickstart Key: JBTM-2895 URL: https://issues.jboss.org/browse/JBTM-2895 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator Reporter: Amos Feng Assignee: Amos Feng The current GA release of spring boot is 1.5.3.RELEASE -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 8 03:16:00 2017 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 8 May 2017 03:16:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2895) Upgrade the spring-boot framework version of the quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Amos Feng created pull request #193 in GitHub --------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade the spring-boot framework version of the quickstart > ----------------------------------------------------------- > > Key: JBTM-2895 > URL: https://issues.jboss.org/browse/JBTM-2895 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > > The current GA release of spring boot is 1.5.3.RELEASE -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 8 10:36:02 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 8 May 2017 10:36:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2896) Invalid warning when committing STM optimistic records In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2896: -------------------------------------- Summary: Invalid warning when committing STM optimistic records Key: JBTM-2896 URL: https://issues.jboss.org/browse/JBTM-2896 Project: JBoss Transaction Manager Issue Type: Bug Components: STM Affects Versions: 5.5.24.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next There is some code in OptimisticLockRecord#topLevelCommit that generates an invalid warning bq. WARN: ARJUNA015051: OptimisticLockRecord.topLevelCommit state check failed for org.jboss.stm.internal.proxy.OptimisticLockManagerProxy at 7f058cfa will force rollback. when in fact there is no rollback. The offending code is: {code} public int topLevelCommit () { boolean stateOK = checkState(); if (stateOK) { txojLogger.i18NLogger.warn_OptimisticLockRecord_2((LockManager) value()); } {code} The condition was intended to be if (!stateOK) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 8 10:40:00 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 8 May 2017 10:40:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2896) Invalid warning when committing STM optimistic records In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #1177 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Invalid warning when committing STM optimistic records > ------------------------------------------------------ > > Key: JBTM-2896 > URL: https://issues.jboss.org/browse/JBTM-2896 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.5.24.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > There is some code in OptimisticLockRecord#topLevelCommit that generates an invalid warning > bq. WARN: ARJUNA015051: OptimisticLockRecord.topLevelCommit state check failed for org.jboss.stm.internal.proxy.OptimisticLockManagerProxy at 7f058cfa will force rollback. > when in fact there is no rollback. The offending code is: > {code} > public int topLevelCommit () > { > boolean stateOK = checkState(); > > if (stateOK) > { > txojLogger.i18NLogger.warn_OptimisticLockRecord_2((LockManager) value()); > } > {code} > The condition was intended to be if (!stateOK) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 10 05:02:00 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 10 May 2017 05:02:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2889) Include a vertx with STM quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #194 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Include a vertx with STM quickstart > ----------------------------------- > > Key: JBTM-2889 > URL: https://issues.jboss.org/browse/JBTM-2889 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, STM > Affects Versions: 5.5.24.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > It would be useful to include a quickstart that shows how to use STM with vertx -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 10 11:36:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 10 May 2017 11:36:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2897) Calling jts TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled In-Reply-To: References: Message-ID: Ondra Chaloupka created JBTM-2897: ------------------------------------- Summary: Calling jts TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled Key: JBTM-2897 URL: https://issues.jboss.org/browse/JBTM-2897 Project: JBoss Transaction Manager Issue Type: Bug Components: JTS Affects Versions: 5.5.24.Final Reporter: Ondra Chaloupka Assignee: Ondra Chaloupka Priority: Minor If trace logging is enabled then call on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple#registerSynchronization}} is done with {{null}} in parameter then {{NullPointerException}} is thrown but {{SystemException}} should be thrown in such case. https://github.com/jbosstm/narayana/blob/930bd7f17f1b0cc2b8529eaa2ae1fcacf9582ac5/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L452 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 10 11:43:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 10 May 2017 11:43:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2897) Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2897: ---------------------------------- Summary: Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled (was: Calling jts TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled) > Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2897 > URL: https://issues.jboss.org/browse/JBTM-2897 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > If trace logging is enabled then call on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple#registerSynchronization}} is done with {{null}} in parameter then {{NullPointerException}} is thrown but {{SystemException}} should be thrown in such case. > https://github.com/jbosstm/narayana/blob/930bd7f17f1b0cc2b8529eaa2ae1fcacf9582ac5/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L452 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 10 11:47:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 10 May 2017 11:47:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2893) JTS subordinate transaction could check Xid format during enlistment to allow it being edited In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1178 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > JTS subordinate transaction could check Xid format during enlistment to allow it being edited > --------------------------------------------------------------------------------------------- > > Key: JBTM-2893 > URL: https://issues.jboss.org/browse/JBTM-2893 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > When a subordinate transaction created by Narayana is imported in JTS it's capable to correctly handle only one XAResource being enlisted. When two or more resources are enlisted they all contain the same Xid. That Xid came from what {{TransactionImple}} defines (here is call which is never reached by such txn code: https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3a39e3bc9/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L1760) > That behavior is fine when txn is imported from EIS but when is managed by Narayana it should not be problem to generate Xids for each XAResource unique. > That behavior makes the issue when recovery should be part of handling. All the resources are "merged" under one record in object log store. That way can't be recovered correctly. > This handling is "fixed" in JTA (see https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3a39e3bc9/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/subordinate/TransactionImple.java#L359) where format of xid is checked when enlistment happens. Such thing could be passed to JTS mode too. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 10 11:49:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Wed, 10 May 2017 11:49:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2897) Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1179 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2897 > URL: https://issues.jboss.org/browse/JBTM-2897 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > If trace logging is enabled then call on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple#registerSynchronization}} is done with {{null}} in parameter then {{NullPointerException}} is thrown but {{SystemException}} should be thrown in such case. > https://github.com/jbosstm/narayana/blob/930bd7f17f1b0cc2b8529eaa2ae1fcacf9582ac5/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L452 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 12 16:51:00 2017 From: issues at jboss.org (Mark Little (JIRA)) Date: Fri, 12 May 2017 16:51:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2898) Consider Java 9 alternatives to reflection for STM In-Reply-To: References: Message-ID: Mark Little created JBTM-2898: --------------------------------- Summary: Consider Java 9 alternatives to reflection for STM Key: JBTM-2898 URL: https://issues.jboss.org/browse/JBTM-2898 Project: JBoss Transaction Manager Issue Type: Feature Request Components: STM Reporter: Mark Little Assignee: Mark Little -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 17 06:27:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 17 May 2017 06:27:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2760) SPI to check if JTA or JTS transaction is active during graceful shutdown In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407614#comment-13407614 ] Tom Jenkinson commented on JBTM-2760: ------------------------------------- Link to the code at the time of Gytis' comments: https://github.com/jbosstm/jboss-transaction-spi/blob/efe7825ec9780b06877801ffa7ff69e922d1418d/src/main/java/org/jboss/tm/ExtendedJBossXATerminator.java#L67 > SPI to check if JTA or JTS transaction is active during graceful shutdown > ------------------------------------------------------------------------- > > Key: JBTM-2760 > URL: https://issues.jboss.org/browse/JBTM-2760 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > > During graceful shutdown EJB subsystem should check with transaction subsystem if request should be allowed in. Only requests participating in an existing transaction are permitted. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 17 13:33:02 2017 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 17 May 2017 13:33:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2870) Provide way of getting suppressed exceptions out of SubordinateTransaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407894#comment-13407894 ] RH Bugzilla Integration commented on JBTM-2870: ----------------------------------------------- Radovan STANCEL changed the Status of [bug 1435549|https://bugzilla.redhat.com/show_bug.cgi?id=1435549] from POST to MODIFIED > Provide way of getting suppressed exceptions out of SubordinateTransaction > -------------------------------------------------------------------------- > > Key: JBTM-2870 > URL: https://issues.jboss.org/browse/JBTM-2870 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 4.17.38, 5.5.5.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 4.17.40, 5.2.23.Final, 5.5.7.Final, 5.next > > > We need to provide way how to pass suppressed exceptions of of the `SubordinateTransaction` to the caller. > This request came from customer case and https://bugzilla.redhat.com/show_bug.cgi?id=1435549 as we need to provide exceptions thrown from transaction resource. > The interface is used for controlling propagated transaction from one server to another in EAP/WFLY. > Callers are is ejb3 subsystem in EAP 6.4/7.0 and WFTC in EAP 7.1. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Thu May 18 09:43:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 18 May 2017 09:43:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2766) Implement pooling for transactional driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #1180 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Implement pooling for transactional driver > ------------------------------------------ > > Key: JBTM-2766 > URL: https://issues.jboss.org/browse/JBTM-2766 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > > Transactional driver does not provide connection pooling. We should either implement it ourselves or find a third party implementation. In case of the second option we should test it and provide a demonstration and blog post of its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 19 05:21:00 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 19 May 2017 05:21:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1488) Implement the REST-JDI specification In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-1488 started by Michael Musgrove. ---------------------------------------------- > Implement the REST-JDI specification > ------------------------------------ > > Key: JBTM-1488 > URL: https://issues.jboss.org/browse/JBTM-1488 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: REST > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Labels: student > Fix For: 6.later > > > https://community.jboss.org/wiki/CompensatingRESTfulTransactions/ -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 19 05:41:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 19 May 2017 05:41:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2766) Allow Transactional Driver to be used with commons-dbcp in Tomcat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2766: -------------------------------- Summary: Allow Transactional Driver to be used with commons-dbcp in Tomcat (was: Implement pooling for transactional driver) > Allow Transactional Driver to be used with commons-dbcp in Tomcat > ----------------------------------------------------------------- > > Key: JBTM-2766 > URL: https://issues.jboss.org/browse/JBTM-2766 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > > Transactional driver does not provide connection pooling. We should either implement it ourselves or find a third party implementation. In case of the second option we should test it and provide a demonstration and blog post of its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Fri May 19 05:42:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 19 May 2017 05:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2766) Allow Transactional Driver to be used with commons-dbcp in Tomcat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2766: -------------------------------- Description: Transactional driver does not provide connection pooling but commons-dbcp (as used in Tomcat) does. We should test it and provide a demonstration and blog post of its usage. (was: Transactional driver does not provide connection pooling. We should either implement it ourselves or find a third party implementation. In case of the second option we should test it and provide a demonstration and blog post of its usage.) > Allow Transactional Driver to be used with commons-dbcp in Tomcat > ----------------------------------------------------------------- > > Key: JBTM-2766 > URL: https://issues.jboss.org/browse/JBTM-2766 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > > Transactional driver does not provide connection pooling but commons-dbcp (as used in Tomcat) does. We should test it and provide a demonstration and blog post of its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Mon May 22 07:19:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 22 May 2017 07:19:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2899) Consider independently versioning the quickstarts In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2899: ----------------------------------- Summary: Consider independently versioning the quickstarts Key: JBTM-2899 URL: https://issues.jboss.org/browse/JBTM-2899 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator Reporter: Tom Jenkinson It would be clearer to know when an individual quickstart has changed. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 06:14:00 2017 From: issues at jboss.org (Ondra Chaloupka (JIRA)) Date: Tue, 23 May 2017 06:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2893) JTS subordinate transaction could check Xid format during enlistment to allow it being edited In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondra Chaloupka updated JBTM-2893: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JTS subordinate transaction could check Xid format during enlistment to allow it being edited > --------------------------------------------------------------------------------------------- > > Key: JBTM-2893 > URL: https://issues.jboss.org/browse/JBTM-2893 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > When a subordinate transaction created by Narayana is imported in JTS it's capable to correctly handle only one XAResource being enlisted. When two or more resources are enlisted they all contain the same Xid. That Xid came from what {{TransactionImple}} defines (here is call which is never reached by such txn code: https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3a39e3bc9/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L1760) > That behavior is fine when txn is imported from EIS but when is managed by Narayana it should not be problem to generate Xids for each XAResource unique. > That behavior makes the issue when recovery should be part of handling. All the resources are "merged" under one record in object log store. That way can't be recovered correctly. > This handling is "fixed" in JTA (see https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3a39e3bc9/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/subordinate/TransactionImple.java#L359) where format of xid is checked when enlistment happens. Such thing could be passed to JTS mode too. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 06:53:00 2017 From: issues at jboss.org (Ivan Straka (JIRA)) Date: Tue, 23 May 2017 06:53:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2900) Byteman fails to start on IBM JDK (quickstart) In-Reply-To: References: Message-ID: Ivan Straka created JBTM-2900: --------------------------------- Summary: Byteman fails to start on IBM JDK (quickstart) Key: JBTM-2900 URL: https://issues.jboss.org/browse/JBTM-2900 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 5.5.24.Final Reporter: Ivan Straka Assignee: Ivan Straka Priority: Minor Byteman fails to start on IBM JDK for jta-and-hibernate-standalone quickstart. output: {code:java} Running org.jboss.narayana.quickstart.jta.TestCase byteman jar is /home/hudson/.m2/repository/org/jboss/byteman/byteman/3.0.3/byteman-3.0.3.jar *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 Setting org.jboss.byteman.allow.config.update=true java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:508) at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:408) at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:433) at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibraryImpl(Native Method) at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibrary(Attachment.java:309) at com.ibm.tools.attach.javaSE.Attachment.parseLoadAgent(Attachment.java:287) at com.ibm.tools.attach.javaSE.Attachment.doCommand(Attachment.java:168) at com.ibm.tools.attach.javaSE.Attachment.run(Attachment.java:128) Caused by: java.lang.UnsupportedOperationException: adding retransformable transformers is not supported in this environment at sun.instrument.InstrumentationImpl.addTransformer(InstrumentationImpl.java:100) Exception in thread "Attachment 45368" Agent failed to start! at org.jboss.byteman.agent.Main.premain(Main.java:275) at org.jboss.byteman.agent.Main.agentmain(Main.java:305) ... 11 more JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 08:01:00 2017 From: issues at jboss.org (Ivan Straka (JIRA)) Date: Tue, 23 May 2017 08:01:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2900) Byteman fails to start on IBM JDK (quickstart) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2900 started by Ivan Straka. ----------------------------------------- > Byteman fails to start on IBM JDK (quickstart) > ---------------------------------------------- > > Key: JBTM-2900 > URL: https://issues.jboss.org/browse/JBTM-2900 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.24.Final > Reporter: Ivan Straka > Assignee: Ivan Straka > Priority: Minor > > Byteman fails to start on IBM JDK for jta-and-hibernate-standalone quickstart. > output: > {code:java} > Running org.jboss.narayana.quickstart.jta.TestCase > byteman jar is /home/hudson/.m2/repository/org/jboss/byteman/byteman/3.0.3/byteman-3.0.3.jar > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Setting org.jboss.byteman.allow.config.update=true > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:508) > at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:408) > at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:433) > at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibraryImpl(Native Method) > at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibrary(Attachment.java:309) > at com.ibm.tools.attach.javaSE.Attachment.parseLoadAgent(Attachment.java:287) > at com.ibm.tools.attach.javaSE.Attachment.doCommand(Attachment.java:168) > at com.ibm.tools.attach.javaSE.Attachment.run(Attachment.java:128) > Caused by: java.lang.UnsupportedOperationException: adding retransformable transformers is not supported in this environment > at sun.instrument.InstrumentationImpl.addTransformer(InstrumentationImpl.java:100) > Exception in thread "Attachment 45368" Agent failed to start! > at org.jboss.byteman.agent.Main.premain(Main.java:275) > at org.jboss.byteman.agent.Main.agentmain(Main.java:305) > ... 11 more > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 23 08:09:00 2017 From: issues at jboss.org (Anonymous (JIRA)) Date: Tue, 23 May 2017 08:09:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2900) Byteman fails to start on IBM JDK (quickstart) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when istraka created pull request #197 in GitHub ------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Byteman fails to start on IBM JDK (quickstart) > ---------------------------------------------- > > Key: JBTM-2900 > URL: https://issues.jboss.org/browse/JBTM-2900 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.5.24.Final > Reporter: Ivan Straka > Assignee: Ivan Straka > Priority: Minor > > Byteman fails to start on IBM JDK for jta-and-hibernate-standalone quickstart. > output: > {code:java} > Running org.jboss.narayana.quickstart.jta.TestCase > byteman jar is /home/hudson/.m2/repository/org/jboss/byteman/byteman/3.0.3/byteman-3.0.3.jar > *** java.lang.instrument ASSERTION FAILED ***: "jvmtierror == JVMTI_ERROR_NOT_AVAILABLE" at JPLISAgent.c line: 1009 > Setting org.jboss.byteman.allow.config.update=true > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:508) > at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:408) > at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:433) > at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibraryImpl(Native Method) > at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibrary(Attachment.java:309) > at com.ibm.tools.attach.javaSE.Attachment.parseLoadAgent(Attachment.java:287) > at com.ibm.tools.attach.javaSE.Attachment.doCommand(Attachment.java:168) > at com.ibm.tools.attach.javaSE.Attachment.run(Attachment.java:128) > Caused by: java.lang.UnsupportedOperationException: adding retransformable transformers is not supported in this environment > at sun.instrument.InstrumentationImpl.addTransformer(InstrumentationImpl.java:100) > Exception in thread "Attachment 45368" Agent failed to start! > at org.jboss.byteman.agent.Main.premain(Main.java:275) > at org.jboss.byteman.agent.Main.agentmain(Main.java:305) > ... 11 more > JVMJ9TI064E Agent initialization function Agent_OnAttach failed for library instrument, return code 102 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:52:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:52:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2766) Allow Transactional Driver to be used with commons-dbcp in Tomcat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2766: -------------------------------- Fix Version/s: 5.next > Allow Transactional Driver to be used with commons-dbcp in Tomcat > ----------------------------------------------------------------- > > Key: JBTM-2766 > URL: https://issues.jboss.org/browse/JBTM-2766 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Transactional driver does not provide connection pooling but commons-dbcp (as used in Tomcat) does. We should test it and provide a demonstration and blog post of its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:56:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:56:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2896) Invalid warning when committing STM optimistic records In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2896: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Invalid warning when committing STM optimistic records > ------------------------------------------------------ > > Key: JBTM-2896 > URL: https://issues.jboss.org/browse/JBTM-2896 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.5.24.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > There is some code in OptimisticLockRecord#topLevelCommit that generates an invalid warning > bq. WARN: ARJUNA015051: OptimisticLockRecord.topLevelCommit state check failed for org.jboss.stm.internal.proxy.OptimisticLockManagerProxy at 7f058cfa will force rollback. > when in fact there is no rollback. The offending code is: > {code} > public int topLevelCommit () > { > boolean stateOK = checkState(); > > if (stateOK) > { > txojLogger.i18NLogger.warn_OptimisticLockRecord_2((LockManager) value()); > } > {code} > The condition was intended to be if (!stateOK) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:57:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2889) Include a vertx with STM quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2889: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Include a vertx with STM quickstart > ----------------------------------- > > Key: JBTM-2889 > URL: https://issues.jboss.org/browse/JBTM-2889 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, STM > Affects Versions: 5.5.24.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > It would be useful to include a quickstart that shows how to use STM with vertx -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:57:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2885) Orphan detection may attempt to rollback orphan if resource fails to return values In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2885: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Orphan detection may attempt to rollback orphan if resource fails to return values > ---------------------------------------------------------------------------------- > > Key: JBTM-2885 > URL: https://issues.jboss.org/browse/JBTM-2885 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.next > > > If the XAR returns a Xid from recover(FIRST_PASS) to XARM but then goes offline for a cycle we may attempt to rollback the Xid thinking it is stale. If the XAR returns an XAE at that point we should clear the _xidScans so we pick it up next time. > However, there is a filter that checks for transaction state (JTATransactionLogXAResourceOrphanFilter) which would detect a transaction log and ignore this Xid so adding this protection would only be considered belt-and-braces. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:57:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2865) Cache store can get an NPE as work is written to outside of _workList lock In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2865: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Cache store can get an NPE as work is written to outside of _workList lock > -------------------------------------------------------------------------- > > Key: JBTM-2865 > URL: https://issues.jboss.org/browse/JBTM-2865 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > {code} > java.lang.NullPointerException > at com.arjuna.ats.internal.arjuna.objectstore.AsyncStore.getState(CacheStore.java:579) > at com.arjuna.ats.internal.arjuna.objectstore.CacheStore.read_state(CacheStore.java:130) > at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.read_state_internal(FileSystemStore.java:331) > at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.read_committed(FileSystemStore.java:103) > at com.hp.mwtests.ts.arjuna.objectstore.ThreadWriter.run(CachedTest.java:69) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:58:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2766) Allow Transactional Driver to be used with commons-dbcp in Tomcat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2766: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Allow Transactional Driver to be used with commons-dbcp in Tomcat > ----------------------------------------------------------------- > > Key: JBTM-2766 > URL: https://issues.jboss.org/browse/JBTM-2766 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Transactional driver does not provide connection pooling but commons-dbcp (as used in Tomcat) does. We should test it and provide a demonstration and blog post of its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:58:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2893) JTS subordinate transaction could check Xid format during enlistment to allow it being edited In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2893: -------------------------------- Fix Version/s: 5.next > JTS subordinate transaction could check Xid format during enlistment to allow it being edited > --------------------------------------------------------------------------------------------- > > Key: JBTM-2893 > URL: https://issues.jboss.org/browse/JBTM-2893 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 5.next > > > When a subordinate transaction created by Narayana is imported in JTS it's capable to correctly handle only one XAResource being enlisted. When two or more resources are enlisted they all contain the same Xid. That Xid came from what {{TransactionImple}} defines (here is call which is never reached by such txn code: https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3a39e3bc9/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L1760) > That behavior is fine when txn is imported from EIS but when is managed by Narayana it should not be problem to generate Xids for each XAResource unique. > That behavior makes the issue when recovery should be part of handling. All the resources are "merged" under one record in object log store. That way can't be recovered correctly. > This handling is "fixed" in JTA (see https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3a39e3bc9/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/subordinate/TransactionImple.java#L359) where format of xid is checked when enlistment happens. Such thing could be passed to JTS mode too. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:58:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2897) Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2897: -------------------------------- Fix Version/s: 5.next > Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2897 > URL: https://issues.jboss.org/browse/JBTM-2897 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next > > > If trace logging is enabled then call on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple#registerSynchronization}} is done with {{null}} in parameter then {{NullPointerException}} is thrown but {{SystemException}} should be thrown in such case. > https://github.com/jbosstm/narayana/blob/930bd7f17f1b0cc2b8529eaa2ae1fcacf9582ac5/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L452 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:58:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2897) Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2897: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2897 > URL: https://issues.jboss.org/browse/JBTM-2897 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next > > > If trace logging is enabled then call on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple#registerSynchronization}} is done with {{null}} in parameter then {{NullPointerException}} is thrown but {{SystemException}} should be thrown in such case. > https://github.com/jbosstm/narayana/blob/930bd7f17f1b0cc2b8529eaa2ae1fcacf9582ac5/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L452 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:59:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:59:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2890) asyncAfterSynchronization throw exception when transaction abort In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2890: -------------------------------- Fix Version/s: 5.next > asyncAfterSynchronization throw exception when transaction abort > ---------------------------------------------------------------- > > Key: JBTM-2890 > URL: https://issues.jboss.org/browse/JBTM-2890 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.5.0.Final, 5.5.24.Final > Reporter: Colin Song > Assignee: Tom Jenkinson > Fix For: 5.next > > > *The problem:* > There's two problems about asyncAfterSynchronization(com.arjuna.ats.arjuna.coordinator.asyncAfterSynchronization=true) option: > * If we want asyncAfterSynchronization, we must set asyncBeforeSynchronization > * When tx abort, and we have asyncAfterSynchronization option, there's exception > *Root cause:* {{TwoPhaseCoordinator.synchronizationCompletionService}} and {{TwoPhaseCoordinator.runningSynchronizations}} only inited in {{asyncBeforeSynchronization}} > *Solution:* > Also init {{TwoPhaseCoordinator.synchronizationCompletionService}} and {{TwoPhaseCoordinator.runningSynchronizations}} in asyncAfterSynchronization -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:59:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:59:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2892) Calling Subordinate transaction to enlist with empty parameter list ends with IndexOutOfBoundsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2892: -------------------------------- Fix Version/s: 5.next > Calling Subordinate transaction to enlist with empty parameter list ends with IndexOutOfBoundsException > ------------------------------------------------------------------------------------------------------- > > Key: JBTM-2892 > URL: https://issues.jboss.org/browse/JBTM-2892 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next > > > When calling enlist method on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple}} when parameters are defined as empty array the {{IndexOutOfBoundsException}} exception is thrown. > The method call I do refer to is > https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L517 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:59:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:59:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2892) Calling Subordinate transaction to enlist with empty parameter list ends with IndexOutOfBoundsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2892: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Calling Subordinate transaction to enlist with empty parameter list ends with IndexOutOfBoundsException > ------------------------------------------------------------------------------------------------------- > > Key: JBTM-2892 > URL: https://issues.jboss.org/browse/JBTM-2892 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next > > > When calling enlist method on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple}} when parameters are defined as empty array the {{IndexOutOfBoundsException}} exception is thrown. > The method call I do refer to is > https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L517 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:59:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:59:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2890) asyncAfterSynchronization throw exception when transaction abort In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2890: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > asyncAfterSynchronization throw exception when transaction abort > ---------------------------------------------------------------- > > Key: JBTM-2890 > URL: https://issues.jboss.org/browse/JBTM-2890 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.5.0.Final, 5.5.24.Final > Reporter: Colin Song > Assignee: Tom Jenkinson > > *The problem:* > There's two problems about asyncAfterSynchronization(com.arjuna.ats.arjuna.coordinator.asyncAfterSynchronization=true) option: > * If we want asyncAfterSynchronization, we must set asyncBeforeSynchronization > * When tx abort, and we have asyncAfterSynchronization option, there's exception > *Root cause:* {{TwoPhaseCoordinator.synchronizationCompletionService}} and {{TwoPhaseCoordinator.runningSynchronizations}} only inited in {{asyncBeforeSynchronization}} > *Solution:* > Also init {{TwoPhaseCoordinator.synchronizationCompletionService}} and {{TwoPhaseCoordinator.runningSynchronizations}} in asyncAfterSynchronization -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 04:59:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 04:59:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2890) asyncAfterSynchronization throw exception when transaction abort In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2890: ----------------------------------- Assignee: Tom Jenkinson > asyncAfterSynchronization throw exception when transaction abort > ---------------------------------------------------------------- > > Key: JBTM-2890 > URL: https://issues.jboss.org/browse/JBTM-2890 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.5.0.Final, 5.5.24.Final > Reporter: Colin Song > Assignee: Tom Jenkinson > Fix For: 5.next > > > *The problem:* > There's two problems about asyncAfterSynchronization(com.arjuna.ats.arjuna.coordinator.asyncAfterSynchronization=true) option: > * If we want asyncAfterSynchronization, we must set asyncBeforeSynchronization > * When tx abort, and we have asyncAfterSynchronization option, there's exception > *Root cause:* {{TwoPhaseCoordinator.synchronizationCompletionService}} and {{TwoPhaseCoordinator.runningSynchronizations}} only inited in {{asyncBeforeSynchronization}} > *Solution:* > Also init {{TwoPhaseCoordinator.synchronizationCompletionService}} and {{TwoPhaseCoordinator.runningSynchronizations}} in asyncAfterSynchronization -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:01:00 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:01:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2793) TestATSubordinateCrashDuringPrepare failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2793: -------------------------------- Fix Version/s: 5.next > TestATSubordinateCrashDuringPrepare failure > ------------------------------------------- > > Key: JBTM-2793 > URL: https://issues.jboss.org/browse/JBTM-2793 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next > > > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/13/ > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 630.486 sec <<< FAILURE! - in com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare > subordinateMultiParticipantPrepareAndCommitTest(com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare) Time elapsed: 630.486 sec <<< ERROR! > java.lang.RuntimeException: jboss-as was not killed by Byteman, this indicates a test failure > at com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare.subordinateMultiParticipantPrepareAndCommitTest(TestATSubordinateCrashDuringPrepare.java:17) > {code} > {code} > Starting arquillian with java VM args: -server -Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dorg.jboss.byteman.verbose > -Djboss.modules.system.pkgs=org.jboss.byteman > -Dorg.jboss.byteman.transform.all > -javaagent:/home/jenkins/workspace/narayana-codeCoverage/XTS/localjunit/crash-recovery-tests/target/lib/byteman.jar=script:target/test-classes/scripts/ATSubordinateCrashDuringPrepare.btm,boot:target/lib/byteman.jar,listener:true isIPv6: false > Deleting: /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/tx-object-store > remove tx-object-store: /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/tx-object-store > remove /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/content/75 > remove /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/content/d8 > copy /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/docs/examples/configs/standalone-xts.xml to /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration/standalone-xts.xml > Nov 15, 2016 4:41:31 PM com.arjuna.qa.junit.BaseCrashTest runTest > INFO: Test starting, server should be down: ATSubordinateCrashDuringPrepare:subordinate.MultiParticipantPrepareAndCommitTest > Nov 15, 2016 4:41:31 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance with overridden configuration. New configuration: {managementAddress=127.0.0.1, javaVmArguments=-server -Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dorg.jboss.byteman.verbose > -Djboss.modules.system.pkgs=org.jboss.byteman > -Dorg.jboss.byteman.transform.all > -javaagent:/home/jenkins/workspace/narayana-codeCoverage/XTS/localjunit/crash-recovery-tests/target/lib/byteman.jar=script:target/test-classes/scripts/ATSubordinateCrashDuringPrepare.btm,boot:target/lib/byteman.jar,listener:true -Dorg.jboss.jbossts.xts.servicetests.XTSServiceTestName=org.jboss.jbossts.xts.servicetests.test.at.subordinate.MultiParticipantPrepareAndCommitTest, startupTimeoutInSeconds=60, serverConfig=standalone-xts.xml} > Nov 15, 2016 4:41:31 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > Nov 15, 2016 4:41:31 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/lib/jvm/java-1.8.0-openjdk/bin/java, -D[Standalone], -server, -Xms64m, -Xmx1024m, -XX:MaxPermSize=512m, -Dorg.jboss.byteman.verbose, -Djboss.modules.system.pkgs=org.jboss.byteman, -Dorg.jboss.byteman.transform.all, -javaagent:/home/jenkins/workspace/narayana-codeCoverage/XTS/localjunit/crash-recovery-tests/target/lib/byteman.jar=script:target/test-classes/scripts/ATSubordinateCrashDuringPrepare.btm,boot:target/lib/byteman.jar,listener:true, -Dorg.jboss.jbossts.xts.servicetests.XTSServiceTestName=org.jboss.jbossts.xts.servicetests.test.at.subordinate.MultiParticipantPrepareAndCommitTest, -ea, -Djboss.home.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/jboss-modules.jar, -mp, /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT, -Djboss.server.base.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration, -c=standalone-xts.xml] > OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 16:41:31,887 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta3 > 16:41:32,074 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.Final > 16:41:32,173 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Core 3.0.0.Alpha12 "Kenny" starting > 16:41:32,321 INFO [org.jboss.as.domain.management] (MSC service thread 1-8) WFLYDM0136: Registered OpenSSL provider > 16:41:33,042 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 13) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 16:41:33,066 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 25) WFLYDR0001: Content added at location /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/content/75/4c26bdb7730dd705b361ba38f432c0cfa843bd/content > 16:41:33,084 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 16:41:33,095 INFO [org.xnio] (MSC service thread 1-4) XNIO version 3.4.1.Final > 16:41:33,101 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.4.1.Final > 16:41:33,119 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 40) WFLYCLINF0001: Activating Infinispan subsystem. > 16:41:33,121 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 39) WFLYIO001: Worker 'default' has auto-configured to 48 core threads with 384 task threads based on your 24 available processors > 16:41:33,132 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 47) WFLYJSF0007: Activated the following JSF Implementations: [main] > 16:41:33,135 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem > 16:41:33,135 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 41) WFLYIIOP0001: Activating IIOP Subsystem > 16:41:33,135 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 59) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 16:41:33,139 INFO [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem > 16:41:33,139 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 61) WFLYWS0002: Activating WebServices Extension > 16:41:33,150 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 16:41:33,152 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = h2 > 16:41:33,155 INFO [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final) > 16:41:33,158 INFO [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=5.0.0.Alpha3 > 16:41:33,185 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : possible trigger for rule create participant deletes counter in class org.jboss.jbossts.XTSService > 16:41:33,191 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Undertow 1.4.4.Final starting > 16:41:33,196 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 5.0.0.Beta7 > 16:41:33,201 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 16:41:33,201 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service > 16:41:33,201 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule reset periodic recovery wait time in class com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean > 16:41:33,220 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getPeriodicRecoveryPeriod() int for rule reset periodic recovery wait time > 16:41:33,221 INFO [stdout] (ServerService Thread Pool -- 63) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.XTSService.start() void for rule create participant deletes counter > 16:41:33,237 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : inserted trigger for create participant deletes counter in class org.jboss.jbossts.XTSService > 16:41:33,238 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : possible trigger for rule open trace file in class org.jboss.jbossts.XTSService > 16:41:33,239 INFO [stdout] (ServerService Thread Pool -- 63) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.XTSService.start() void for rule open trace file > 16:41:33,241 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for reset periodic recovery wait time in class com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean > 16:41:33,243 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : inserted trigger for open trace file in class org.jboss.jbossts.XTSService > 16:41:33,260 INFO [org.wildfly.security] (MSC service thread 1-4) ELY00001: WildFly Elytron version 1.1.0.Beta13 > 16:41:33,278 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 384 (per class), which is derived from thread worker pool sizing. > 16:41:33,278 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 96 (per class), which is derived from the number of CPUs on this host. > 16:41:33,284 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0014: Creating file handler for path '/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 16:41:33,286 INFO [stdout] (MSC service thread 1-2) Rule.execute called for reset periodic recovery wait time_0 > 16:41:33,289 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server. > 16:41:33,289 INFO [stdout] (MSC service thread 1-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:33,289 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: Host default-host starting > 16:41:33,289 INFO [stdout] (MSC service thread 1-2) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 16:41:33,290 INFO [stdout] (MSC service thread 1-2) Default helper activated > 16:41:33,291 INFO [stdout] (MSC service thread 1-2) calling installed(reset periodic recovery wait time) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:33,291 INFO [stdout] (MSC service thread 1-2) Installed rule using default helper : reset periodic recovery wait time > 16:41:33,291 INFO [stdout] (MSC service thread 1-2) reset periodic recovery wait time execute > 16:41:33,295 INFO [stdout] (MSC service thread 1-2) caught ReturnException > 16:41:33,322 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule trace TX save at prepare in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:33,351 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(boolean) int for rule trace TX save at prepare > 16:41:33,355 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for trace TX save at prepare in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:33,356 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 16:41:33,360 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule trace remove committed state and exit JVM in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:33,379 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.coordinator.BasicAction.updateState() void for rule trace remove committed state and exit JVM > 16:41:33,382 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for trace remove committed state and exit JVM in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:33,386 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule trace remove committed state in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:33,424 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.coordinator.BasicAction.updateState() void for rule trace remove committed state > 16:41:33,425 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for trace remove committed state in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:33,612 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-8) WFLYIIOP0009: CORBA ORB Service started > 16:41:33,636 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 16:41:33,646 INFO [org.jboss.as.patching] (MSC service thread 1-7) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none > 16:41:33,663 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: Started FileSystemDeploymentService for directory /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/deployments > 16:41:33,668 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "restat-web-5.4.1.Final-SNAPSHOT.war" (runtime-name: "restat-web-5.4.1.Final-SNAPSHOT.war") > 16:41:33,700 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/paging) > 16:41:33,740 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221012: Using AIO Journal > 16:41:33,873 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final > 16:41:33,959 WARN [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0088: HTTP/2 will not be enabled as TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 is not enabled. You may need to install JCE to enable strong ciphers to allow HTTP/2 to function. > 16:41:33,981 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443 > 16:41:34,003 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,004 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,004 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,004 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,004 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,005 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,005 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,005 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,005 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,007 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,007 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,007 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,007 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,008 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,055 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.8) > 16:41:34,057 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-c11 > 16:41:34,057 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-participant > 16:41:34,057 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-client > 16:41:34,057 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-coordinator > 16:41:34,060 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 16:41:34,063 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 16:41:34,064 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 16:41:34,065 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 16:41:34,102 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=TerminationParticipantService > address=http://localhost:8080/ws-t11-client/TerminationParticipantService > implementor=com.arjuna.webservices11.wsarjtx.sei.TerminationParticipantPortTypeImpl > serviceName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService > portName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,102 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-5) JBWS024061: Adding service endpoint metadata: id=ActivationService > address=http://localhost:8080/ws-c11/ActivationService > implementor=com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService > portName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,102 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=CompletionCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > implementor=com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,102 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-6) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithCoordinatorCompletionParticipantService > address=http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionParticipantPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionParticipantService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,102 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=CompletionInitiatorService > address=http://localhost:8080/ws-t11-client/CompletionInitiatorService > implementor=com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=TerminationCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > implementor=com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > serviceName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService > portName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-6) JBWS024061: Adding service endpoint metadata: id=ParticipantService > address=http://localhost:8080/ws-t11-participant/ParticipantService > implementor=com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-5) JBWS024061: Adding service endpoint metadata: id=RegistrationService > address=http://localhost:8080/ws-c11/RegistrationService > implementor=com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService > portName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-6) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithParticipantCompletionParticipantService > address=http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=TerminationCoordinatorRPCService > address=http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > implementor=com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > serviceName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService > portName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypePort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithCoordinatorCompletionCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionCoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithParticipantCompletionCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,104 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=CoordinatorService > address=http://localhost:8080/ws-t11-coordinator/CoordinatorService > implementor=com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,104 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=CompletionCoordinatorRPCService > address=http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > implementor=com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorRPCService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorRPCPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,151 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.restat-web-5.4.1.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 16:41:34,152 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.restat-web-5.4.1.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 16:41:34,270 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 16:41:34,270 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 16:41:34,270 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 16:41:34,271 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 16:41:34,302 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,303 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,338 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live > 16:41:34,338 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.5.0 [default, nodeID=ef9290cb-ab4d-11e6-b97f-0242ac110007] > 16:41:34,340 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 69) AMQ221003: Deploying queue jms.queue.DLQ > 16:41:34,374 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221003: Deploying queue jms.queue.ExpiryQueue > 16:41:34,390 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 16:41:34,391 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 16:41:34,435 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 16:41:34,474 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0021: Registered web context: '/rest-tx' for server 'default-server' > 16:41:34,475 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) Resource adaptor started > 16:41:34,475 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatoractivemq-ra > 16:41:34,477 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 16:41:34,477 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 16:41:34,536 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from class com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > 16:41:34,536 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationParticipantPortType > 16:41:34,536 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-6) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionParticipantService from class org.oasis_open.docs.ws_tx.wsba._2006._06.BusinessAgreementWithCoordinatorCompletionParticipantPortType > 16:41:34,536 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > 16:41:34,949 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-client/TerminationParticipantService > 16:41:34,949 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-6) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > 16:41:34,949 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-5) Setting the server's publish address to be http://localhost:8080/ws-c11/ActivationService > 16:41:34,949 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > 16:41:35,055 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorService.wsdl > 16:41:35,056 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-5) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/ActivationService.wsdl > 16:41:35,056 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationCoordinatorPortType > 16:41:35,057 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from class com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > 16:41:35,057 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/TerminationParticipantService.wsdl > 16:41:35,058 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService from class com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > 16:41:35,060 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-6) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithCoordinatorCompletionParticipantService.wsdl > 16:41:35,060 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-6) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from class com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > 16:41:35,065 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > 16:41:35,070 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-client/CompletionInitiatorService > 16:41:35,073 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-6) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/ParticipantService > 16:41:35,073 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorService.wsdl > 16:41:35,074 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService from class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > 16:41:35,075 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-5) Setting the server's publish address to be http://localhost:8080/ws-c11/RegistrationService > 16:41:35,076 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > 16:41:35,078 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/CompletionInitiatorService.wsdl > 16:41:35,079 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-6) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/ParticipantService.wsdl > 16:41:35,080 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-6) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > 16:41:35,080 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorRPCPortTypeImplService.wsdl > 16:41:35,081 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > 16:41:35,083 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-5) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/RegistrationService.wsdl > 16:41:35,085 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 16:41:35,085 INFO [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 16:41:35,086 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-6) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > 16:41:35,086 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 16:41:35,086 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 16:41:35,091 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-client > 16:41:35,091 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-c11 > 16:41:35,094 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-6) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithParticipantCompletionParticipantService.wsdl > 16:41:35,095 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: '/ws-t11-client' for server 'default-server' > 16:41:35,095 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0021: Registered web context: '/ws-c11' for server 'default-server' > 16:41:35,098 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 16:41:35,098 INFO [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 16:41:35,098 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 16:41:35,098 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > 16:41:35,099 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-participant > 16:41:35,099 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0021: Registered web context: '/ws-t11-participant' for server 'default-server' > 16:41:35,106 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithCoordinatorCompletionCoordinatorService.wsdl > 16:41:35,107 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > 16:41:35,112 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > 16:41:35,120 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithParticipantCompletionCoordinatorService.wsdl > 16:41:35,120 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from class com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > 16:41:35,123 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CoordinatorService > 16:41:35,129 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CoordinatorService.wsdl > 16:41:35,130 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorRPCService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > 16:41:35,132 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > 16:41:35,138 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorRPCService.wsdl > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-coordinator > 16:41:35,143 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0021: Registered web context: '/ws-t11-coordinator' for server 'default-server' > 16:41:35,147 INFO [stdout] (MSC service thread 1-8) Rule.execute called for open trace file_2 > 16:41:35,148 INFO [stdout] (MSC service thread 1-8) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:35,148 INFO [stdout] (MSC service thread 1-8) calling installed(open trace file) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:35,148 INFO [stdout] (MSC service thread 1-8) Installed rule using default helper : open trace file > 16:41:35,148 INFO [stdout] (MSC service thread 1-8) open trace file execute > 16:41:35,149 INFO [stdout] (MSC service thread 1-8) Rule.execute called for create participant deletes counter_1 > 16:41:35,149 INFO [stdout] (MSC service thread 1-8) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:35,149 INFO [stdout] (MSC service thread 1-8) calling installed(create participant deletes counter) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:35,149 INFO [stdout] (MSC service thread 1-8) Installed rule using default helper : create participant deletes counter > 16:41:35,149 INFO [stdout] (MSC service thread 1-8) create participant deletes counter execute > 16:41:35,159 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : possible trigger for rule trace Participant send rollback in class com.arjuna.wst11.messaging.CoordinatorProcessorImpl > 16:41:35,160 INFO [stdout] (MSC service thread 1-8) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.CoordinatorProcessorImpl.prepared(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace Participant send rollback > 16:41:35,163 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : inserted trigger for trace Participant send rollback in class com.arjuna.wst11.messaging.CoordinatorProcessorImpl > 16:41:35,179 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate coordinator close in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:35,180 INFO [stdout] (MSC service thread 1-8) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator.rollback() void for rule trace subordinate coordinator close > 16:41:35,181 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate coordinator close in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:35,182 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate coordinator prepare in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:35,182 INFO [stdout] (MSC service thread 1-8) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator.prepare() int for rule trace subordinate coordinator prepare > 16:41:35,183 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate coordinator prepare in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:35,184 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate coordinator rollback 2 in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:35,185 INFO [stdout] (MSC service thread 1-8) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator.rollback() void for rule trace subordinate coordinator rollback 2 > 16:41:35,186 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate coordinator rollback 2 in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:35,197 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : possible trigger for rule trace delete participant and exit JVM in class org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple > 16:41:35,197 INFO [stdout] (MSC service thread 1-8) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple.deleteParticipantRecoveryRecord(java.lang.String) boolean for rule trace delete participant and exit JVM > 16:41:35,198 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : inserted trigger for trace delete participant and exit JVM in class org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple > 16:41:35,221 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-4) ARJUNA033013: OutboundBridgeRecoveryManager starting > 16:41:35,221 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-8) ARJUNA033006: InboundBridgeRecoveryManager starting > 16:41:35,235 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "restat-web-5.4.1.Final-SNAPSHOT.war" (runtime-name : "restat-web-5.4.1.Final-SNAPSHOT.war") > 16:41:35,301 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 16:41:35,301 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 16:41:35,301 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha12 "Kenny" started in 3688ms - Started 508 of 752 services (451 services are lazy, passive or on-demand) > 16:41:35,378 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/content/67/eecc8af4663400c3ea658c818ff35814a26f3a/content > 16:41:35,380 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "xtstest.war" (runtime-name: "xtstest.war") > 16:41:35,661 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.xtstest.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 16:41:35,675 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment xtstest.war > 16:41:35,699 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-6) HV000001: Hibernate Validator 5.2.4.Final > 16:41:35,830 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 2.4.0 (Final) > 16:41:35,837 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Service_One > address=http://localhost:8080/xtstest/xtsservicetest1 > implementor=org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:35,838 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Service_Two > address=http://localhost:8080/xtstest/xtsservicetest2 > implementor=org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:35,838 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Service_Three > address=http://localhost:8080/xtstest/xtsservicetest3 > implementor=org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:35,838 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Subordinate_Service_One > address=http://localhost:8080/xtstest/xtssubordinateservicetest1 > implementor=org.jboss.jbossts.xts.servicetests.service.subordinate.XTSSubordinateServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:35,848 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:35,881 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest1 > 16:41:35,887 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:35,888 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:35,890 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest2 > 16:41:35,892 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:35,893 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:35,894 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest3 > 16:41:35,897 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:35,897 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:35,898 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/xtstest/xtssubordinateservicetest1 > 16:41:35,902 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:35,909 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 16:41:35,910 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 16:41:35,910 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 16:41:35,910 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 16:41:35,913 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:35,914 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:36,099 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-1) WELD-000169: Jandex cannot distinguish inner and static nested classes! Update Jandex to 2.0.3.Final version or newer to improve scanning performance. > 16:41:36,386 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 13) Starting XTSServiceTestRunner > 16:41:36,386 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 13) Starting XTS Service Test org.jboss.jbossts.xts.servicetests.test.at.subordinate.MultiParticipantPrepareAndCommitTest > 16:41:36,386 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 13) Started XTSServiceTestRunner > 16:41:36,394 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 13) Initializing Mojarra 2.2.13.SP1 20160303-1204 for context '/xtstest' > 16:41:36,784 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 13) WFLYUT0021: Registered web context: '/xtstest' for server 'default-server' > 16:41:36,811 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") > Nov 15, 2016 4:41:36 PM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > Nov 15, 2016 4:41:36 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill > INFO: Hard killing of a server instance > Nov 15, 2016 4:41:36 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: waiting for byteman to kill the server > Nov 15, 2016 4:41:36 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > 16:41:41,421 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Thread-123) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 16:41:41,431 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Thread-123) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 16:41:41,785 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Thread-123) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 16:41:41,817 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Thread-123) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: vfs:/content/xtstest.war/WEB-INF/classes/org/jboss/jbossts/xts/servicetests/generated/wsdl/xtsservicetests.wsdl > 16:41:41,862 INFO [stdout] (default task-3) service /xtsservicetest1 > 16:41:41,862 INFO [stdout] (default task-3) command enlistDurable > 16:41:41,862 INFO [stdout] (default task-3) command prepare > 16:41:41,862 INFO [stdout] (default task-3) command commit > 16:41:41,880 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-3) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 16:41:41,901 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace Coordinator engine create in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,902 INFO [stdout] (default task-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.(java.lang.String,boolean,javax.xml.ws.wsaddressing.W3CEndpointReference,boolean,com.arjuna.webservices11.wsat.State) void for rule trace Coordinator engine create > 16:41:41,911 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace Coordinator engine create in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,912 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive Participant aborted in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,913 INFO [stdout] (default task-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.aborted(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive Participant aborted > 16:41:41,918 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive Participant aborted in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,919 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive participant prepared in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,920 INFO [stdout] (default task-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.prepared(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive participant prepared > 16:41:41,926 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive participant prepared in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,927 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send participant prepare in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,928 INFO [stdout] (default task-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.prepare() com.arjuna.webservices11.wsat.State for rule trace send participant prepare > 16:41:41,933 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace send participant prepare in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,934 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send Participant rollback in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,935 INFO [stdout] (default task-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.rollback() com.arjuna.webservices11.wsat.State for rule trace send Participant rollback > 16:41:41,940 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace send Participant rollback in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,942 INFO [stdout] (default task-4) Rule.execute called for trace Coordinator engine create_11 > 16:41:41,943 INFO [stdout] (default task-4) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:41,943 INFO [stdout] (default task-4) calling installed(trace Coordinator engine create) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:41,943 INFO [stdout] (default task-4) Installed rule using default helper : trace Coordinator engine create > 16:41:41,943 INFO [stdout] (default task-4) trace Coordinator engine create execute > 16:41:41,955 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : possible trigger for rule trace Participant create in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,956 INFO [stdout] (default task-3) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.(com.arjuna.wst.Participant,java.lang.String,com.arjuna.webservices11.wsat.State,javax.xml.ws.wsaddressing.W3CEndpointReference,boolean) void for rule trace Participant create > 16:41:41,968 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : inserted trigger for trace Participant create in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,969 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive participant prepare in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,970 INFO [stdout] (default task-3) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.prepare(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive participant prepare > 16:41:41,976 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive participant prepare in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,978 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send Participant prepared in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,984 INFO [stdout] (default task-3) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.sendPrepared(boolean) void for rule trace send Participant prepared > 16:41:41,984 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : inserted trigger for trace send Participant prepared in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,986 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive Participant rollback in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,986 INFO [stdout] (default task-3) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.rollback(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive Participant rollback > 16:41:41,993 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive Participant rollback in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,994 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send Participant aborted in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:42,000 INFO [stdout] (default task-3) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.sendAborted() void for rule trace send Participant aborted > 16:41:42,000 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : inserted trigger for trace send Participant aborted in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:42,002 INFO [stdout] (default task-3) Rule.execute called for trace Participant create_16 > 16:41:42,002 INFO [stdout] (default task-3) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,002 INFO [stdout] (default task-3) calling installed(trace Participant create) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,002 INFO [stdout] (default task-3) Installed rule using default helper : trace Participant create > 16:41:42,002 INFO [stdout] (default task-3) trace Participant create execute > 16:41:42,029 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub rollback in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,030 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.rollback() void for rule trace subordinate participant stub rollback > 16:41:42,031 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub rollback in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,031 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub prepare in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,031 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.prepare() com.arjuna.wst.Vote for rule trace subordinate participant stub prepare > 16:41:42,032 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub prepare in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,032 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub prepare 2 in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,033 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.prepare() com.arjuna.wst.Vote for rule trace subordinate participant stub prepare 2 > 16:41:42,033 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub prepare 2 in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,034 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub rollback forward in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,034 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.rollback() void for rule trace subordinate participant stub rollback forward > 16:41:42,035 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub rollback forward in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,036 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub rollback with no coordinator in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,036 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.rollback() void for rule trace subordinate participant stub rollback with no coordinator > 16:41:42,037 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub rollback with no coordinator in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,037 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub rollback with unactivated coordinator in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,038 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.rollback() void for rule trace subordinate participant stub rollback with unactivated coordinator > 16:41:42,038 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub rollback with unactivated coordinator in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,039 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub rollback return in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,039 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.rollback() void for rule trace subordinate participant stub rollback return > 16:41:42,040 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub rollback return in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,055 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 16:41:42,071 INFO [stdout] (default task-6) Rule.execute called for trace Coordinator engine create_11 > 16:41:42,072 INFO [stdout] (default task-6) trace Coordinator engine create execute > 16:41:42,081 INFO [stdout] (default task-5) Rule.execute called for trace Participant create_16 > 16:41:42,082 INFO [stdout] (default task-5) trace Participant create execute > 16:41:42,091 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 16:41:42,104 INFO [stdout] (default task-7) Rule.execute called for trace Coordinator engine create_11 > 16:41:42,105 INFO [stdout] (default task-7) trace Coordinator engine create execute > 16:41:42,112 INFO [stdout] (default task-5) Rule.execute called for trace Participant create_16 > 16:41:42,112 INFO [stdout] (default task-5) trace Participant create execute > 16:41:42,116 INFO [stdout] (default task-5) service /xtssubordinateservicetest1 > 16:41:42,116 INFO [stdout] (default task-5) command enlistDurable > 16:41:42,116 INFO [stdout] (default task-5) command prepare > 16:41:42,116 INFO [stdout] (default task-5) command commit > 16:41:42,128 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 16:41:42,140 INFO [stdout] (default task-8) Rule.execute called for trace Coordinator engine create_11 > 16:41:42,141 INFO [stdout] (default task-8) trace Coordinator engine create execute > 16:41:42,148 INFO [stdout] (default task-5) Rule.execute called for trace Participant create_16 > 16:41:42,148 INFO [stdout] (default task-5) trace Participant create execute > 16:41:42,169 INFO [stdout] (default task-9) service /xtssubordinateservicetest1 > 16:41:42,170 INFO [stdout] (default task-9) command enlistDurable > 16:41:42,170 INFO [stdout] (default task-9) command prepare > 16:41:42,170 INFO [stdout] (default task-9) command commit > 16:41:42,181 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-9) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 16:41:42,193 INFO [stdout] (default task-10) Rule.execute called for trace Coordinator engine create_11 > 16:41:42,193 INFO [stdout] (default task-10) trace Coordinator engine create execute > 16:41:42,199 INFO [stdout] (default task-9) Rule.execute called for trace Participant create_16 > 16:41:42,199 INFO [stdout] (default task-9) trace Participant create execute > 16:41:42,220 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Thread-123) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-completion-coordinator-binding.wsdl > 16:41:42,254 INFO [stdout] (TaskWorker-1) Rule.execute called for trace send participant prepare_14 > 16:41:42,255 INFO [stdout] (TaskWorker-1) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,255 INFO [stdout] (TaskWorker-1) calling installed(trace send participant prepare) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,255 INFO [stdout] (TaskWorker-1) Installed rule using default helper : trace send participant prepare > 16:41:42,255 INFO [stdout] (TaskWorker-1) trace send participant prepare execute > 16:41:42,255 INFO [stdout] (TaskWorker-1) rule.debug{trace send participant prepare} : prepare sent for Coordinator engine V0:ffffac110007:-3ffa9bb3:582b3abd:1b > 16:41:42,274 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:41:42,300 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive participant prepare_17 > 16:41:42,301 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,301 INFO [stdout] (TaskWorker-2) calling installed(trace receive participant prepare) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,301 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace receive participant prepare > 16:41:42,301 INFO [stdout] (TaskWorker-2) trace receive participant prepare execute > 16:41:42,301 INFO [stdout] (TaskWorker-2) rule.debug{trace receive participant prepare} : prepare received for participant org.jboss.jbossts.xts.at.subordinate.participant.0:ffffac110007:-3ffa9bb3:582b3abd:19_V > 16:41:42,302 INFO [stdout] (TaskWorker-2) Rule.execute called for trace send Participant prepared_18 > 16:41:42,303 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,303 INFO [stdout] (TaskWorker-2) calling installed(trace send Participant prepared) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,303 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace send Participant prepared > 16:41:42,303 INFO [stdout] (TaskWorker-2) trace send Participant prepared execute > 16:41:42,303 INFO [stdout] (TaskWorker-2) rule.debug{trace send Participant prepared} : prepared sent for Participant org.jboss.jbossts.xts.at.subordinate.participant.0:ffffac110007:-3ffa9bb3:582b3abd:19_V > 16:41:42,321 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:41:42,342 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive participant prepared_13 > 16:41:42,342 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,342 INFO [stdout] (TaskWorker-2) calling installed(trace receive participant prepared) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,342 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace receive participant prepared > 16:41:42,342 INFO [stdout] (TaskWorker-2) trace receive participant prepared execute > 16:41:42,342 INFO [stdout] (TaskWorker-2) rule.debug{trace receive participant prepared} : prepared received for Coordinator engine V0:ffffac110007:-3ffa9bb3:582b3abd:1b > 16:41:42,343 INFO [stdout] (TaskWorker-1) Rule.execute called for trace send participant prepare_14 > 16:41:42,343 INFO [stdout] (TaskWorker-1) trace send participant prepare execute > 16:41:42,343 INFO [stdout] (TaskWorker-1) rule.debug{trace send participant prepare} : prepare sent for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:16 > 16:41:42,352 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:41:42,367 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive participant prepare_17 > 16:41:42,368 INFO [stdout] (TaskWorker-2) trace receive participant prepare execute > 16:41:42,368 INFO [stdout] (TaskWorker-2) rule.debug{trace receive participant prepare} : prepare received for participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:41:42,396 INFO [stdout] (TaskWorker-2) Rule.execute called for trace send Participant prepared_18 > 16:41:42,396 INFO [stdout] (TaskWorker-2) trace send Participant prepared execute > 16:41:42,396 INFO [stdout] (TaskWorker-2) rule.debug{trace send Participant prepared} : prepared sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:41:42,404 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:41:42,422 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive participant prepared_13 > 16:41:42,422 INFO [stdout] (TaskWorker-2) trace receive participant prepared execute > 16:41:42,422 INFO [stdout] (TaskWorker-2) rule.debug{trace receive participant prepared} : prepared received for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:16 > 16:41:42,423 INFO [stdout] (TaskWorker-1) Rule.execute called for trace send participant prepare_14 > 16:41:42,423 INFO [stdout] (TaskWorker-1) trace send participant prepare execute > 16:41:42,423 INFO [stdout] (TaskWorker-1) rule.debug{trace send participant prepare} : prepare sent for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:1d > 16:41:42,430 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:41:42,445 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive participant prepare_17 > 16:41:42,445 INFO [stdout] (TaskWorker-2) trace receive participant prepare execute > 16:41:42,446 INFO [stdout] (TaskWorker-2) rule.debug{trace receive participant prepare} : prepare received for participant org.jboss.jbossts.xts.at.subordinate.participant.0:ffffac110007:-3ffa9bb3:582b3abd:19_D > 16:41:42,446 INFO [stdout] (TaskWorker-2) Rule.execute called for trace subordinate participant stub prepare_22 > 16:41:42,446 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,446 INFO [stdout] (TaskWorker-2) calling installed(trace subordinate participant stub prepare) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,446 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace subordinate participant stub prepare > 16:41:42,446 INFO [stdout] (TaskWorker-2) trace subordinate participant stub prepare execute > 16:41:42,446 INFO [stdout] (TaskWorker-2) rule.debug{trace subordinate participant stub prepare} : prepare called for pseudo-participant com.arjuna.wst11.stub.SubordinateDurable2PCStub at 422a3fd3 > 16:41:42,446 INFO [stdout] (TaskWorker-2) Rule.execute called for trace subordinate coordinator prepare_8 > 16:41:42,447 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,447 INFO [stdout] (TaskWorker-2) calling installed(trace subordinate coordinator prepare) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,447 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace subordinate coordinator prepare > 16:41:42,447 INFO [stdout] (TaskWorker-2) trace subordinate coordinator prepare execute > 16:41:42,447 INFO [stdout] (TaskWorker-2) rule.debug{trace subordinate coordinator prepare} : prepare for subordinate transaction 0:ffffac110007:-3ffa9bb3:582b3abd:19 > 16:41:42,447 INFO [stdout] (TaskWorker-2) Rule.execute called for trace send participant prepare_14 > 16:41:42,448 INFO [stdout] (TaskWorker-2) trace send participant prepare execute > 16:41:42,448 INFO [stdout] (TaskWorker-2) rule.debug{trace send participant prepare} : prepare sent for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:20 > 16:41:42,456 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:41:42,471 INFO [stdout] (TaskWorker-3) Rule.execute called for trace receive participant prepare_17 > 16:41:42,471 INFO [stdout] (TaskWorker-3) trace receive participant prepare execute > 16:41:42,471 INFO [stdout] (TaskWorker-3) rule.debug{trace receive participant prepare} : prepare received for participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:41:42,706 INFO [stdout] (TaskWorker-3) Rule.execute called for trace send Participant prepared_18 > 16:41:42,707 INFO [stdout] (TaskWorker-3) trace send Participant prepared execute > 16:41:42,707 INFO [stdout] (TaskWorker-3) rule.debug{trace send Participant prepared} : prepared sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:41:42,714 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-3) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:41:42,729 INFO [stdout] (TaskWorker-3) Rule.execute called for trace receive participant prepared_13 > 16:41:42,729 INFO [stdout] (TaskWorker-3) trace receive participant prepared execute > 16:41:42,729 INFO [stdout] (TaskWorker-3) rule.debug{trace receive participant prepared} : prepared received for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:20 > 16:41:42,730 INFO [stdout] (TaskWorker-2) Rule.execute called for trace send participant prepare_14 > 16:41:42,730 INFO [stdout] (TaskWorker-2) trace send participant prepare execute > 16:41:42,730 INFO [stdout] (TaskWorker-2) rule.debug{trace send participant prepare} : prepare sent for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:23 > 16:41:42,739 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:41:42,751 INFO [stdout] (TaskWorker-3) Rule.execute called for trace receive participant prepare_17 > 16:41:42,751 INFO [stdout] (TaskWorker-3) trace receive participant prepare execute > 16:41:42,751 INFO [stdout] (TaskWorker-3) rule.debug{trace receive participant prepare} : prepare received for participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:41:42,753 INFO [stdout] (TaskWorker-3) Rule.execute called for trace send Participant prepared_18 > 16:41:42,753 INFO [stdout] (TaskWorker-3) trace send Participant prepared execute > 16:41:42,753 INFO [stdout] (TaskWorker-3) rule.debug{trace send Participant prepared} : prepared sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:41:42,759 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-3) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:41:42,773 INFO [stdout] (TaskWorker-3) Rule.execute called for trace receive participant prepared_13 > 16:41:42,773 INFO [stdout] (TaskWorker-3) trace receive participant prepared execute > 16:41:42,774 INFO [stdout] (TaskWorker-3) rule.debug{trace receive participant prepared} : prepared received for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:23 > 16:41:42,777 INFO [stdout] (TaskWorker-2) Rule.execute called for trace TX save at prepare_3 > 16:41:42,778 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,778 INFO [stdout] (TaskWorker-2) calling installed(trace TX save at prepare) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,778 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace TX save at prepare > 16:41:42,778 INFO [stdout] (TaskWorker-2) trace TX save at prepare execute > 16:41:42,778 INFO [stdout] (TaskWorker-2) rule.debug{trace TX save at prepare} : saved to disk transaction 0:ffffac110007:-3ffa9bb3:582b3abd:19 > 16:41:42,782 INFO [stdout] (TaskWorker-2) Rule.execute called for trace subordinate participant stub prepare 2_23 > 16:41:42,782 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,782 INFO [stdout] (TaskWorker-2) calling installed(trace subordinate participant stub prepare 2) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,782 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace subordinate participant stub prepare 2 > 16:41:42,782 INFO [stdout] (TaskWorker-2) trace subordinate participant stub prepare 2 execute > 16:41:42,782 INFO [stdout] (TaskWorker-2) rule.debug{trace subordinate participant stub prepare 2} : JVM exit > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep '\[java\] '`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as killed by byteman scirpt > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommand > INFO: Executing shell command: 'mkdir target/surefire-reports/processes' > std error mkdir: cannot create directory 'target/surefire-reports/processes': File exists > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.BaseServerKillProcessor dumpStream > INFO: Execution result: 'mkdir: cannot create directory 'target/surefire-reports/processes': File exists' > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommand > INFO: Executing shell command: 'ps aux > target/surefire-reports/processes/null:null_12.txt' > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.BaseServerKillProcessor dumpProcesses > INFO: Logged current running processes to: target/surefire-reports/processes/null:null_12.txt > Nov 15, 2016 4:41:46 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance with overridden configuration. New configuration: {managementAddress=127.0.0.1, javaVmArguments=-server -Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dorg.jboss.byteman.verbose > -Djboss.modules.system.pkgs=org.jboss.byteman > -Dorg.jboss.byteman.transform.all > -javaagent:/home/jenkins/workspace/narayana-codeCoverage/XTS/localjunit/crash-recovery-tests/target/lib/byteman.jar=script:target/test-classes/scripts/ATSubordinateCrashDuringPrepare.btm,boot:target/lib/byteman.jar,listener:true , startupTimeoutInSeconds=60, serverConfig=standalone-xts.xml} > Nov 15, 2016 4:41:46 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > Nov 15, 2016 4:41:46 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/lib/jvm/java-1.8.0-openjdk/bin/java, -D[Standalone], -server, -Xms64m, -Xmx1024m, -XX:MaxPermSize=512m, -Dorg.jboss.byteman.verbose, -Djboss.modules.system.pkgs=org.jboss.byteman, -Dorg.jboss.byteman.transform.all, -javaagent:/home/jenkins/workspace/narayana-codeCoverage/XTS/localjunit/crash-recovery-tests/target/lib/byteman.jar=script:target/test-classes/scripts/ATSubordinateCrashDuringPrepare.btm,boot:target/lib/byteman.jar,listener:true, -ea, -Djboss.home.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/jboss-modules.jar, -mp, /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT, -Djboss.server.base.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration, -c=standalone-xts.xml] > OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 16:41:47,298 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta3 > 16:41:47,473 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.Final > 16:41:47,565 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Core 3.0.0.Alpha12 "Kenny" starting > 16:41:47,703 INFO [org.jboss.as.domain.management] (MSC service thread 1-1) WFLYDM0136: Registered OpenSSL provider > 16:41:48,403 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 7) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 16:41:48,449 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 16:41:48,460 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.4.1.Final > 16:41:48,465 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.4.1.Final > 16:41:48,483 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 40) WFLYCLINF0001: Activating Infinispan subsystem. > 16:41:48,484 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 41) WFLYIIOP0001: Activating IIOP Subsystem > 16:41:48,485 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 39) WFLYIO001: Worker 'default' has auto-configured to 48 core threads with 384 task threads based on your 24 available processors > 16:41:48,487 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 47) WFLYJSF0007: Activated the following JSF Implementations: [main] > 16:41:48,493 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final) > 16:41:48,536 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 16:41:48,537 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem > 16:41:48,540 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = h2 > 16:41:48,550 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 59) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 16:41:48,557 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 61) WFLYWS0002: Activating WebServices Extension > 16:41:48,558 INFO [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem > 16:41:48,560 INFO [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=5.0.0.Alpha3 > 16:41:48,599 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.4.4.Final starting > 16:41:48,602 INFO [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service > 16:41:48,603 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 16:41:48,616 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 5.0.0.Beta7 > 16:41:48,636 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : possible trigger for rule create participant deletes counter in class org.jboss.jbossts.XTSService > 16:41:48,663 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : possible trigger for rule reset periodic recovery wait time in class com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean > 16:41:48,675 INFO [stdout] (MSC service thread 1-7) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getPeriodicRecoveryPeriod() int for rule reset periodic recovery wait time > 16:41:48,676 INFO [stdout] (ServerService Thread Pool -- 63) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.XTSService.start() void for rule create participant deletes counter > 16:41:48,684 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : inserted trigger for reset periodic recovery wait time in class com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean > 16:41:48,691 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : inserted trigger for create participant deletes counter in class org.jboss.jbossts.XTSService > 16:41:48,693 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : possible trigger for rule open trace file in class org.jboss.jbossts.XTSService > 16:41:48,695 INFO [stdout] (ServerService Thread Pool -- 63) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.XTSService.start() void for rule open trace file > 16:41:48,699 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : inserted trigger for open trace file in class org.jboss.jbossts.XTSService > 16:41:48,707 INFO [org.wildfly.security] (MSC service thread 1-8) ELY00001: WildFly Elytron version 1.1.0.Beta13 > 16:41:48,710 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 96 (per class), which is derived from the number of CPUs on this host. > 16:41:48,710 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 384 (per class), which is derived from thread worker pool sizing. > 16:41:48,723 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0014: Creating file handler for path '/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 16:41:48,730 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server. > 16:41:48,731 INFO [stdout] (MSC service thread 1-7) Rule.execute called for reset periodic recovery wait time_1 > 16:41:48,731 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: Host default-host starting > 16:41:48,733 INFO [stdout] (MSC service thread 1-7) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:48,735 INFO [stdout] (MSC service thread 1-7) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 16:41:48,735 INFO [stdout] (MSC service thread 1-7) Default helper activated > 16:41:48,735 INFO [stdout] (MSC service thread 1-7) calling installed(reset periodic recovery wait time) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:48,736 INFO [stdout] (MSC service thread 1-7) Installed rule using default helper : reset periodic recovery wait time > 16:41:48,736 INFO [stdout] (MSC service thread 1-7) reset periodic recovery wait time execute > 16:41:48,736 INFO [stdout] (MSC service thread 1-7) caught ReturnException > 16:41:48,761 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : possible trigger for rule trace TX save at prepare in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:48,790 INFO [stdout] (MSC service thread 1-7) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(boolean) int for rule trace TX save at prepare > 16:41:48,794 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : inserted trigger for trace TX save at prepare in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:48,794 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 16:41:48,799 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : possible trigger for rule trace remove committed state and exit JVM in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:48,817 INFO [stdout] (MSC service thread 1-7) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.coordinator.BasicAction.updateState() void for rule trace remove committed state and exit JVM > 16:41:48,818 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : inserted trigger for trace remove committed state and exit JVM in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:48,822 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : possible trigger for rule trace remove committed state in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:48,840 INFO [stdout] (MSC service thread 1-7) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.coordinator.BasicAction.updateState() void for rule trace remove committed state > 16:41:48,843 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : inserted trigger for trace remove committed state in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:48,923 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-6) WFLYIIOP0009: CORBA ORB Service started > 16:41:49,091 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 16:41:49,106 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none > 16:41:49,145 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "restat-web-5.4.1.Final-SNAPSHOT.war" (runtime-name: "restat-web-5.4.1.Final-SNAPSHOT.war") > 16:41:49,147 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "xtstest.war" (runtime-name: "xtstest.war") > 16:41:49,148 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/deployments > 16:41:49,324 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/paging) > 16:41:49,375 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221012: Using AIO Journal > 16:41:49,389 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final > 16:41:49,429 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,430 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,430 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,431 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,431 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,432 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,432 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,433 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,434 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,434 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,434 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,435 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,442 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,442 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,445 WARN [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0088: HTTP/2 will not be enabled as TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 is not enabled. You may need to install JCE to enable strong ciphers to allow HTTP/2 to function. > 16:41:49,456 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443 > 16:41:49,537 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.8) > 16:41:49,539 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-client > 16:41:49,539 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-coordinator > 16:41:49,539 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-participant > 16:41:49,539 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-c11 > 16:41:49,569 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 16:41:49,571 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 16:41:49,572 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithCoordinatorCompletionParticipantService > address=http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionParticipantPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionParticipantService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,572 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) JBWS024061: Adding service endpoint metadata: id=TerminationParticipantService > address=http://localhost:8080/ws-t11-client/TerminationParticipantService > implementor=com.arjuna.webservices11.wsarjtx.sei.TerminationParticipantPortTypeImpl > serviceName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService > portName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,572 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-5) JBWS024061: Adding service endpoint metadata: id=ActivationService > address=http://localhost:8080/ws-c11/ActivationService > implementor=com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService > portName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,572 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=CompletionCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > implementor=com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,572 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 16:41:49,572 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=ParticipantService > address=http://localhost:8080/ws-t11-participant/ParticipantService > implementor=com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,572 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=TerminationCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > implementor=com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > serviceName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService > portName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,573 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-5) JBWS024061: Adding service endpoint metadata: id=RegistrationService > address=http://localhost:8080/ws-c11/RegistrationService > implementor=com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService > portName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,573 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithParticipantCompletionParticipantService > address=http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,573 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) JBWS024061: Adding service endpoint metadata: id=CompletionInitiatorService > address=http://localhost:8080/ws-t11-client/CompletionInitiatorService > implementor=com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,573 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 16:41:49,573 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=TerminationCoordinatorRPCService > address=http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > implementor=com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > serviceName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService > portName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypePort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,573 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithCoordinatorCompletionCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionCoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,574 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithParticipantCompletionCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,574 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=CoordinatorService > address=http://localhost:8080/ws-t11-coordinator/CoordinatorService > implementor=com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,574 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=CompletionCoordinatorRPCService > address=http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > implementor=com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorRPCService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorRPCPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,629 WARN [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.restat-web-5.4.1.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 16:41:49,629 WARN [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.restat-web-5.4.1.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 16:41:49,806 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,807 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,815 WARN [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.xtstest.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 16:41:49,833 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment xtstest.war > 16:41:49,863 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.2.4.Final > 16:41:49,897 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 16:41:49,897 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 16:41:49,897 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 16:41:49,898 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 16:41:49,937 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0021: Registered web context: '/rest-tx' for server 'default-server' > 16:41:49,960 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live > 16:41:49,960 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.5.0 [default, nodeID=ef9290cb-ab4d-11e6-b97f-0242ac110007] > 16:41:49,962 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221003: Deploying queue jms.queue.DLQ > 16:41:49,992 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 16:41:49,993 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: Deploying queue jms.queue.ExpiryQueue > 16:41:49,995 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 65) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 16:41:50,010 INFO [org.jboss.weld.Version] (MSC service thread 1-8) WELD-000900: 2.4.0 (Final) > 16:41:50,018 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-8) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Service_One > address=http://localhost:8080/xtstest/xtsservicetest1 > implementor=org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:50,019 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-8) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Service_Two > address=http://localhost:8080/xtstest/xtsservicetest2 > implementor=org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:50,019 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-8) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Service_Three > address=http://localhost:8080/xtstest/xtsservicetest3 > implementor=org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:50,019 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-8) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Subordinate_Service_One > address=http://localhost:8080/xtstest/xtssubordinateservicetest1 > implementor=org.jboss.jbossts.xts.servicetests.service.subordinate.XTSSubordinateServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:50,026 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0007: Registered connection factory java:/JmsXA > 16:41:50,036 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-8) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:50,036 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from class com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > 16:41:50,036 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > 16:41:50,036 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationParticipantPortType > 16:41:50,036 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionParticipantService from class org.oasis_open.docs.ws_tx.wsba._2006._06.BusinessAgreementWithCoordinatorCompletionParticipantPortType > 16:41:50,062 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-6) Resource adaptor started > 16:41:50,062 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatoractivemq-ra > 16:41:50,063 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 16:41:50,063 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 16:41:50,339 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-8) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest1 > 16:41:50,386 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-client/TerminationParticipantService > 16:41:50,390 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > 16:41:50,390 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > 16:41:50,400 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-5) Setting the server's publish address to be http://localhost:8080/ws-c11/ActivationService > 16:41:50,429 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-8) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:50,430 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-8) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:50,432 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-8) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest2 > 16:41:50,436 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-8) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:50,436 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-8) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:50,438 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-8) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest3 > 16:41:50,442 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-8) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:50,442 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-8) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:50,444 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-8) Setting the server's publish address to be http://localhost:8080/xtstest/xtssubordinateservicetest1 > 16:41:50,448 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorService.wsdl > 16:41:50,449 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationCoordinatorPortType > 16:41:50,449 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-8) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:50,450 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-5) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/ActivationService.wsdl > 16:41:50,450 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/TerminationParticipantService.wsdl > 16:41:50,450 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from class com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > 16:41:50,451 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService from class com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > 16:41:50,455 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > 16:41:50,459 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithCoordinatorCompletionParticipantService.wsdl > 16:41:50,460 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-client/CompletionInitiatorService > 16:41:50,460 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from class com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > 16:41:50,462 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorService.wsdl > 16:41:50,462 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/ParticipantService > 16:41:50,463 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService from class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > 16:41:50,463 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 16:41:50,463 INFO [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 16:41:50,463 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 16:41:50,464 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 16:41:50,465 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > 16:41:50,465 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-5) Setting the server's publish address to be http://localhost:8080/ws-c11/RegistrationService > 16:41:50,466 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/CompletionInitiatorService.wsdl > 16:41:50,469 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:50,470 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:50,470 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/ParticipantService.wsdl > 16:41:50,472 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > 16:41:50,472 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorRPCPortTypeImplService.wsdl > 16:41:50,472 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 16:41:50,472 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 16:41:50,473 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > 16:41:50,473 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-client > 16:41:50,478 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0021: Registered web context: '/ws-t11-client' for server 'default-server' > 16:41:50,482 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > 16:41:50,483 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-5) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/RegistrationService.wsdl > 16:41:50,487 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 16:41:50,487 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 16:41:50,489 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-c11 > 16:41:50,490 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0021: Registered web context: '/ws-c11' for server 'default-server' > 16:41:50,492 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithParticipantCompletionParticipantService.wsdl > 16:41:50,495 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 16:41:50,495 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 16:41:50,495 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 16:41:50,496 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-participant > 16:41:50,497 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: '/ws-t11-participant' for server 'default-server' > 16:41:50,502 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > 16:41:50,517 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithCoordinatorCompletionCoordinatorService.wsdl > 16:41:50,518 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > 16:41:50,522 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > 16:41:50,533 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithParticipantCompletionCoordinatorService.wsdl > 16:41:50,533 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from class com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > 16:41:50,537 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CoordinatorService > 16:41:50,544 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CoordinatorService.wsdl > 16:41:50,545 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorRPCService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > 16:41:50,549 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > 16:41:50,555 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorRPCService.wsdl > 16:41:50,560 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 16:41:50,560 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 16:41:50,561 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 16:41:50,561 INFO [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 16:41:50,561 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 16:41:50,561 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 16:41:50,561 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 16:41:50,564 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-coordinator > 16:41:50,565 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0021: Registered web context: '/ws-t11-coordinator' for server 'default-server' > 16:41:50,569 INFO [stdout] (MSC service thread 1-4) Rule.execute called for open trace file_2 > 16:41:50,570 INFO [stdout] (MSC service thread 1-4) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:50,570 INFO [stdout] (MSC service thread 1-4) calling installed(open trace file) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:50,570 INFO [stdout] (MSC service thread 1-4) Installed rule using default helper : open trace file > 16:41:50,570 INFO [stdout] (MSC service thread 1-4) open trace file execute > 16:41:50,570 INFO [stdout] (MSC service thread 1-4) Rule.execute called for create participant deletes counter_0 > 16:41:50,571 INFO [stdout] (MSC service thread 1-4) Rule.execute for decommissioned key create participant deletes counter_0 > 16:41:50,582 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace Participant send rollback in class com.arjuna.wst11.messaging.CoordinatorProcessorImpl > 16:41:50,583 INFO [stdout] (MSC service thread 1-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.CoordinatorProcessorImpl.prepared(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace Participant send rollback > 16:41:50,587 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace Participant send rollback in class com.arjuna.wst11.messaging.CoordinatorProcessorImpl > 16:41:50,607 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate coordinator close in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:50,607 INFO [stdout] (MSC service thread 1-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator.rollback() void for rule trace subordinate coordinator close > 16:41:50,608 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate coordinator close in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:50,609 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate coordinator prepare in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:50,609 INFO [stdout] (MSC service thread 1-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator.prepare() int for rule trace subordinate coordinator prepare > 16:41:50,610 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate coordinator prepare in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:50,611 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate coordinator rollback 2 in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:50,612 INFO [stdout] (MSC service thread 1-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator.rollback() void for rule trace subordinate coordinator rollback 2 > 16:41:50,613 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate coordinator rollback 2 in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:50,632 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace delete participant and exit JVM in class org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple > 16:41:50,633 INFO [stdout] (MSC service thread 1-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple.deleteParticipantRecoveryRecord(java.lang.String) boolean for rule trace delete participant and exit JVM > 16:41:50,634 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace delete participant and exit JVM in class org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple > 16:41:50,661 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033013: OutboundBridgeRecoveryManager starting > 16:41:50,661 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-4) ARJUNA033006: InboundBridgeRecoveryManager starting > 16:41:50,749 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000169: Jandex cannot distinguish inner and static nested classes! Update Jandex to 2.0.3.Final version or newer to improve scanning performance. > 16:41:51,008 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 73) Starting XTSServiceTestRunner > 16:41:51,008 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 73) Started XTSServiceTestRunner > 16:41:51,017 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 73) Initializing Mojarra 2.2.13.SP1 20160303-1204 for context '/xtstest' > 16:41:51,377 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0021: Registered web context: '/xtstest' for server 'default-server' > 16:41:51,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") > 16:41:51,391 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "restat-web-5.4.1.Final-SNAPSHOT.war" (runtime-name : "restat-web-5.4.1.Final-SNAPSHOT.war") > 16:41:51,449 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 16:41:51,449 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 16:41:51,450 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha12 "Kenny" started in 4409ms - Started 671 of 918 services (462 services are lazy, passive or on-demand) > Nov 15, 2016 4:41:51 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill > INFO: Hard killing of a server instance > Nov 15, 2016 4:41:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: waiting for byteman to kill the server > Nov 15, 2016 4:41:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:42:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:42:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:42:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:42:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > 16:42:18,935 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate prepared replay in class org.jboss.jbossts.xts.recovery.coordinator.at.RecoverySubordinateATCoordinator > 16:42:18,937 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.recovery.coordinator.at.RecoverySubordinateATCoordinator.replayPhase2() void for rule trace subordinate prepared replay > 16:42:18,938 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate prepared replay in class org.jboss.jbossts.xts.recovery.coordinator.at.RecoverySubordinateATCoordinator > 16:42:18,977 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace Coordinator engine create in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:18,978 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.(java.lang.String,boolean,javax.xml.ws.wsaddressing.W3CEndpointReference,boolean,com.arjuna.webservices11.wsat.State) void for rule trace Coordinator engine create > 16:42:18,991 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace Coordinator engine create in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:18,992 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive Participant aborted in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:18,992 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.aborted(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive Participant aborted > 16:42:19,002 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive Participant aborted in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,004 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive participant prepared in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,004 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.prepared(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive participant prepared > 16:42:19,015 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive participant prepared in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,017 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send participant prepare in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,018 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.prepare() com.arjuna.webservices11.wsat.State for rule trace send participant prepare > 16:42:19,028 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace send participant prepare in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,029 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send Participant rollback in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,030 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.rollback() com.arjuna.webservices11.wsat.State for rule trace send Participant rollback > 16:42:19,040 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace send Participant rollback in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,042 INFO [stdout] (Periodic Recovery) Rule.execute called for trace Coordinator engine create_12 > 16:42:19,042 INFO [stdout] (Periodic Recovery) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,042 INFO [stdout] (Periodic Recovery) calling installed(trace Coordinator engine create) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,042 INFO [stdout] (Periodic Recovery) Installed rule using default helper : trace Coordinator engine create > 16:42:19,042 INFO [stdout] (Periodic Recovery) trace Coordinator engine create execute > 16:42:19,043 INFO [stdout] (Periodic Recovery) rule.debug{trace Coordinator engine create} : created recovered Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:20 > 16:42:19,054 INFO [stdout] (Periodic Recovery) Rule.execute called for trace Coordinator engine create_12 > 16:42:19,054 INFO [stdout] (Periodic Recovery) trace Coordinator engine create execute > 16:42:19,054 INFO [stdout] (Periodic Recovery) rule.debug{trace Coordinator engine create} : created recovered Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:23 > 16:42:19,054 INFO [stdout] (Periodic Recovery) Rule.execute called for trace subordinate prepared replay_11 > 16:42:19,057 INFO [stdout] (Periodic Recovery) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,057 INFO [stdout] (Periodic Recovery) calling installed(trace subordinate prepared replay) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,057 INFO [stdout] (Periodic Recovery) Installed rule using default helper : trace subordinate prepared replay > 16:42:19,057 INFO [stdout] (Periodic Recovery) trace subordinate prepared replay execute > 16:42:19,057 INFO [stdout] (Periodic Recovery) rule.debug{trace subordinate prepared replay} : reinstated prepared subordinate transaction 0:ffffac110007:-3ffa9bb3:582b3abd:19 > 16:42:19,062 INFO [stdout] (Periodic Recovery) xts service test : attempting to deserialize WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:42:19,064 INFO [stdout] (Periodic Recovery) xts service test : deserialized WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:42:19,065 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace Participant create in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,066 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.(com.arjuna.wst.Participant,java.lang.String,com.arjuna.webservices11.wsat.State,javax.xml.ws.wsaddressing.W3CEndpointReference,boolean) void for rule trace Participant create > 16:42:19,078 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace Participant create in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,079 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive participant prepare in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,079 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.prepare(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive participant prepare > 16:42:19,086 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive participant prepare in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,087 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send Participant prepared in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,093 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.sendPrepared(boolean) void for rule trace send Participant prepared > 16:42:19,093 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace send Participant prepared in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,095 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive Participant rollback in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,096 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.rollback(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive Participant rollback > 16:42:19,102 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive Participant rollback in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,103 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send Participant aborted in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,109 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.sendAborted() void for rule trace send Participant aborted > 16:42:19,109 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace send Participant aborted in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,111 INFO [stdout] (Periodic Recovery) Rule.execute called for trace Participant create_17 > 16:42:19,111 INFO [stdout] (Periodic Recovery) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,111 INFO [stdout] (Periodic Recovery) calling installed(trace Participant create) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,111 INFO [stdout] (Periodic Recovery) Installed rule using default helper : trace Participant create > 16:42:19,111 INFO [stdout] (Periodic Recovery) trace Participant create execute > 16:42:19,111 INFO [stdout] (Periodic Recovery) rule.debug{trace Participant create} : created recovered Participant engine org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:42:19,118 INFO [stdout] (Periodic Recovery) Rule.execute called for trace send Participant prepared_19 > 16:42:19,118 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace send Participant prepared_19 > 16:42:19,227 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Periodic Recovery) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:42:19,520 INFO [stdout] (Periodic Recovery) xts service test : attempting to deserialize WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:42:19,520 INFO [stdout] (Periodic Recovery) xts service test : deserialized WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:42:19,520 INFO [stdout] (Periodic Recovery) Rule.execute called for trace Participant create_17 > 16:42:19,520 INFO [stdout] (Periodic Recovery) trace Participant create execute > 16:42:19,520 INFO [stdout] (Periodic Recovery) rule.debug{trace Participant create} : created recovered Participant engine org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:42:19,521 INFO [stdout] (Periodic Recovery) Rule.execute called for trace send Participant prepared_19 > 16:42:19,521 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace send Participant prepared_19 > 16:42:19,530 INFO [stdout] (TaskWorker-1) Rule.execute called for trace receive participant prepared_14 > 16:42:19,530 INFO [stdout] (TaskWorker-1) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,530 INFO [stdout] (TaskWorker-1) calling installed(trace receive participant prepared) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,531 INFO [stdout] (TaskWorker-1) Installed rule using default helper : trace receive participant prepared > 16:42:19,531 INFO [stdout] (TaskWorker-1) trace receive participant prepared execute > 16:42:19,531 INFO [stdout] (TaskWorker-1) rule.debug{trace receive participant prepared} : prepared received for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:23 > 16:42:19,532 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Periodic Recovery) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:42:19,550 INFO [stdout] (Periodic Recovery) xts service test : attempting to deserialize WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:42:19,550 INFO [stdout] (Periodic Recovery) xts service test : deserialized WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:42:19,551 INFO [stdout] (TaskWorker-1) Rule.execute called for trace receive participant prepared_14 > 16:42:19,551 INFO [stdout] (Periodic Recovery) Rule.execute called for trace Participant create_17 > 16:42:19,551 INFO [stdout] (TaskWorker-1) trace receive participant prepared execute > 16:42:19,551 INFO [stdout] (Periodic Recovery) trace Participant create execute > 16:42:19,551 INFO [stdout] (TaskWorker-1) rule.debug{trace receive participant prepared} : prepared received for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:20 > 16:42:19,551 INFO [stdout] (Periodic Recovery) rule.debug{trace Participant create} : created recovered Participant engine org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:42:19,551 INFO [stdout] (Periodic Recovery) Rule.execute called for trace send Participant prepared_19 > 16:42:19,551 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace send Participant prepared_19 > 16:42:19,560 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Periodic Recovery) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:42:19,576 WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046033: Compensating orphaned subordinate WS-AT transcation 0:ffffac110007:-3ffa9bb3:582b3abd:19 > 16:42:19,576 INFO [stdout] (Periodic Recovery) Rule.execute called for trace subordinate coordinator close_7 > 16:42:19,576 INFO [stdout] (Periodic Recovery) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,577 INFO [stdout] (Periodic Recovery) calling installed(trace subordinate coordinator close) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,577 INFO [stdout] (Periodic Recovery) Installed rule using default helper : trace subordinate coordinator close > 16:42:19,577 INFO [stdout] (Periodic Recovery) trace subordinate coordinator close execute > 16:42:19,577 INFO [stdout] (Periodic Recovery) rule.debug{trace subordinate coordinator close} : rollback called for subordinate coordinator BasicAction: 0:ffffac110007:-3ffa9bb3:582b3abd:19 status: ActionStatus.COMMITTING > 16:42:19,577 INFO [stdout] (Periodic Recovery) Rule.execute called for trace send Participant rollback_16 > 16:42:19,577 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace send Participant rollback_16 > 16:42:19,583 WARN [com.arjuna.wst] (TaskWorker-1) ARJUNA043134: Prepared called on unknown coordinator: D0:ffffac110007:-3ffa9bb3:582b3abd:16 > 16:42:19,583 INFO [stdout] (TaskWorker-1) Rule.execute called for trace Participant send rollback_6 > 16:42:19,583 INFO [stdout] (TaskWorker-1) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,583 INFO [stdout] (TaskWorker-1) calling installed(trace Participant send rollback) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,583 INFO [stdout] (TaskWorker-1) Installed rule using default helper : trace Participant send rollback > 16:42:19,584 INFO [stdout] (TaskWorker-1) trace Participant send rollback execute > 16:42:19,584 INFO [stdout] (TaskWorker-1) rule.debug{trace Participant send rollback} : sent rollback for unknown Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:16 > 16:42:19,588 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:42:19,599 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Periodic Recovery) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:42:19,600 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:42:19,638 INFO [stdout] (TaskWorker-1) Rule.execute called for trace receive Participant rollback_20 > 16:42:19,638 INFO [stdout] (TaskWorker-1) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,638 INFO [stdout] (TaskWorker-1) calling installed(trace receive Participant rollback) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,638 INFO [stdout] (TaskWorker-1) Installed rule using default helper : trace receive Participant rollback > 16:42:19,638 INFO [stdout] (TaskWorker-1) trace receive Participant rollback execute > 16:42:19,639 INFO [stdout] (TaskWorker-1) rule.debug{trace receive Participant rollback} : rollback received for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:42:19,639 INFO [stdout] (TaskWorker-1) Rule.execute called for trace delete participant and exit JVM_10 > 16:42:19,639 INFO [stdout] (TaskWorker-1) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,639 INFO [stdout] (TaskWorker-1) calling installed(trace delete participant and exit JVM) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,639 INFO [stdout] (TaskWorker-1) Installed rule using default helper : trace delete participant and exit JVM > 16:42:19,639 INFO [stdout] (TaskWorker-1) trace delete participant and exit JVM execute > 16:42:19,640 INFO [stdout] (TaskWorker-1) Rule.execute called for trace send Participant aborted_21 > 16:42:19,640 INFO [stdout] (TaskWorker-1) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,640 INFO [stdout] (TaskWorker-1) calling installed(trace send Participant aborted) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,640 INFO [stdout] (TaskWorker-1) Installed rule using default helper : trace send Participant aborted > 16:42:19,640 INFO [stdout] (TaskWorker-1) trace send Participant aborted execute > 16:42:19,640 INFO [stdout] (TaskWorker-1) rule.debug{trace send Participant aborted} : aborted sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:42:19,650 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:42:19,667 INFO [stdout] (TaskWorker-1) Rule.execute called for trace receive Participant rollback_20 > 16:42:19,668 INFO [stdout] (TaskWorker-1) trace receive Participant rollback execute > 16:42:19,668 INFO [stdout] (TaskWorker-1) rule.debug{trace receive Participant rollback} : rollback received for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:42:19,669 INFO [stdout] (TaskWorker-1) Rule.execute called for trace delete participant and exit JVM_10 > 16:42:19,669 INFO [stdout] (TaskWorker-1) trace delete participant and exit JVM execute > 16:42:19,669 INFO [stdout] (TaskWorker-1) Rule.execute called for trace send Participant aborted_21 > 16:42:19,670 INFO [stdout] (TaskWorker-1) trace send Participant aborted execute > 16:42:19,669 WARN [com.arjuna.wst] (TaskWorker-2) ARJUNA043130: Aborted called on unknown coordinator: D0:ffffac110007:-3ffa9bb3:582b3abd:16 > 16:42:19,670 INFO [stdout] (TaskWorker-1) rule.debug{trace send Participant aborted} : aborted sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:42:19,678 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:42:19,694 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive Participant aborted_13 > 16:42:19,694 INFO [stdout] (TaskWorker-2) Rule.execute for decommissioned key trace receive Participant aborted_13 > 16:42:19,694 INFO [stdout] (Periodic Recovery) Rule.execute called for trace send Participant rollback_16 > 16:42:19,694 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace send Participant rollback_16 > 16:42:19,710 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Periodic Recovery) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:42:19,728 INFO [stdout] (TaskWorker-1) Rule.execute called for trace receive Participant rollback_20 > 16:42:19,728 INFO [stdout] (TaskWorker-1) trace receive Participant rollback execute > 16:42:19,729 INFO [stdout] (TaskWorker-1) rule.debug{trace receive Participant rollback} : rollback received for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:42:19,729 INFO [stdout] (TaskWorker-1) Rule.execute called for trace delete participant and exit JVM_10 > 16:42:19,729 INFO [stdout] (TaskWorker-1) trace delete participant and exit JVM execute > 16:42:19,729 INFO [stdout] (TaskWorker-1) Rule.execute called for trace send Participant aborted_21 > 16:42:19,729 INFO [stdout] (TaskWorker-1) trace send Participant aborted execute > 16:42:19,730 INFO [stdout] (TaskWorker-1) rule.debug{trace send Participant aborted} : aborted sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:42:19,738 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:42:19,752 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive Participant aborted_13 > 16:42:19,752 INFO [stdout] (TaskWorker-2) Rule.execute for decommissioned key trace receive Participant aborted_13 > 16:42:19,753 INFO [stdout] (Periodic Recovery) Rule.execute called for trace remove committed state_5 > 16:42:19,753 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace remove committed state_5 > 16:42:19,753 INFO [stdout] (Periodic Recovery) Rule.execute called for trace remove committed state and exit JVM_4 > 16:42:19,753 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace remove committed state and exit JVM_4 > 16:42:19,753 INFO [stdout] (Periodic Recovery) Rule.execute called for trace subordinate coordinator rollback 2_9 > 16:42:19,754 INFO [stdout] (Periodic Recovery) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,754 INFO [stdout] (Periodic Recovery) calling installed(trace subordinate coordinator rollback 2) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,754 INFO [stdout] (Periodic Recovery) Installed rule using default helper : trace subordinate coordinator rollback 2 > 16:42:19,754 INFO [stdout] (Periodic Recovery) trace subordinate coordinator rollback 2 execute > 16:42:19,754 INFO [stdout] (Periodic Recovery) rule.debug{trace subordinate coordinator rollback 2} : rollback returned for subordinate coordinator BasicAction: 0:ffffac110007:-3ffa9bb3:582b3abd:19 status: ActionStatus.ABORTED > Nov 15, 2016 4:42:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:42:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:42:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:42:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:42:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:42:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:42:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:42:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:43:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:43:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:43:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:43:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:43:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:43:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:43:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:43:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:43:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:43:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:43:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:43:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:44:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:44:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:44:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:44:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:44:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:44:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:44:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:44:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:44:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:44:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:44:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:44:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:45:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:45:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:45:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:45:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:45:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:45:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:45:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:45:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:45:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:45:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:45:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:45:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:46:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:46:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:46:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:46:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:46:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:46:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:46:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:46:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:46:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:46:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:46:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:46:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:47:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:47:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:47:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:47:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:47:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:47:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:47:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:47:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:47:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:47:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:47:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:47:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:48:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:48:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:48:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:48:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:48:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:48:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:48:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:48:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:48:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:48:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:48:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:48:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:49:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:49:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:49:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:49:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:49:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:49:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:49:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:49:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:49:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:49:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:49:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:49:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:50:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:50:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:50:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:50:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:50:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:50:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:50:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:50:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:50:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:50:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:50:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:50:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:51:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:51:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:51:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:51:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:51:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:51:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:51:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:51:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:51:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:51:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:51:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:51:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommand > INFO: Executing shell command: 'ps aux | grep jboss-module[s] | awk '{print $2}' | xargs kill' > Nov 15, 2016 4:51:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > 16:51:51,969 INFO [org.jboss.as.server] (Thread-3) WFLYSRV0220: Server shutdown has been requested via an OS signal > 16:51:51,982 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-6) ARJUNA033007: InboundBridgeRecoveryManager stopping > 16:51:51,982 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 16:51:51,982 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-7) ARJUNA033014: OutboundBridgeRecoveryManager stopping > 16:51:51,984 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > 16:51:51,984 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 77) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 16:51:51,990 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0022: Unregistered web context: '/rest-tx' from server 'default-server' > 16:51:51,990 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 80) WFLYUT0022: Unregistered web context: '/xtstest' from server 'default-server' > 16:51:51,996 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 80) Stopping XTSServiceTestRunner > 16:51:51,996 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 80) Stopped XTSServiceTestRunner > 16:51:51,997 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 16:51:51,997 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 16:51:51,998 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 16:51:51,998 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 16:51:52,012 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 16:51:52,013 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 16:51:52,017 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 78) AMQ151003: resource adaptor stopped > 16:51:52,026 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment restat-web-5.4.1.Final-SNAPSHOT.war (runtime-name: restat-web-5.4.1.Final-SNAPSHOT.war) in 50ms > 16:51:52,031 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment xtstest.war (runtime-name: xtstest.war) in 56ms > 16:51:52,053 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.5.0 [ef9290cb-ab4d-11e6-b97f-0242ac110007] stopped, uptime 10 minutes > Nov 15, 2016 4:51:56 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > 16:51:59,834 WARN [org.apache.activemq.artemis.service.extensions.xa.recovery] (Periodic Recovery) AMQ122015: Can not connect to XARecoveryConfig [transportConfiguration=[TransportConfiguration(name=, factory=org-apache-activemq-artemis-core-remoting-impl-invm-InVMConnectorFactory) ?serverId=0], discoveryConfiguration=null, username=null, password=****, JNDI_NAME=java:/JmsXA] on auto-generated resource recovery: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:785) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.connect(ActiveMQXAResourceWrapper.java:311) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.getDelegate(ActiveMQXAResourceWrapper.java:239) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.recover(ActiveMQXAResourceWrapper.java:69) > at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.recover(ActiveMQXAResourceWrapperImpl.java:106) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:770) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:461) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:218) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) > 16:51:59,834 WARN [org.apache.activemq.artemis.service.extensions.xa.recovery] (Periodic Recovery) AMQ122008: XA Recovery can not connect to any broker on recovery [XARecoveryConfig [transportConfiguration=[TransportConfiguration(name=, factory=org-apache-activemq-artemis-core-remoting-impl-invm-InVMConnectorFactory) ?serverId=0], discoveryConfiguration=null, username=null, password=****, JNDI_NAME=java:/JmsXA]] > 16:51:59,835 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMFAIL: javax.transaction.xa.XAException: Error trying to connect to any providers for xa recovery > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.getDelegate(ActiveMQXAResourceWrapper.java:258) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.recover(ActiveMQXAResourceWrapper.java:69) > at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.recover(ActiveMQXAResourceWrapperImpl.java:106) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:770) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:461) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:218) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=null] > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.connect(ActiveMQXAResourceWrapper.java:345) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.getDelegate(ActiveMQXAResourceWrapper.java:239) > ... 7 more > 16:51:59,836 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-coordinator > 16:51:59,836 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-c11 > 16:51:59,836 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-client > 16:51:59,836 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-participant > 16:51:59,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0022: Unregistered web context: '/ws-t11-coordinator' from server 'default-server' > 16:51:59,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: '/ws-c11' from server 'default-server' > 16:51:59,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0022: Unregistered web context: '/ws-t11-participant' from server 'default-server' > 16:51:59,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0022: Unregistered web context: '/ws-t11-client' from server 'default-server' > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 16:51:59,838 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 16:51:59,838 INFO [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 16:51:59,838 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-c11 > 16:51:59,838 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-coordinator > 16:51:59,838 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-client > 16:51:59,838 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-participant > 16:51:59,838 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0019: Host default-host stopping > 16:51:59,841 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0008: Undertow HTTP listener default suspending > 16:51:59,841 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HTTPS listener https suspending > 16:51:59,841 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 16:51:59,841 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HTTPS listener https stopped, was bound to 127.0.0.1:8443 > 16:51:59,842 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0004: Undertow 1.4.4.Final stopping > 16:51:59,849 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0050: WildFly Core 3.0.0.Alpha12 "Kenny" stopped in 7870ms > Nov 15, 2016 4:52:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:52:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor shutdownJBoss > INFO: jboss-as shutdown after sending shutdown command > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:03:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:03:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2897) Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2897. ------------------------------- > Calling TransactionImple to register synchronization with null parameter causes NullPointerException being thrown when trace logging is enabled > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2897 > URL: https://issues.jboss.org/browse/JBTM-2897 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.6.0.Final > > > If trace logging is enabled then call on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple#registerSynchronization}} is done with {{null}} in parameter then {{NullPointerException}} is thrown but {{SystemException}} should be thrown in such case. > https://github.com/jbosstm/narayana/blob/930bd7f17f1b0cc2b8529eaa2ae1fcacf9582ac5/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L452 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:03:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:03:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2896) Invalid warning when committing STM optimistic records In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2896. ------------------------------- > Invalid warning when committing STM optimistic records > ------------------------------------------------------ > > Key: JBTM-2896 > URL: https://issues.jboss.org/browse/JBTM-2896 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.5.24.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.6.0.Final > > > There is some code in OptimisticLockRecord#topLevelCommit that generates an invalid warning > bq. WARN: ARJUNA015051: OptimisticLockRecord.topLevelCommit state check failed for org.jboss.stm.internal.proxy.OptimisticLockManagerProxy at 7f058cfa will force rollback. > when in fact there is no rollback. The offending code is: > {code} > public int topLevelCommit () > { > boolean stateOK = checkState(); > > if (stateOK) > { > txojLogger.i18NLogger.warn_OptimisticLockRecord_2((LockManager) value()); > } > {code} > The condition was intended to be if (!stateOK) -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:03:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:03:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2892) Calling Subordinate transaction to enlist with empty parameter list ends with IndexOutOfBoundsException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2892. ------------------------------- > Calling Subordinate transaction to enlist with empty parameter list ends with IndexOutOfBoundsException > ------------------------------------------------------------------------------------------------------- > > Key: JBTM-2892 > URL: https://issues.jboss.org/browse/JBTM-2892 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.6.0.Final > > > When calling enlist method on {{com.arjuna.ats.internal.jta.transaction.jts.TransactionImple}} when parameters are defined as empty array the {{IndexOutOfBoundsException}} exception is thrown. > The method call I do refer to is > https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L517 -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:03:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:03:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2893) JTS subordinate transaction could check Xid format during enlistment to allow it being edited In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2893. ------------------------------- > JTS subordinate transaction could check Xid format during enlistment to allow it being edited > --------------------------------------------------------------------------------------------- > > Key: JBTM-2893 > URL: https://issues.jboss.org/browse/JBTM-2893 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Affects Versions: 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 5.6.0.Final > > > When a subordinate transaction created by Narayana is imported in JTS it's capable to correctly handle only one XAResource being enlisted. When two or more resources are enlisted they all contain the same Xid. That Xid came from what {{TransactionImple}} defines (here is call which is never reached by such txn code: https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3a39e3bc9/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java#L1760) > That behavior is fine when txn is imported from EIS but when is managed by Narayana it should not be problem to generate Xids for each XAResource unique. > That behavior makes the issue when recovery should be part of handling. All the resources are "merged" under one record in object log store. That way can't be recovered correctly. > This handling is "fixed" in JTA (see https://github.com/jbosstm/narayana/blob/a8f8df24d6531e6ba83cc3746ce05fc3a39e3bc9/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/subordinate/TransactionImple.java#L359) where format of xid is checked when enlistment happens. Such thing could be passed to JTS mode too. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:03:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:03:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2890) asyncAfterSynchronization throw exception when transaction abort In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2890. ------------------------------- > asyncAfterSynchronization throw exception when transaction abort > ---------------------------------------------------------------- > > Key: JBTM-2890 > URL: https://issues.jboss.org/browse/JBTM-2890 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.5.0.Final, 5.5.24.Final > Reporter: Colin Song > Assignee: Tom Jenkinson > Fix For: 5.6.0.Final > > > *The problem:* > There's two problems about asyncAfterSynchronization(com.arjuna.ats.arjuna.coordinator.asyncAfterSynchronization=true) option: > * If we want asyncAfterSynchronization, we must set asyncBeforeSynchronization > * When tx abort, and we have asyncAfterSynchronization option, there's exception > *Root cause:* {{TwoPhaseCoordinator.synchronizationCompletionService}} and {{TwoPhaseCoordinator.runningSynchronizations}} only inited in {{asyncBeforeSynchronization}} > *Solution:* > Also init {{TwoPhaseCoordinator.synchronizationCompletionService}} and {{TwoPhaseCoordinator.runningSynchronizations}} in asyncAfterSynchronization -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2885) Orphan detection may attempt to rollback orphan if resource fails to return values In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2885. ------------------------------- > Orphan detection may attempt to rollback orphan if resource fails to return values > ---------------------------------------------------------------------------------- > > Key: JBTM-2885 > URL: https://issues.jboss.org/browse/JBTM-2885 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 5.6.0.Final > > > If the XAR returns a Xid from recover(FIRST_PASS) to XARM but then goes offline for a cycle we may attempt to rollback the Xid thinking it is stale. If the XAR returns an XAE at that point we should clear the _xidScans so we pick it up next time. > However, there is a filter that checks for transaction state (JTATransactionLogXAResourceOrphanFilter) which would detect a transaction log and ignore this Xid so adding this protection would only be considered belt-and-braces. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2881) STM InvocationHandler swallows application exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2881. ------------------------------- > STM InvocationHandler swallows application exceptions > ----------------------------------------------------- > > Key: JBTM-2881 > URL: https://issues.jboss.org/browse/JBTM-2881 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.5.6.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.6.0.Final > > > The STM implementation intercepts calls on transactional objects (ones that implement interfaces marked with the @Transactional annotation). If the application object throws a business exception it is wrapped in an java.lang.reflect.InvocationTargetException and this is raised. Application code is written to anticipate business exceptions but not java.lang.reflect.InvocationTargetException. > The fix is throw the wrapped business exception instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2889) Include a vertx with STM quickstart In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2889. ------------------------------- > Include a vertx with STM quickstart > ----------------------------------- > > Key: JBTM-2889 > URL: https://issues.jboss.org/browse/JBTM-2889 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, STM > Affects Versions: 5.5.24.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.6.0.Final > > > It would be useful to include a quickstart that shows how to use STM with vertx -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2874) WildFly to GlassFish interop: Add a quickstart that shows transaction propagation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2874. ------------------------------- > WildFly to GlassFish interop: Add a quickstart that shows transaction propagation > --------------------------------------------------------------------------------- > > Key: JBTM-2874 > URL: https://issues.jboss.org/browse/JBTM-2874 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator > Affects Versions: 5.5.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.6.0.Final > > > Currently both app servers need patching. The quickstart will demonstrate: > # how to patch the servers; > # link to the WidFly and GlassFish JIRAs that stop interop from working; > # show how to configure and run transactional ejb calls between the two servers > A follow up quickstart will demonstrate recovery -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2868) CoordinationContextHelper needs additional privileged blocks if Security Manager is enabled In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2868. ------------------------------- > CoordinationContextHelper needs additional privileged blocks if Security Manager is enabled > ------------------------------------------------------------------------------------------- > > Key: JBTM-2868 > URL: https://issues.jboss.org/browse/JBTM-2868 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.5.5.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 5.5.6.Final, 5.6.0.Final > > > CoordinationContextHelper needs additional privileged blocks when running with Security Manager enabled. JBTM-2519 has enclosed setContextClassLoader with a privileged block, but getContextClassLoader needs the privileged block too, see the attached PR. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2871) BlackTie core does not compile on Fedora 25 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2871. ------------------------------- > BlackTie core does not compile on Fedora 25 > ------------------------------------------- > > Key: JBTM-2871 > URL: https://issues.jboss.org/browse/JBTM-2871 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.5.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.6.0.Final > > > BlackTie core no longer compiles after upgrading to Fedora 25 (from Fedora 23). The error is in the STL: > {code} > [cc] /home/mmusgrov/work/source/forks/narayana/master/blacktie/core/src/main/cpp/ThreadLocalStorage.cxx:52:87: error: no matching function for call to 'make_pair(apr_os_thread_t&, apr_pool_t*&)' > [cc] tls_pools.insert(std::make_pair(os_th,tls_pool)); > {code} > The fix is to let the library infer the types of the pair being inserted, ie: > {code} > tls_pools.insert(std::make_pair(os_th,tls_pool)); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2879) JTS before_completion in SynchronizationImple swallows and hides exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2879. ------------------------------- > JTS before_completion in SynchronizationImple swallows and hides exceptions > --------------------------------------------------------------------------- > > Key: JBTM-2879 > URL: https://issues.jboss.org/browse/JBTM-2879 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTS > Reporter: David Lloyd > Assignee: Ondra Chaloupka > Fix For: 5.5.7.Final, 5.6.0.Final > > > In [SynchronizationImple|https://github.com/jbosstm/narayana/blob/781ace284d840805282e037e9c10c8de6f2de472/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/resources/jts/orbspecific/SynchronizationImple.java#L93], if the user's synchronization fails, the exception is swallowed and never logged. Instead a descriptionless {{UNKNOWN}} is thrown. > The exception should at least be logged to aid in troubleshooting. > Later in the same file, {{after_completion}} is using {{e.printStackTrace()}} to log the stack, which is also less than ideal. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2869) Deprecate SPI transaction event notifications In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2869. ------------------------------- > Deprecate SPI transaction event notifications > --------------------------------------------- > > Key: JBTM-2869 > URL: https://issues.jboss.org/browse/JBTM-2869 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Affects Versions: 5.5.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.6.0.Final > > > The SPI API for monitoring thread to transaction association changes needs deprecating. It was introduced in JBTM-2343 (Interface for tracking thread/transaction association changes) and WFLY-4923. > The ability to listen for such changes has been re implemented by WFTC (see WFLY commit 7ef53b800:- Updated EJB client integration: Fixes to start bringing Transactions, EJB, and Discovery together) so we should stop generating these events. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2870) Provide way of getting suppressed exceptions out of SubordinateTransaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2870. ------------------------------- > Provide way of getting suppressed exceptions out of SubordinateTransaction > -------------------------------------------------------------------------- > > Key: JBTM-2870 > URL: https://issues.jboss.org/browse/JBTM-2870 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 4.17.38, 5.5.5.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 4.17.40, 5.2.23.Final, 5.5.7.Final, 5.6.0.Final > > > We need to provide way how to pass suppressed exceptions of of the `SubordinateTransaction` to the caller. > This request came from customer case and https://bugzilla.redhat.com/show_bug.cgi?id=1435549 as we need to provide exceptions thrown from transaction resource. > The interface is used for controlling propagated transaction from one server to another in EAP/WFLY. > Callers are is ejb3 subsystem in EAP 6.4/7.0 and WFTC in EAP 7.1. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:01 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2878) Quickstarts not running in CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2878. ------------------------------- > Quickstarts not running in CI > ----------------------------- > > Key: JBTM-2878 > URL: https://issues.jboss.org/browse/JBTM-2878 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.5.6.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.6.0.Final > > > The script that is meant to run the quickstarts (scripts/hudson/quickstart.sh) is not running them for the following reason: the script clones narayana and changes directory into it to build it but does not change directory back into the quickstart directory before running ./build.sh clean install and consequently it just ends up doing a second rebuild of narayana instead. > Also JENKINS_HOST is missing a userConotent directory so the following call will fail the build > wget http://${JENKINS_HOST}/userConotent/blacktie-thirdparty-centos70x64.tgz -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2793) TestATSubordinateCrashDuringPrepare failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2793. ------------------------------- > TestATSubordinateCrashDuringPrepare failure > ------------------------------------------- > > Key: JBTM-2793 > URL: https://issues.jboss.org/browse/JBTM-2793 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.6.0.Final > > > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/13/ > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 630.486 sec <<< FAILURE! - in com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare > subordinateMultiParticipantPrepareAndCommitTest(com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare) Time elapsed: 630.486 sec <<< ERROR! > java.lang.RuntimeException: jboss-as was not killed by Byteman, this indicates a test failure > at com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare.subordinateMultiParticipantPrepareAndCommitTest(TestATSubordinateCrashDuringPrepare.java:17) > {code} > {code} > Starting arquillian with java VM args: -server -Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dorg.jboss.byteman.verbose > -Djboss.modules.system.pkgs=org.jboss.byteman > -Dorg.jboss.byteman.transform.all > -javaagent:/home/jenkins/workspace/narayana-codeCoverage/XTS/localjunit/crash-recovery-tests/target/lib/byteman.jar=script:target/test-classes/scripts/ATSubordinateCrashDuringPrepare.btm,boot:target/lib/byteman.jar,listener:true isIPv6: false > Deleting: /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/tx-object-store > remove tx-object-store: /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/tx-object-store > remove /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/content/75 > remove /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/content/d8 > copy /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/docs/examples/configs/standalone-xts.xml to /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration/standalone-xts.xml > Nov 15, 2016 4:41:31 PM com.arjuna.qa.junit.BaseCrashTest runTest > INFO: Test starting, server should be down: ATSubordinateCrashDuringPrepare:subordinate.MultiParticipantPrepareAndCommitTest > Nov 15, 2016 4:41:31 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance with overridden configuration. New configuration: {managementAddress=127.0.0.1, javaVmArguments=-server -Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dorg.jboss.byteman.verbose > -Djboss.modules.system.pkgs=org.jboss.byteman > -Dorg.jboss.byteman.transform.all > -javaagent:/home/jenkins/workspace/narayana-codeCoverage/XTS/localjunit/crash-recovery-tests/target/lib/byteman.jar=script:target/test-classes/scripts/ATSubordinateCrashDuringPrepare.btm,boot:target/lib/byteman.jar,listener:true -Dorg.jboss.jbossts.xts.servicetests.XTSServiceTestName=org.jboss.jbossts.xts.servicetests.test.at.subordinate.MultiParticipantPrepareAndCommitTest, startupTimeoutInSeconds=60, serverConfig=standalone-xts.xml} > Nov 15, 2016 4:41:31 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > Nov 15, 2016 4:41:31 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/lib/jvm/java-1.8.0-openjdk/bin/java, -D[Standalone], -server, -Xms64m, -Xmx1024m, -XX:MaxPermSize=512m, -Dorg.jboss.byteman.verbose, -Djboss.modules.system.pkgs=org.jboss.byteman, -Dorg.jboss.byteman.transform.all, -javaagent:/home/jenkins/workspace/narayana-codeCoverage/XTS/localjunit/crash-recovery-tests/target/lib/byteman.jar=script:target/test-classes/scripts/ATSubordinateCrashDuringPrepare.btm,boot:target/lib/byteman.jar,listener:true, -Dorg.jboss.jbossts.xts.servicetests.XTSServiceTestName=org.jboss.jbossts.xts.servicetests.test.at.subordinate.MultiParticipantPrepareAndCommitTest, -ea, -Djboss.home.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/jboss-modules.jar, -mp, /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT, -Djboss.server.base.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration, -c=standalone-xts.xml] > OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 16:41:31,887 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta3 > 16:41:32,074 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.Final > 16:41:32,173 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Core 3.0.0.Alpha12 "Kenny" starting > 16:41:32,321 INFO [org.jboss.as.domain.management] (MSC service thread 1-8) WFLYDM0136: Registered OpenSSL provider > 16:41:33,042 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 13) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 16:41:33,066 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 25) WFLYDR0001: Content added at location /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/content/75/4c26bdb7730dd705b361ba38f432c0cfa843bd/content > 16:41:33,084 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 16:41:33,095 INFO [org.xnio] (MSC service thread 1-4) XNIO version 3.4.1.Final > 16:41:33,101 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.4.1.Final > 16:41:33,119 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 40) WFLYCLINF0001: Activating Infinispan subsystem. > 16:41:33,121 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 39) WFLYIO001: Worker 'default' has auto-configured to 48 core threads with 384 task threads based on your 24 available processors > 16:41:33,132 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 47) WFLYJSF0007: Activated the following JSF Implementations: [main] > 16:41:33,135 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem > 16:41:33,135 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 41) WFLYIIOP0001: Activating IIOP Subsystem > 16:41:33,135 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 59) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 16:41:33,139 INFO [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem > 16:41:33,139 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 61) WFLYWS0002: Activating WebServices Extension > 16:41:33,150 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 16:41:33,152 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = h2 > 16:41:33,155 INFO [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final) > 16:41:33,158 INFO [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=5.0.0.Alpha3 > 16:41:33,185 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : possible trigger for rule create participant deletes counter in class org.jboss.jbossts.XTSService > 16:41:33,191 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Undertow 1.4.4.Final starting > 16:41:33,196 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 5.0.0.Beta7 > 16:41:33,201 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 16:41:33,201 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service > 16:41:33,201 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule reset periodic recovery wait time in class com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean > 16:41:33,220 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getPeriodicRecoveryPeriod() int for rule reset periodic recovery wait time > 16:41:33,221 INFO [stdout] (ServerService Thread Pool -- 63) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.XTSService.start() void for rule create participant deletes counter > 16:41:33,237 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : inserted trigger for create participant deletes counter in class org.jboss.jbossts.XTSService > 16:41:33,238 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : possible trigger for rule open trace file in class org.jboss.jbossts.XTSService > 16:41:33,239 INFO [stdout] (ServerService Thread Pool -- 63) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.XTSService.start() void for rule open trace file > 16:41:33,241 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for reset periodic recovery wait time in class com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean > 16:41:33,243 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : inserted trigger for open trace file in class org.jboss.jbossts.XTSService > 16:41:33,260 INFO [org.wildfly.security] (MSC service thread 1-4) ELY00001: WildFly Elytron version 1.1.0.Beta13 > 16:41:33,278 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 384 (per class), which is derived from thread worker pool sizing. > 16:41:33,278 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 96 (per class), which is derived from the number of CPUs on this host. > 16:41:33,284 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0014: Creating file handler for path '/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 16:41:33,286 INFO [stdout] (MSC service thread 1-2) Rule.execute called for reset periodic recovery wait time_0 > 16:41:33,289 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server. > 16:41:33,289 INFO [stdout] (MSC service thread 1-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:33,289 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: Host default-host starting > 16:41:33,289 INFO [stdout] (MSC service thread 1-2) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 16:41:33,290 INFO [stdout] (MSC service thread 1-2) Default helper activated > 16:41:33,291 INFO [stdout] (MSC service thread 1-2) calling installed(reset periodic recovery wait time) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:33,291 INFO [stdout] (MSC service thread 1-2) Installed rule using default helper : reset periodic recovery wait time > 16:41:33,291 INFO [stdout] (MSC service thread 1-2) reset periodic recovery wait time execute > 16:41:33,295 INFO [stdout] (MSC service thread 1-2) caught ReturnException > 16:41:33,322 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule trace TX save at prepare in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:33,351 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(boolean) int for rule trace TX save at prepare > 16:41:33,355 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for trace TX save at prepare in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:33,356 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 16:41:33,360 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule trace remove committed state and exit JVM in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:33,379 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.coordinator.BasicAction.updateState() void for rule trace remove committed state and exit JVM > 16:41:33,382 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for trace remove committed state and exit JVM in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:33,386 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : possible trigger for rule trace remove committed state in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:33,424 INFO [stdout] (MSC service thread 1-2) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.coordinator.BasicAction.updateState() void for rule trace remove committed state > 16:41:33,425 INFO [stdout] (MSC service thread 1-2) org.jboss.byteman.agent.Transformer : inserted trigger for trace remove committed state in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:33,612 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-8) WFLYIIOP0009: CORBA ORB Service started > 16:41:33,636 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 16:41:33,646 INFO [org.jboss.as.patching] (MSC service thread 1-7) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none > 16:41:33,663 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: Started FileSystemDeploymentService for directory /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/deployments > 16:41:33,668 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "restat-web-5.4.1.Final-SNAPSHOT.war" (runtime-name: "restat-web-5.4.1.Final-SNAPSHOT.war") > 16:41:33,700 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/paging) > 16:41:33,740 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221012: Using AIO Journal > 16:41:33,873 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final > 16:41:33,959 WARN [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0088: HTTP/2 will not be enabled as TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 is not enabled. You may need to install JCE to enable strong ciphers to allow HTTP/2 to function. > 16:41:33,981 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443 > 16:41:34,003 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,004 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,004 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,004 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,004 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,005 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,005 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,005 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,005 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,007 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,007 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,007 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,007 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,008 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,055 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.8) > 16:41:34,057 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-c11 > 16:41:34,057 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-participant > 16:41:34,057 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-client > 16:41:34,057 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-coordinator > 16:41:34,060 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 16:41:34,063 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 16:41:34,064 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 16:41:34,065 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 16:41:34,102 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=TerminationParticipantService > address=http://localhost:8080/ws-t11-client/TerminationParticipantService > implementor=com.arjuna.webservices11.wsarjtx.sei.TerminationParticipantPortTypeImpl > serviceName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService > portName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,102 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-5) JBWS024061: Adding service endpoint metadata: id=ActivationService > address=http://localhost:8080/ws-c11/ActivationService > implementor=com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService > portName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,102 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=CompletionCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > implementor=com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,102 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-6) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithCoordinatorCompletionParticipantService > address=http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionParticipantPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionParticipantService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,102 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=CompletionInitiatorService > address=http://localhost:8080/ws-t11-client/CompletionInitiatorService > implementor=com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=TerminationCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > implementor=com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > serviceName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService > portName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-6) JBWS024061: Adding service endpoint metadata: id=ParticipantService > address=http://localhost:8080/ws-t11-participant/ParticipantService > implementor=com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-5) JBWS024061: Adding service endpoint metadata: id=RegistrationService > address=http://localhost:8080/ws-c11/RegistrationService > implementor=com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService > portName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-6) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithParticipantCompletionParticipantService > address=http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=TerminationCoordinatorRPCService > address=http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > implementor=com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > serviceName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService > portName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypePort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithCoordinatorCompletionCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionCoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,103 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithParticipantCompletionCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,104 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=CoordinatorService > address=http://localhost:8080/ws-t11-coordinator/CoordinatorService > implementor=com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,104 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=CompletionCoordinatorRPCService > address=http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > implementor=com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorRPCService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorRPCPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:34,151 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.restat-web-5.4.1.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 16:41:34,152 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.restat-web-5.4.1.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 16:41:34,270 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 16:41:34,270 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 16:41:34,270 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 16:41:34,271 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 16:41:34,302 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,303 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:34,338 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live > 16:41:34,338 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.5.0 [default, nodeID=ef9290cb-ab4d-11e6-b97f-0242ac110007] > 16:41:34,340 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 69) AMQ221003: Deploying queue jms.queue.DLQ > 16:41:34,374 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221003: Deploying queue jms.queue.ExpiryQueue > 16:41:34,390 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 16:41:34,391 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 16:41:34,435 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 16:41:34,474 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0021: Registered web context: '/rest-tx' for server 'default-server' > 16:41:34,475 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) Resource adaptor started > 16:41:34,475 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatoractivemq-ra > 16:41:34,477 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 16:41:34,477 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 16:41:34,536 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from class com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > 16:41:34,536 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationParticipantPortType > 16:41:34,536 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-6) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionParticipantService from class org.oasis_open.docs.ws_tx.wsba._2006._06.BusinessAgreementWithCoordinatorCompletionParticipantPortType > 16:41:34,536 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > 16:41:34,949 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-client/TerminationParticipantService > 16:41:34,949 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-6) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > 16:41:34,949 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-5) Setting the server's publish address to be http://localhost:8080/ws-c11/ActivationService > 16:41:34,949 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > 16:41:35,055 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorService.wsdl > 16:41:35,056 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-5) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/ActivationService.wsdl > 16:41:35,056 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationCoordinatorPortType > 16:41:35,057 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from class com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > 16:41:35,057 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/TerminationParticipantService.wsdl > 16:41:35,058 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService from class com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > 16:41:35,060 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-6) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithCoordinatorCompletionParticipantService.wsdl > 16:41:35,060 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-6) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from class com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > 16:41:35,065 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > 16:41:35,070 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-client/CompletionInitiatorService > 16:41:35,073 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-6) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/ParticipantService > 16:41:35,073 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorService.wsdl > 16:41:35,074 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService from class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > 16:41:35,075 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-5) Setting the server's publish address to be http://localhost:8080/ws-c11/RegistrationService > 16:41:35,076 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > 16:41:35,078 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/CompletionInitiatorService.wsdl > 16:41:35,079 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-6) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/ParticipantService.wsdl > 16:41:35,080 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-6) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > 16:41:35,080 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorRPCPortTypeImplService.wsdl > 16:41:35,081 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > 16:41:35,083 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-5) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/RegistrationService.wsdl > 16:41:35,085 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 16:41:35,085 INFO [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 16:41:35,086 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-6) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > 16:41:35,086 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 16:41:35,086 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 16:41:35,091 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-client > 16:41:35,091 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-c11 > 16:41:35,094 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-6) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithParticipantCompletionParticipantService.wsdl > 16:41:35,095 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: '/ws-t11-client' for server 'default-server' > 16:41:35,095 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0021: Registered web context: '/ws-c11' for server 'default-server' > 16:41:35,098 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 16:41:35,098 INFO [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 16:41:35,098 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 16:41:35,098 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > 16:41:35,099 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-participant > 16:41:35,099 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0021: Registered web context: '/ws-t11-participant' for server 'default-server' > 16:41:35,106 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithCoordinatorCompletionCoordinatorService.wsdl > 16:41:35,107 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > 16:41:35,112 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > 16:41:35,120 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithParticipantCompletionCoordinatorService.wsdl > 16:41:35,120 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from class com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > 16:41:35,123 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CoordinatorService > 16:41:35,129 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CoordinatorService.wsdl > 16:41:35,130 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorRPCService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > 16:41:35,132 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > 16:41:35,138 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorRPCService.wsdl > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 16:41:35,142 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-coordinator > 16:41:35,143 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0021: Registered web context: '/ws-t11-coordinator' for server 'default-server' > 16:41:35,147 INFO [stdout] (MSC service thread 1-8) Rule.execute called for open trace file_2 > 16:41:35,148 INFO [stdout] (MSC service thread 1-8) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:35,148 INFO [stdout] (MSC service thread 1-8) calling installed(open trace file) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:35,148 INFO [stdout] (MSC service thread 1-8) Installed rule using default helper : open trace file > 16:41:35,148 INFO [stdout] (MSC service thread 1-8) open trace file execute > 16:41:35,149 INFO [stdout] (MSC service thread 1-8) Rule.execute called for create participant deletes counter_1 > 16:41:35,149 INFO [stdout] (MSC service thread 1-8) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:35,149 INFO [stdout] (MSC service thread 1-8) calling installed(create participant deletes counter) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:35,149 INFO [stdout] (MSC service thread 1-8) Installed rule using default helper : create participant deletes counter > 16:41:35,149 INFO [stdout] (MSC service thread 1-8) create participant deletes counter execute > 16:41:35,159 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : possible trigger for rule trace Participant send rollback in class com.arjuna.wst11.messaging.CoordinatorProcessorImpl > 16:41:35,160 INFO [stdout] (MSC service thread 1-8) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.CoordinatorProcessorImpl.prepared(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace Participant send rollback > 16:41:35,163 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : inserted trigger for trace Participant send rollback in class com.arjuna.wst11.messaging.CoordinatorProcessorImpl > 16:41:35,179 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate coordinator close in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:35,180 INFO [stdout] (MSC service thread 1-8) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator.rollback() void for rule trace subordinate coordinator close > 16:41:35,181 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate coordinator close in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:35,182 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate coordinator prepare in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:35,182 INFO [stdout] (MSC service thread 1-8) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator.prepare() int for rule trace subordinate coordinator prepare > 16:41:35,183 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate coordinator prepare in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:35,184 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate coordinator rollback 2 in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:35,185 INFO [stdout] (MSC service thread 1-8) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator.rollback() void for rule trace subordinate coordinator rollback 2 > 16:41:35,186 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate coordinator rollback 2 in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:35,197 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : possible trigger for rule trace delete participant and exit JVM in class org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple > 16:41:35,197 INFO [stdout] (MSC service thread 1-8) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple.deleteParticipantRecoveryRecord(java.lang.String) boolean for rule trace delete participant and exit JVM > 16:41:35,198 INFO [stdout] (MSC service thread 1-8) org.jboss.byteman.agent.Transformer : inserted trigger for trace delete participant and exit JVM in class org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple > 16:41:35,221 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-4) ARJUNA033013: OutboundBridgeRecoveryManager starting > 16:41:35,221 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-8) ARJUNA033006: InboundBridgeRecoveryManager starting > 16:41:35,235 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "restat-web-5.4.1.Final-SNAPSHOT.war" (runtime-name : "restat-web-5.4.1.Final-SNAPSHOT.war") > 16:41:35,301 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 16:41:35,301 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 16:41:35,301 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha12 "Kenny" started in 3688ms - Started 508 of 752 services (451 services are lazy, passive or on-demand) > 16:41:35,378 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/content/67/eecc8af4663400c3ea658c818ff35814a26f3a/content > 16:41:35,380 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "xtstest.war" (runtime-name: "xtstest.war") > 16:41:35,661 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.xtstest.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 16:41:35,675 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment xtstest.war > 16:41:35,699 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-6) HV000001: Hibernate Validator 5.2.4.Final > 16:41:35,830 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 2.4.0 (Final) > 16:41:35,837 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Service_One > address=http://localhost:8080/xtstest/xtsservicetest1 > implementor=org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:35,838 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Service_Two > address=http://localhost:8080/xtstest/xtsservicetest2 > implementor=org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:35,838 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Service_Three > address=http://localhost:8080/xtstest/xtsservicetest3 > implementor=org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:35,838 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Subordinate_Service_One > address=http://localhost:8080/xtstest/xtssubordinateservicetest1 > implementor=org.jboss.jbossts.xts.servicetests.service.subordinate.XTSSubordinateServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:35,848 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:35,881 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest1 > 16:41:35,887 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:35,888 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:35,890 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest2 > 16:41:35,892 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:35,893 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:35,894 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest3 > 16:41:35,897 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:35,897 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:35,898 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/xtstest/xtssubordinateservicetest1 > 16:41:35,902 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:35,909 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 16:41:35,910 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 16:41:35,910 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 16:41:35,910 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 16:41:35,913 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:35,914 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:36,099 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-1) WELD-000169: Jandex cannot distinguish inner and static nested classes! Update Jandex to 2.0.3.Final version or newer to improve scanning performance. > 16:41:36,386 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 13) Starting XTSServiceTestRunner > 16:41:36,386 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 13) Starting XTS Service Test org.jboss.jbossts.xts.servicetests.test.at.subordinate.MultiParticipantPrepareAndCommitTest > 16:41:36,386 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 13) Started XTSServiceTestRunner > 16:41:36,394 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 13) Initializing Mojarra 2.2.13.SP1 20160303-1204 for context '/xtstest' > 16:41:36,784 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 13) WFLYUT0021: Registered web context: '/xtstest' for server 'default-server' > 16:41:36,811 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") > Nov 15, 2016 4:41:36 PM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > Nov 15, 2016 4:41:36 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill > INFO: Hard killing of a server instance > Nov 15, 2016 4:41:36 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: waiting for byteman to kill the server > Nov 15, 2016 4:41:36 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > 16:41:41,421 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Thread-123) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 16:41:41,431 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Thread-123) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 16:41:41,785 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Thread-123) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 16:41:41,817 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Thread-123) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: vfs:/content/xtstest.war/WEB-INF/classes/org/jboss/jbossts/xts/servicetests/generated/wsdl/xtsservicetests.wsdl > 16:41:41,862 INFO [stdout] (default task-3) service /xtsservicetest1 > 16:41:41,862 INFO [stdout] (default task-3) command enlistDurable > 16:41:41,862 INFO [stdout] (default task-3) command prepare > 16:41:41,862 INFO [stdout] (default task-3) command commit > 16:41:41,880 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-3) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 16:41:41,901 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace Coordinator engine create in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,902 INFO [stdout] (default task-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.(java.lang.String,boolean,javax.xml.ws.wsaddressing.W3CEndpointReference,boolean,com.arjuna.webservices11.wsat.State) void for rule trace Coordinator engine create > 16:41:41,911 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace Coordinator engine create in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,912 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive Participant aborted in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,913 INFO [stdout] (default task-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.aborted(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive Participant aborted > 16:41:41,918 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive Participant aborted in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,919 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive participant prepared in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,920 INFO [stdout] (default task-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.prepared(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive participant prepared > 16:41:41,926 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive participant prepared in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,927 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send participant prepare in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,928 INFO [stdout] (default task-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.prepare() com.arjuna.webservices11.wsat.State for rule trace send participant prepare > 16:41:41,933 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace send participant prepare in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,934 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send Participant rollback in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,935 INFO [stdout] (default task-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.rollback() com.arjuna.webservices11.wsat.State for rule trace send Participant rollback > 16:41:41,940 INFO [stdout] (default task-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace send Participant rollback in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:41:41,942 INFO [stdout] (default task-4) Rule.execute called for trace Coordinator engine create_11 > 16:41:41,943 INFO [stdout] (default task-4) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:41,943 INFO [stdout] (default task-4) calling installed(trace Coordinator engine create) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:41,943 INFO [stdout] (default task-4) Installed rule using default helper : trace Coordinator engine create > 16:41:41,943 INFO [stdout] (default task-4) trace Coordinator engine create execute > 16:41:41,955 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : possible trigger for rule trace Participant create in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,956 INFO [stdout] (default task-3) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.(com.arjuna.wst.Participant,java.lang.String,com.arjuna.webservices11.wsat.State,javax.xml.ws.wsaddressing.W3CEndpointReference,boolean) void for rule trace Participant create > 16:41:41,968 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : inserted trigger for trace Participant create in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,969 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive participant prepare in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,970 INFO [stdout] (default task-3) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.prepare(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive participant prepare > 16:41:41,976 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive participant prepare in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,978 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send Participant prepared in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,984 INFO [stdout] (default task-3) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.sendPrepared(boolean) void for rule trace send Participant prepared > 16:41:41,984 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : inserted trigger for trace send Participant prepared in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,986 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive Participant rollback in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,986 INFO [stdout] (default task-3) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.rollback(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive Participant rollback > 16:41:41,993 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive Participant rollback in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:41,994 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send Participant aborted in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:42,000 INFO [stdout] (default task-3) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.sendAborted() void for rule trace send Participant aborted > 16:41:42,000 INFO [stdout] (default task-3) org.jboss.byteman.agent.Transformer : inserted trigger for trace send Participant aborted in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:41:42,002 INFO [stdout] (default task-3) Rule.execute called for trace Participant create_16 > 16:41:42,002 INFO [stdout] (default task-3) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,002 INFO [stdout] (default task-3) calling installed(trace Participant create) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,002 INFO [stdout] (default task-3) Installed rule using default helper : trace Participant create > 16:41:42,002 INFO [stdout] (default task-3) trace Participant create execute > 16:41:42,029 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub rollback in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,030 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.rollback() void for rule trace subordinate participant stub rollback > 16:41:42,031 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub rollback in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,031 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub prepare in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,031 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.prepare() com.arjuna.wst.Vote for rule trace subordinate participant stub prepare > 16:41:42,032 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub prepare in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,032 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub prepare 2 in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,033 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.prepare() com.arjuna.wst.Vote for rule trace subordinate participant stub prepare 2 > 16:41:42,033 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub prepare 2 in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,034 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub rollback forward in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,034 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.rollback() void for rule trace subordinate participant stub rollback forward > 16:41:42,035 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub rollback forward in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,036 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub rollback with no coordinator in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,036 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.rollback() void for rule trace subordinate participant stub rollback with no coordinator > 16:41:42,037 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub rollback with no coordinator in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,037 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub rollback with unactivated coordinator in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,038 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.rollback() void for rule trace subordinate participant stub rollback with unactivated coordinator > 16:41:42,038 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub rollback with unactivated coordinator in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,039 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate participant stub rollback return in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,039 INFO [stdout] (default task-5) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.stub.SubordinateDurable2PCStub.rollback() void for rule trace subordinate participant stub rollback return > 16:41:42,040 INFO [stdout] (default task-5) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate participant stub rollback return in class com.arjuna.wst11.stub.SubordinateDurable2PCStub > 16:41:42,055 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 16:41:42,071 INFO [stdout] (default task-6) Rule.execute called for trace Coordinator engine create_11 > 16:41:42,072 INFO [stdout] (default task-6) trace Coordinator engine create execute > 16:41:42,081 INFO [stdout] (default task-5) Rule.execute called for trace Participant create_16 > 16:41:42,082 INFO [stdout] (default task-5) trace Participant create execute > 16:41:42,091 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 16:41:42,104 INFO [stdout] (default task-7) Rule.execute called for trace Coordinator engine create_11 > 16:41:42,105 INFO [stdout] (default task-7) trace Coordinator engine create execute > 16:41:42,112 INFO [stdout] (default task-5) Rule.execute called for trace Participant create_16 > 16:41:42,112 INFO [stdout] (default task-5) trace Participant create execute > 16:41:42,116 INFO [stdout] (default task-5) service /xtssubordinateservicetest1 > 16:41:42,116 INFO [stdout] (default task-5) command enlistDurable > 16:41:42,116 INFO [stdout] (default task-5) command prepare > 16:41:42,116 INFO [stdout] (default task-5) command commit > 16:41:42,128 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 16:41:42,140 INFO [stdout] (default task-8) Rule.execute called for trace Coordinator engine create_11 > 16:41:42,141 INFO [stdout] (default task-8) trace Coordinator engine create execute > 16:41:42,148 INFO [stdout] (default task-5) Rule.execute called for trace Participant create_16 > 16:41:42,148 INFO [stdout] (default task-5) trace Participant create execute > 16:41:42,169 INFO [stdout] (default task-9) service /xtssubordinateservicetest1 > 16:41:42,170 INFO [stdout] (default task-9) command enlistDurable > 16:41:42,170 INFO [stdout] (default task-9) command prepare > 16:41:42,170 INFO [stdout] (default task-9) command commit > 16:41:42,181 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-9) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 16:41:42,193 INFO [stdout] (default task-10) Rule.execute called for trace Coordinator engine create_11 > 16:41:42,193 INFO [stdout] (default task-10) trace Coordinator engine create execute > 16:41:42,199 INFO [stdout] (default task-9) Rule.execute called for trace Participant create_16 > 16:41:42,199 INFO [stdout] (default task-9) trace Participant create execute > 16:41:42,220 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Thread-123) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-completion-coordinator-binding.wsdl > 16:41:42,254 INFO [stdout] (TaskWorker-1) Rule.execute called for trace send participant prepare_14 > 16:41:42,255 INFO [stdout] (TaskWorker-1) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,255 INFO [stdout] (TaskWorker-1) calling installed(trace send participant prepare) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,255 INFO [stdout] (TaskWorker-1) Installed rule using default helper : trace send participant prepare > 16:41:42,255 INFO [stdout] (TaskWorker-1) trace send participant prepare execute > 16:41:42,255 INFO [stdout] (TaskWorker-1) rule.debug{trace send participant prepare} : prepare sent for Coordinator engine V0:ffffac110007:-3ffa9bb3:582b3abd:1b > 16:41:42,274 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:41:42,300 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive participant prepare_17 > 16:41:42,301 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,301 INFO [stdout] (TaskWorker-2) calling installed(trace receive participant prepare) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,301 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace receive participant prepare > 16:41:42,301 INFO [stdout] (TaskWorker-2) trace receive participant prepare execute > 16:41:42,301 INFO [stdout] (TaskWorker-2) rule.debug{trace receive participant prepare} : prepare received for participant org.jboss.jbossts.xts.at.subordinate.participant.0:ffffac110007:-3ffa9bb3:582b3abd:19_V > 16:41:42,302 INFO [stdout] (TaskWorker-2) Rule.execute called for trace send Participant prepared_18 > 16:41:42,303 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,303 INFO [stdout] (TaskWorker-2) calling installed(trace send Participant prepared) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,303 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace send Participant prepared > 16:41:42,303 INFO [stdout] (TaskWorker-2) trace send Participant prepared execute > 16:41:42,303 INFO [stdout] (TaskWorker-2) rule.debug{trace send Participant prepared} : prepared sent for Participant org.jboss.jbossts.xts.at.subordinate.participant.0:ffffac110007:-3ffa9bb3:582b3abd:19_V > 16:41:42,321 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:41:42,342 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive participant prepared_13 > 16:41:42,342 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,342 INFO [stdout] (TaskWorker-2) calling installed(trace receive participant prepared) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,342 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace receive participant prepared > 16:41:42,342 INFO [stdout] (TaskWorker-2) trace receive participant prepared execute > 16:41:42,342 INFO [stdout] (TaskWorker-2) rule.debug{trace receive participant prepared} : prepared received for Coordinator engine V0:ffffac110007:-3ffa9bb3:582b3abd:1b > 16:41:42,343 INFO [stdout] (TaskWorker-1) Rule.execute called for trace send participant prepare_14 > 16:41:42,343 INFO [stdout] (TaskWorker-1) trace send participant prepare execute > 16:41:42,343 INFO [stdout] (TaskWorker-1) rule.debug{trace send participant prepare} : prepare sent for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:16 > 16:41:42,352 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:41:42,367 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive participant prepare_17 > 16:41:42,368 INFO [stdout] (TaskWorker-2) trace receive participant prepare execute > 16:41:42,368 INFO [stdout] (TaskWorker-2) rule.debug{trace receive participant prepare} : prepare received for participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:41:42,396 INFO [stdout] (TaskWorker-2) Rule.execute called for trace send Participant prepared_18 > 16:41:42,396 INFO [stdout] (TaskWorker-2) trace send Participant prepared execute > 16:41:42,396 INFO [stdout] (TaskWorker-2) rule.debug{trace send Participant prepared} : prepared sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:41:42,404 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:41:42,422 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive participant prepared_13 > 16:41:42,422 INFO [stdout] (TaskWorker-2) trace receive participant prepared execute > 16:41:42,422 INFO [stdout] (TaskWorker-2) rule.debug{trace receive participant prepared} : prepared received for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:16 > 16:41:42,423 INFO [stdout] (TaskWorker-1) Rule.execute called for trace send participant prepare_14 > 16:41:42,423 INFO [stdout] (TaskWorker-1) trace send participant prepare execute > 16:41:42,423 INFO [stdout] (TaskWorker-1) rule.debug{trace send participant prepare} : prepare sent for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:1d > 16:41:42,430 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:41:42,445 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive participant prepare_17 > 16:41:42,445 INFO [stdout] (TaskWorker-2) trace receive participant prepare execute > 16:41:42,446 INFO [stdout] (TaskWorker-2) rule.debug{trace receive participant prepare} : prepare received for participant org.jboss.jbossts.xts.at.subordinate.participant.0:ffffac110007:-3ffa9bb3:582b3abd:19_D > 16:41:42,446 INFO [stdout] (TaskWorker-2) Rule.execute called for trace subordinate participant stub prepare_22 > 16:41:42,446 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,446 INFO [stdout] (TaskWorker-2) calling installed(trace subordinate participant stub prepare) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,446 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace subordinate participant stub prepare > 16:41:42,446 INFO [stdout] (TaskWorker-2) trace subordinate participant stub prepare execute > 16:41:42,446 INFO [stdout] (TaskWorker-2) rule.debug{trace subordinate participant stub prepare} : prepare called for pseudo-participant com.arjuna.wst11.stub.SubordinateDurable2PCStub at 422a3fd3 > 16:41:42,446 INFO [stdout] (TaskWorker-2) Rule.execute called for trace subordinate coordinator prepare_8 > 16:41:42,447 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,447 INFO [stdout] (TaskWorker-2) calling installed(trace subordinate coordinator prepare) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,447 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace subordinate coordinator prepare > 16:41:42,447 INFO [stdout] (TaskWorker-2) trace subordinate coordinator prepare execute > 16:41:42,447 INFO [stdout] (TaskWorker-2) rule.debug{trace subordinate coordinator prepare} : prepare for subordinate transaction 0:ffffac110007:-3ffa9bb3:582b3abd:19 > 16:41:42,447 INFO [stdout] (TaskWorker-2) Rule.execute called for trace send participant prepare_14 > 16:41:42,448 INFO [stdout] (TaskWorker-2) trace send participant prepare execute > 16:41:42,448 INFO [stdout] (TaskWorker-2) rule.debug{trace send participant prepare} : prepare sent for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:20 > 16:41:42,456 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:41:42,471 INFO [stdout] (TaskWorker-3) Rule.execute called for trace receive participant prepare_17 > 16:41:42,471 INFO [stdout] (TaskWorker-3) trace receive participant prepare execute > 16:41:42,471 INFO [stdout] (TaskWorker-3) rule.debug{trace receive participant prepare} : prepare received for participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:41:42,706 INFO [stdout] (TaskWorker-3) Rule.execute called for trace send Participant prepared_18 > 16:41:42,707 INFO [stdout] (TaskWorker-3) trace send Participant prepared execute > 16:41:42,707 INFO [stdout] (TaskWorker-3) rule.debug{trace send Participant prepared} : prepared sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:41:42,714 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-3) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:41:42,729 INFO [stdout] (TaskWorker-3) Rule.execute called for trace receive participant prepared_13 > 16:41:42,729 INFO [stdout] (TaskWorker-3) trace receive participant prepared execute > 16:41:42,729 INFO [stdout] (TaskWorker-3) rule.debug{trace receive participant prepared} : prepared received for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:20 > 16:41:42,730 INFO [stdout] (TaskWorker-2) Rule.execute called for trace send participant prepare_14 > 16:41:42,730 INFO [stdout] (TaskWorker-2) trace send participant prepare execute > 16:41:42,730 INFO [stdout] (TaskWorker-2) rule.debug{trace send participant prepare} : prepare sent for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:23 > 16:41:42,739 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:41:42,751 INFO [stdout] (TaskWorker-3) Rule.execute called for trace receive participant prepare_17 > 16:41:42,751 INFO [stdout] (TaskWorker-3) trace receive participant prepare execute > 16:41:42,751 INFO [stdout] (TaskWorker-3) rule.debug{trace receive participant prepare} : prepare received for participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:41:42,753 INFO [stdout] (TaskWorker-3) Rule.execute called for trace send Participant prepared_18 > 16:41:42,753 INFO [stdout] (TaskWorker-3) trace send Participant prepared execute > 16:41:42,753 INFO [stdout] (TaskWorker-3) rule.debug{trace send Participant prepared} : prepared sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:41:42,759 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-3) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:41:42,773 INFO [stdout] (TaskWorker-3) Rule.execute called for trace receive participant prepared_13 > 16:41:42,773 INFO [stdout] (TaskWorker-3) trace receive participant prepared execute > 16:41:42,774 INFO [stdout] (TaskWorker-3) rule.debug{trace receive participant prepared} : prepared received for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:23 > 16:41:42,777 INFO [stdout] (TaskWorker-2) Rule.execute called for trace TX save at prepare_3 > 16:41:42,778 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,778 INFO [stdout] (TaskWorker-2) calling installed(trace TX save at prepare) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,778 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace TX save at prepare > 16:41:42,778 INFO [stdout] (TaskWorker-2) trace TX save at prepare execute > 16:41:42,778 INFO [stdout] (TaskWorker-2) rule.debug{trace TX save at prepare} : saved to disk transaction 0:ffffac110007:-3ffa9bb3:582b3abd:19 > 16:41:42,782 INFO [stdout] (TaskWorker-2) Rule.execute called for trace subordinate participant stub prepare 2_23 > 16:41:42,782 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:42,782 INFO [stdout] (TaskWorker-2) calling installed(trace subordinate participant stub prepare 2) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:42,782 INFO [stdout] (TaskWorker-2) Installed rule using default helper : trace subordinate participant stub prepare 2 > 16:41:42,782 INFO [stdout] (TaskWorker-2) trace subordinate participant stub prepare 2 execute > 16:41:42,782 INFO [stdout] (TaskWorker-2) rule.debug{trace subordinate participant stub prepare 2} : JVM exit > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep '\[java\] '`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as killed by byteman scirpt > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommand > INFO: Executing shell command: 'mkdir target/surefire-reports/processes' > std error mkdir: cannot create directory 'target/surefire-reports/processes': File exists > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.BaseServerKillProcessor dumpStream > INFO: Execution result: 'mkdir: cannot create directory 'target/surefire-reports/processes': File exists' > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommand > INFO: Executing shell command: 'ps aux > target/surefire-reports/processes/null:null_12.txt' > Nov 15, 2016 4:41:46 PM com.arjuna.qa.extension.BaseServerKillProcessor dumpProcesses > INFO: Logged current running processes to: target/surefire-reports/processes/null:null_12.txt > Nov 15, 2016 4:41:46 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance with overridden configuration. New configuration: {managementAddress=127.0.0.1, javaVmArguments=-server -Xms64m -Xmx1024m -XX:MaxPermSize=512m -Dorg.jboss.byteman.verbose > -Djboss.modules.system.pkgs=org.jboss.byteman > -Dorg.jboss.byteman.transform.all > -javaagent:/home/jenkins/workspace/narayana-codeCoverage/XTS/localjunit/crash-recovery-tests/target/lib/byteman.jar=script:target/test-classes/scripts/ATSubordinateCrashDuringPrepare.btm,boot:target/lib/byteman.jar,listener:true , startupTimeoutInSeconds=60, serverConfig=standalone-xts.xml} > Nov 15, 2016 4:41:46 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > Nov 15, 2016 4:41:46 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/lib/jvm/java-1.8.0-openjdk/bin/java, -D[Standalone], -server, -Xms64m, -Xmx1024m, -XX:MaxPermSize=512m, -Dorg.jboss.byteman.verbose, -Djboss.modules.system.pkgs=org.jboss.byteman, -Dorg.jboss.byteman.transform.all, -javaagent:/home/jenkins/workspace/narayana-codeCoverage/XTS/localjunit/crash-recovery-tests/target/lib/byteman.jar=script:target/test-classes/scripts/ATSubordinateCrashDuringPrepare.btm,boot:target/lib/byteman.jar,listener:true, -ea, -Djboss.home.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/jboss-modules.jar, -mp, /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT, -Djboss.server.base.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/configuration, -c=standalone-xts.xml] > OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 16:41:47,298 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta3 > 16:41:47,473 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.Final > 16:41:47,565 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Core 3.0.0.Alpha12 "Kenny" starting > 16:41:47,703 INFO [org.jboss.as.domain.management] (MSC service thread 1-1) WFLYDM0136: Registered OpenSSL provider > 16:41:48,403 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 7) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 16:41:48,449 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 16:41:48,460 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.4.1.Final > 16:41:48,465 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.4.1.Final > 16:41:48,483 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 40) WFLYCLINF0001: Activating Infinispan subsystem. > 16:41:48,484 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 41) WFLYIIOP0001: Activating IIOP Subsystem > 16:41:48,485 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 39) WFLYIO001: Worker 'default' has auto-configured to 48 core threads with 384 task threads based on your 24 available processors > 16:41:48,487 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 47) WFLYJSF0007: Activated the following JSF Implementations: [main] > 16:41:48,493 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final) > 16:41:48,536 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 16:41:48,537 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem > 16:41:48,540 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = h2 > 16:41:48,550 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 59) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 16:41:48,557 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 61) WFLYWS0002: Activating WebServices Extension > 16:41:48,558 INFO [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem > 16:41:48,560 INFO [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=5.0.0.Alpha3 > 16:41:48,599 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.4.4.Final starting > 16:41:48,602 INFO [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service > 16:41:48,603 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 16:41:48,616 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 5.0.0.Beta7 > 16:41:48,636 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : possible trigger for rule create participant deletes counter in class org.jboss.jbossts.XTSService > 16:41:48,663 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : possible trigger for rule reset periodic recovery wait time in class com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean > 16:41:48,675 INFO [stdout] (MSC service thread 1-7) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getPeriodicRecoveryPeriod() int for rule reset periodic recovery wait time > 16:41:48,676 INFO [stdout] (ServerService Thread Pool -- 63) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.XTSService.start() void for rule create participant deletes counter > 16:41:48,684 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : inserted trigger for reset periodic recovery wait time in class com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean > 16:41:48,691 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : inserted trigger for create participant deletes counter in class org.jboss.jbossts.XTSService > 16:41:48,693 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : possible trigger for rule open trace file in class org.jboss.jbossts.XTSService > 16:41:48,695 INFO [stdout] (ServerService Thread Pool -- 63) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.XTSService.start() void for rule open trace file > 16:41:48,699 INFO [stdout] (ServerService Thread Pool -- 63) org.jboss.byteman.agent.Transformer : inserted trigger for open trace file in class org.jboss.jbossts.XTSService > 16:41:48,707 INFO [org.wildfly.security] (MSC service thread 1-8) ELY00001: WildFly Elytron version 1.1.0.Beta13 > 16:41:48,710 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 96 (per class), which is derived from the number of CPUs on this host. > 16:41:48,710 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 384 (per class), which is derived from thread worker pool sizing. > 16:41:48,723 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0014: Creating file handler for path '/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 16:41:48,730 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server. > 16:41:48,731 INFO [stdout] (MSC service thread 1-7) Rule.execute called for reset periodic recovery wait time_1 > 16:41:48,731 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: Host default-host starting > 16:41:48,733 INFO [stdout] (MSC service thread 1-7) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:48,735 INFO [stdout] (MSC service thread 1-7) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 16:41:48,735 INFO [stdout] (MSC service thread 1-7) Default helper activated > 16:41:48,735 INFO [stdout] (MSC service thread 1-7) calling installed(reset periodic recovery wait time) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:48,736 INFO [stdout] (MSC service thread 1-7) Installed rule using default helper : reset periodic recovery wait time > 16:41:48,736 INFO [stdout] (MSC service thread 1-7) reset periodic recovery wait time execute > 16:41:48,736 INFO [stdout] (MSC service thread 1-7) caught ReturnException > 16:41:48,761 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : possible trigger for rule trace TX save at prepare in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:48,790 INFO [stdout] (MSC service thread 1-7) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(boolean) int for rule trace TX save at prepare > 16:41:48,794 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : inserted trigger for trace TX save at prepare in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:48,794 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 16:41:48,799 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : possible trigger for rule trace remove committed state and exit JVM in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:48,817 INFO [stdout] (MSC service thread 1-7) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.coordinator.BasicAction.updateState() void for rule trace remove committed state and exit JVM > 16:41:48,818 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : inserted trigger for trace remove committed state and exit JVM in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:48,822 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : possible trigger for rule trace remove committed state in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:48,840 INFO [stdout] (MSC service thread 1-7) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.ats.arjuna.coordinator.BasicAction.updateState() void for rule trace remove committed state > 16:41:48,843 INFO [stdout] (MSC service thread 1-7) org.jboss.byteman.agent.Transformer : inserted trigger for trace remove committed state in class com.arjuna.ats.arjuna.coordinator.BasicAction > 16:41:48,923 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-6) WFLYIIOP0009: CORBA ORB Service started > 16:41:49,091 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 16:41:49,106 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly cumulative patch ID is: base, one-off patches include: none > 16:41:49,145 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "restat-web-5.4.1.Final-SNAPSHOT.war" (runtime-name: "restat-web-5.4.1.Final-SNAPSHOT.war") > 16:41:49,147 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "xtstest.war" (runtime-name: "xtstest.war") > 16:41:49,148 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/deployments > 16:41:49,324 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/paging) > 16:41:49,375 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221012: Using AIO Journal > 16:41:49,389 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final > 16:41:49,429 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,430 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,430 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,431 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-8) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,431 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,432 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,432 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,433 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,434 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,434 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,434 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,435 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,442 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,442 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-5) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,445 WARN [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0088: HTTP/2 will not be enabled as TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 is not enabled. You may need to install JCE to enable strong ciphers to allow HTTP/2 to function. > 16:41:49,456 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443 > 16:41:49,537 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.8) > 16:41:49,539 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-client > 16:41:49,539 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-coordinator > 16:41:49,539 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-participant > 16:41:49,539 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-c11 > 16:41:49,569 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 16:41:49,571 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 16:41:49,572 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithCoordinatorCompletionParticipantService > address=http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionParticipantPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionParticipantService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,572 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) JBWS024061: Adding service endpoint metadata: id=TerminationParticipantService > address=http://localhost:8080/ws-t11-client/TerminationParticipantService > implementor=com.arjuna.webservices11.wsarjtx.sei.TerminationParticipantPortTypeImpl > serviceName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService > portName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,572 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-5) JBWS024061: Adding service endpoint metadata: id=ActivationService > address=http://localhost:8080/ws-c11/ActivationService > implementor=com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService > portName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,572 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=CompletionCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > implementor=com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,572 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 16:41:49,572 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=ParticipantService > address=http://localhost:8080/ws-t11-participant/ParticipantService > implementor=com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,572 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=TerminationCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > implementor=com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > serviceName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService > portName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,573 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-5) JBWS024061: Adding service endpoint metadata: id=RegistrationService > address=http://localhost:8080/ws-c11/RegistrationService > implementor=com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService > portName={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,573 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithParticipantCompletionParticipantService > address=http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,573 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) JBWS024061: Adding service endpoint metadata: id=CompletionInitiatorService > address=http://localhost:8080/ws-t11-client/CompletionInitiatorService > implementor=com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,573 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 16:41:49,573 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=TerminationCoordinatorRPCService > address=http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > implementor=com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > serviceName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService > portName={http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypePort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,573 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithCoordinatorCompletionCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionCoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,574 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=BusinessAgreementWithParticipantCompletionCoordinatorService > address=http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > implementor=com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,574 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=CoordinatorService > address=http://localhost:8080/ws-t11-coordinator/CoordinatorService > implementor=com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,574 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) JBWS024061: Adding service endpoint metadata: id=CompletionCoordinatorRPCService > address=http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > implementor=com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > serviceName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorRPCService > portName={http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorRPCPortType > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 16:41:49,629 WARN [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.restat-web-5.4.1.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 16:41:49,629 WARN [org.jboss.as.dependency.private] (MSC service thread 1-7) WFLYSRV0018: Deployment "deployment.restat-web-5.4.1.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 16:41:49,806 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,807 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:49,815 WARN [org.jboss.as.dependency.private] (MSC service thread 1-8) WFLYSRV0018: Deployment "deployment.xtstest.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 16:41:49,833 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment xtstest.war > 16:41:49,863 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.2.4.Final > 16:41:49,897 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 16:41:49,897 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 16:41:49,897 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 16:41:49,898 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 16:41:49,937 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0021: Registered web context: '/rest-tx' for server 'default-server' > 16:41:49,960 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live > 16:41:49,960 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.5.0 [default, nodeID=ef9290cb-ab4d-11e6-b97f-0242ac110007] > 16:41:49,962 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221003: Deploying queue jms.queue.DLQ > 16:41:49,992 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 16:41:49,993 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: Deploying queue jms.queue.ExpiryQueue > 16:41:49,995 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 65) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 16:41:50,010 INFO [org.jboss.weld.Version] (MSC service thread 1-8) WELD-000900: 2.4.0 (Final) > 16:41:50,018 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-8) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Service_One > address=http://localhost:8080/xtstest/xtsservicetest1 > implementor=org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:50,019 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-8) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Service_Two > address=http://localhost:8080/xtstest/xtsservicetest2 > implementor=org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:50,019 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-8) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Service_Three > address=http://localhost:8080/xtstest/xtsservicetest3 > implementor=org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:50,019 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-8) JBWS024061: Adding service endpoint metadata: id=XTS_Service_Test_Subordinate_Service_One > address=http://localhost:8080/xtstest/xtssubordinateservicetest1 > implementor=org.jboss.jbossts.xts.servicetests.service.subordinate.XTSSubordinateServiceTestPortTypeImpl > serviceName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService > portName={http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestPortType > annotationWsdlLocation=WEB-INF/wsdl/xtsservicetests.wsdl > wsdlLocationOverride=null > mtomEnabled=false > 16:41:50,026 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0007: Registered connection factory java:/JmsXA > 16:41:50,036 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-8) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:50,036 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from class com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > 16:41:50,036 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > 16:41:50,036 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationParticipantPortType > 16:41:50,036 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionParticipantService from class org.oasis_open.docs.ws_tx.wsba._2006._06.BusinessAgreementWithCoordinatorCompletionParticipantPortType > 16:41:50,062 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-6) Resource adaptor started > 16:41:50,062 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatoractivemq-ra > 16:41:50,063 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 16:41:50,063 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 16:41:50,339 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-8) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest1 > 16:41:50,386 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-client/TerminationParticipantService > 16:41:50,390 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > 16:41:50,390 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > 16:41:50,400 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-5) Setting the server's publish address to be http://localhost:8080/ws-c11/ActivationService > 16:41:50,429 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-8) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:50,430 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-8) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:50,432 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-8) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest2 > 16:41:50,436 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-8) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:50,436 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-8) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:50,438 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-8) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest3 > 16:41:50,442 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-8) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:50,442 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-8) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 16:41:50,444 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-8) Setting the server's publish address to be http://localhost:8080/xtstest/xtssubordinateservicetest1 > 16:41:50,448 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorService.wsdl > 16:41:50,449 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationCoordinatorPortType > 16:41:50,449 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-8) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 16:41:50,450 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-5) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/ActivationService.wsdl > 16:41:50,450 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/TerminationParticipantService.wsdl > 16:41:50,450 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-5) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from class com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > 16:41:50,451 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService from class com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > 16:41:50,455 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > 16:41:50,459 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithCoordinatorCompletionParticipantService.wsdl > 16:41:50,460 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-client/CompletionInitiatorService > 16:41:50,460 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from class com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > 16:41:50,462 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorService.wsdl > 16:41:50,462 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/ParticipantService > 16:41:50,463 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService from class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > 16:41:50,463 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 16:41:50,463 INFO [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 16:41:50,463 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 16:41:50,464 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 16:41:50,465 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > 16:41:50,465 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-5) Setting the server's publish address to be http://localhost:8080/ws-c11/RegistrationService > 16:41:50,466 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/CompletionInitiatorService.wsdl > 16:41:50,469 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:50,470 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. > 16:41:50,470 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/ParticipantService.wsdl > 16:41:50,472 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > 16:41:50,472 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorRPCPortTypeImplService.wsdl > 16:41:50,472 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 16:41:50,472 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 16:41:50,473 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithCoordinatorCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > 16:41:50,473 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-client > 16:41:50,478 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0021: Registered web context: '/ws-t11-client' for server 'default-server' > 16:41:50,482 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > 16:41:50,483 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-5) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/RegistrationService.wsdl > 16:41:50,487 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 16:41:50,487 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 16:41:50,489 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-c11 > 16:41:50,490 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0021: Registered web context: '/ws-c11' for server 'default-server' > 16:41:50,492 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithParticipantCompletionParticipantService.wsdl > 16:41:50,495 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 16:41:50,495 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 16:41:50,495 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 16:41:50,496 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-participant > 16:41:50,497 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: '/ws-t11-participant' for server 'default-server' > 16:41:50,502 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > 16:41:50,517 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithCoordinatorCompletionCoordinatorService.wsdl > 16:41:50,518 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > 16:41:50,522 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > 16:41:50,533 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithParticipantCompletionCoordinatorService.wsdl > 16:41:50,533 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from class com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > 16:41:50,537 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CoordinatorService > 16:41:50,544 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CoordinatorService.wsdl > 16:41:50,545 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionCoordinatorRPCService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > 16:41:50,549 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > 16:41:50,555 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/jenkins/workspace/narayana-codeCoverage/jboss-as/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorRPCService.wsdl > 16:41:50,560 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 16:41:50,560 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 16:41:50,561 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 16:41:50,561 INFO [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 16:41:50,561 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 16:41:50,561 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 16:41:50,561 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 16:41:50,564 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-coordinator > 16:41:50,565 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0021: Registered web context: '/ws-t11-coordinator' for server 'default-server' > 16:41:50,569 INFO [stdout] (MSC service thread 1-4) Rule.execute called for open trace file_2 > 16:41:50,570 INFO [stdout] (MSC service thread 1-4) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:41:50,570 INFO [stdout] (MSC service thread 1-4) calling installed(open trace file) for helper classorg.jboss.byteman.rule.helper.Helper > 16:41:50,570 INFO [stdout] (MSC service thread 1-4) Installed rule using default helper : open trace file > 16:41:50,570 INFO [stdout] (MSC service thread 1-4) open trace file execute > 16:41:50,570 INFO [stdout] (MSC service thread 1-4) Rule.execute called for create participant deletes counter_0 > 16:41:50,571 INFO [stdout] (MSC service thread 1-4) Rule.execute for decommissioned key create participant deletes counter_0 > 16:41:50,582 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace Participant send rollback in class com.arjuna.wst11.messaging.CoordinatorProcessorImpl > 16:41:50,583 INFO [stdout] (MSC service thread 1-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.CoordinatorProcessorImpl.prepared(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace Participant send rollback > 16:41:50,587 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace Participant send rollback in class com.arjuna.wst11.messaging.CoordinatorProcessorImpl > 16:41:50,607 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate coordinator close in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:50,607 INFO [stdout] (MSC service thread 1-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator.rollback() void for rule trace subordinate coordinator close > 16:41:50,608 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate coordinator close in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:50,609 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate coordinator prepare in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:50,609 INFO [stdout] (MSC service thread 1-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator.prepare() int for rule trace subordinate coordinator prepare > 16:41:50,610 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate coordinator prepare in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:50,611 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate coordinator rollback 2 in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:50,612 INFO [stdout] (MSC service thread 1-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator.rollback() void for rule trace subordinate coordinator rollback 2 > 16:41:50,613 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate coordinator rollback 2 in class com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateATCoordinator > 16:41:50,632 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : possible trigger for rule trace delete participant and exit JVM in class org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple > 16:41:50,633 INFO [stdout] (MSC service thread 1-4) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple.deleteParticipantRecoveryRecord(java.lang.String) boolean for rule trace delete participant and exit JVM > 16:41:50,634 INFO [stdout] (MSC service thread 1-4) org.jboss.byteman.agent.Transformer : inserted trigger for trace delete participant and exit JVM in class org.jboss.jbossts.xts.recovery.participant.at.XTSATRecoveryManagerImple > 16:41:50,661 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033013: OutboundBridgeRecoveryManager starting > 16:41:50,661 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-4) ARJUNA033006: InboundBridgeRecoveryManager starting > 16:41:50,749 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000169: Jandex cannot distinguish inner and static nested classes! Update Jandex to 2.0.3.Final version or newer to improve scanning performance. > 16:41:51,008 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 73) Starting XTSServiceTestRunner > 16:41:51,008 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 73) Started XTSServiceTestRunner > 16:41:51,017 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 73) Initializing Mojarra 2.2.13.SP1 20160303-1204 for context '/xtstest' > 16:41:51,377 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0021: Registered web context: '/xtstest' for server 'default-server' > 16:41:51,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") > 16:41:51,391 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "restat-web-5.4.1.Final-SNAPSHOT.war" (runtime-name : "restat-web-5.4.1.Final-SNAPSHOT.war") > 16:41:51,449 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 16:41:51,449 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 16:41:51,450 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 3.0.0.Alpha12 "Kenny" started in 4409ms - Started 671 of 918 services (462 services are lazy, passive or on-demand) > Nov 15, 2016 4:41:51 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill > INFO: Hard killing of a server instance > Nov 15, 2016 4:41:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: waiting for byteman to kill the server > Nov 15, 2016 4:41:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:42:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:42:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:42:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:42:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > 16:42:18,935 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace subordinate prepared replay in class org.jboss.jbossts.xts.recovery.coordinator.at.RecoverySubordinateATCoordinator > 16:42:18,937 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.recovery.coordinator.at.RecoverySubordinateATCoordinator.replayPhase2() void for rule trace subordinate prepared replay > 16:42:18,938 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace subordinate prepared replay in class org.jboss.jbossts.xts.recovery.coordinator.at.RecoverySubordinateATCoordinator > 16:42:18,977 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace Coordinator engine create in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:18,978 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.(java.lang.String,boolean,javax.xml.ws.wsaddressing.W3CEndpointReference,boolean,com.arjuna.webservices11.wsat.State) void for rule trace Coordinator engine create > 16:42:18,991 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace Coordinator engine create in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:18,992 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive Participant aborted in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:18,992 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.aborted(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive Participant aborted > 16:42:19,002 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive Participant aborted in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,004 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive participant prepared in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,004 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.prepared(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive participant prepared > 16:42:19,015 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive participant prepared in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,017 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send participant prepare in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,018 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.prepare() com.arjuna.webservices11.wsat.State for rule trace send participant prepare > 16:42:19,028 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace send participant prepare in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,029 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send Participant rollback in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,030 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.CoordinatorEngine.rollback() com.arjuna.webservices11.wsat.State for rule trace send Participant rollback > 16:42:19,040 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace send Participant rollback in class com.arjuna.wst11.messaging.engines.CoordinatorEngine > 16:42:19,042 INFO [stdout] (Periodic Recovery) Rule.execute called for trace Coordinator engine create_12 > 16:42:19,042 INFO [stdout] (Periodic Recovery) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,042 INFO [stdout] (Periodic Recovery) calling installed(trace Coordinator engine create) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,042 INFO [stdout] (Periodic Recovery) Installed rule using default helper : trace Coordinator engine create > 16:42:19,042 INFO [stdout] (Periodic Recovery) trace Coordinator engine create execute > 16:42:19,043 INFO [stdout] (Periodic Recovery) rule.debug{trace Coordinator engine create} : created recovered Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:20 > 16:42:19,054 INFO [stdout] (Periodic Recovery) Rule.execute called for trace Coordinator engine create_12 > 16:42:19,054 INFO [stdout] (Periodic Recovery) trace Coordinator engine create execute > 16:42:19,054 INFO [stdout] (Periodic Recovery) rule.debug{trace Coordinator engine create} : created recovered Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:23 > 16:42:19,054 INFO [stdout] (Periodic Recovery) Rule.execute called for trace subordinate prepared replay_11 > 16:42:19,057 INFO [stdout] (Periodic Recovery) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,057 INFO [stdout] (Periodic Recovery) calling installed(trace subordinate prepared replay) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,057 INFO [stdout] (Periodic Recovery) Installed rule using default helper : trace subordinate prepared replay > 16:42:19,057 INFO [stdout] (Periodic Recovery) trace subordinate prepared replay execute > 16:42:19,057 INFO [stdout] (Periodic Recovery) rule.debug{trace subordinate prepared replay} : reinstated prepared subordinate transaction 0:ffffac110007:-3ffa9bb3:582b3abd:19 > 16:42:19,062 INFO [stdout] (Periodic Recovery) xts service test : attempting to deserialize WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:42:19,064 INFO [stdout] (Periodic Recovery) xts service test : deserialized WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:42:19,065 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace Participant create in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,066 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.(com.arjuna.wst.Participant,java.lang.String,com.arjuna.webservices11.wsat.State,javax.xml.ws.wsaddressing.W3CEndpointReference,boolean) void for rule trace Participant create > 16:42:19,078 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace Participant create in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,079 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive participant prepare in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,079 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.prepare(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive participant prepare > 16:42:19,086 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive participant prepare in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,087 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send Participant prepared in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,093 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.sendPrepared(boolean) void for rule trace send Participant prepared > 16:42:19,093 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace send Participant prepared in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,095 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace receive Participant rollback in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,096 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.rollback(org.oasis_open.docs.ws_tx.wsat._2006._06.Notification,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule trace receive Participant rollback > 16:42:19,102 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace receive Participant rollback in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,103 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : possible trigger for rule trace send Participant aborted in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,109 INFO [stdout] (Periodic Recovery) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantEngine.sendAborted() void for rule trace send Participant aborted > 16:42:19,109 INFO [stdout] (Periodic Recovery) org.jboss.byteman.agent.Transformer : inserted trigger for trace send Participant aborted in class com.arjuna.wst11.messaging.engines.ParticipantEngine > 16:42:19,111 INFO [stdout] (Periodic Recovery) Rule.execute called for trace Participant create_17 > 16:42:19,111 INFO [stdout] (Periodic Recovery) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,111 INFO [stdout] (Periodic Recovery) calling installed(trace Participant create) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,111 INFO [stdout] (Periodic Recovery) Installed rule using default helper : trace Participant create > 16:42:19,111 INFO [stdout] (Periodic Recovery) trace Participant create execute > 16:42:19,111 INFO [stdout] (Periodic Recovery) rule.debug{trace Participant create} : created recovered Participant engine org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:42:19,118 INFO [stdout] (Periodic Recovery) Rule.execute called for trace send Participant prepared_19 > 16:42:19,118 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace send Participant prepared_19 > 16:42:19,227 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Periodic Recovery) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:42:19,520 INFO [stdout] (Periodic Recovery) xts service test : attempting to deserialize WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:42:19,520 INFO [stdout] (Periodic Recovery) xts service test : deserialized WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:42:19,520 INFO [stdout] (Periodic Recovery) Rule.execute called for trace Participant create_17 > 16:42:19,520 INFO [stdout] (Periodic Recovery) trace Participant create execute > 16:42:19,520 INFO [stdout] (Periodic Recovery) rule.debug{trace Participant create} : created recovered Participant engine org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:42:19,521 INFO [stdout] (Periodic Recovery) Rule.execute called for trace send Participant prepared_19 > 16:42:19,521 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace send Participant prepared_19 > 16:42:19,530 INFO [stdout] (TaskWorker-1) Rule.execute called for trace receive participant prepared_14 > 16:42:19,530 INFO [stdout] (TaskWorker-1) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,530 INFO [stdout] (TaskWorker-1) calling installed(trace receive participant prepared) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,531 INFO [stdout] (TaskWorker-1) Installed rule using default helper : trace receive participant prepared > 16:42:19,531 INFO [stdout] (TaskWorker-1) trace receive participant prepared execute > 16:42:19,531 INFO [stdout] (TaskWorker-1) rule.debug{trace receive participant prepared} : prepared received for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:23 > 16:42:19,532 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Periodic Recovery) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:42:19,550 INFO [stdout] (Periodic Recovery) xts service test : attempting to deserialize WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:42:19,550 INFO [stdout] (Periodic Recovery) xts service test : deserialized WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:42:19,551 INFO [stdout] (TaskWorker-1) Rule.execute called for trace receive participant prepared_14 > 16:42:19,551 INFO [stdout] (Periodic Recovery) Rule.execute called for trace Participant create_17 > 16:42:19,551 INFO [stdout] (TaskWorker-1) trace receive participant prepared execute > 16:42:19,551 INFO [stdout] (Periodic Recovery) trace Participant create execute > 16:42:19,551 INFO [stdout] (TaskWorker-1) rule.debug{trace receive participant prepared} : prepared received for Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:20 > 16:42:19,551 INFO [stdout] (Periodic Recovery) rule.debug{trace Participant create} : created recovered Participant engine org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:42:19,551 INFO [stdout] (Periodic Recovery) Rule.execute called for trace send Participant prepared_19 > 16:42:19,551 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace send Participant prepared_19 > 16:42:19,560 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Periodic Recovery) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:42:19,576 WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046033: Compensating orphaned subordinate WS-AT transcation 0:ffffac110007:-3ffa9bb3:582b3abd:19 > 16:42:19,576 INFO [stdout] (Periodic Recovery) Rule.execute called for trace subordinate coordinator close_7 > 16:42:19,576 INFO [stdout] (Periodic Recovery) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,577 INFO [stdout] (Periodic Recovery) calling installed(trace subordinate coordinator close) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,577 INFO [stdout] (Periodic Recovery) Installed rule using default helper : trace subordinate coordinator close > 16:42:19,577 INFO [stdout] (Periodic Recovery) trace subordinate coordinator close execute > 16:42:19,577 INFO [stdout] (Periodic Recovery) rule.debug{trace subordinate coordinator close} : rollback called for subordinate coordinator BasicAction: 0:ffffac110007:-3ffa9bb3:582b3abd:19 status: ActionStatus.COMMITTING > 16:42:19,577 INFO [stdout] (Periodic Recovery) Rule.execute called for trace send Participant rollback_16 > 16:42:19,577 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace send Participant rollback_16 > 16:42:19,583 WARN [com.arjuna.wst] (TaskWorker-1) ARJUNA043134: Prepared called on unknown coordinator: D0:ffffac110007:-3ffa9bb3:582b3abd:16 > 16:42:19,583 INFO [stdout] (TaskWorker-1) Rule.execute called for trace Participant send rollback_6 > 16:42:19,583 INFO [stdout] (TaskWorker-1) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,583 INFO [stdout] (TaskWorker-1) calling installed(trace Participant send rollback) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,583 INFO [stdout] (TaskWorker-1) Installed rule using default helper : trace Participant send rollback > 16:42:19,584 INFO [stdout] (TaskWorker-1) trace Participant send rollback execute > 16:42:19,584 INFO [stdout] (TaskWorker-1) rule.debug{trace Participant send rollback} : sent rollback for unknown Coordinator engine D0:ffffac110007:-3ffa9bb3:582b3abd:16 > 16:42:19,588 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:42:19,599 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Periodic Recovery) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:42:19,600 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:42:19,638 INFO [stdout] (TaskWorker-1) Rule.execute called for trace receive Participant rollback_20 > 16:42:19,638 INFO [stdout] (TaskWorker-1) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,638 INFO [stdout] (TaskWorker-1) calling installed(trace receive Participant rollback) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,638 INFO [stdout] (TaskWorker-1) Installed rule using default helper : trace receive Participant rollback > 16:42:19,638 INFO [stdout] (TaskWorker-1) trace receive Participant rollback execute > 16:42:19,639 INFO [stdout] (TaskWorker-1) rule.debug{trace receive Participant rollback} : rollback received for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:42:19,639 INFO [stdout] (TaskWorker-1) Rule.execute called for trace delete participant and exit JVM_10 > 16:42:19,639 INFO [stdout] (TaskWorker-1) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,639 INFO [stdout] (TaskWorker-1) calling installed(trace delete participant and exit JVM) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,639 INFO [stdout] (TaskWorker-1) Installed rule using default helper : trace delete participant and exit JVM > 16:42:19,639 INFO [stdout] (TaskWorker-1) trace delete participant and exit JVM execute > 16:42:19,640 INFO [stdout] (TaskWorker-1) Rule.execute called for trace send Participant aborted_21 > 16:42:19,640 INFO [stdout] (TaskWorker-1) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,640 INFO [stdout] (TaskWorker-1) calling installed(trace send Participant aborted) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,640 INFO [stdout] (TaskWorker-1) Installed rule using default helper : trace send Participant aborted > 16:42:19,640 INFO [stdout] (TaskWorker-1) trace send Participant aborted execute > 16:42:19,640 INFO [stdout] (TaskWorker-1) rule.debug{trace send Participant aborted} : aborted sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 > 16:42:19,650 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:42:19,667 INFO [stdout] (TaskWorker-1) Rule.execute called for trace receive Participant rollback_20 > 16:42:19,668 INFO [stdout] (TaskWorker-1) trace receive Participant rollback execute > 16:42:19,668 INFO [stdout] (TaskWorker-1) rule.debug{trace receive Participant rollback} : rollback received for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:42:19,669 INFO [stdout] (TaskWorker-1) Rule.execute called for trace delete participant and exit JVM_10 > 16:42:19,669 INFO [stdout] (TaskWorker-1) trace delete participant and exit JVM execute > 16:42:19,669 INFO [stdout] (TaskWorker-1) Rule.execute called for trace send Participant aborted_21 > 16:42:19,670 INFO [stdout] (TaskWorker-1) trace send Participant aborted execute > 16:42:19,669 WARN [com.arjuna.wst] (TaskWorker-2) ARJUNA043130: Aborted called on unknown coordinator: D0:ffffac110007:-3ffa9bb3:582b3abd:16 > 16:42:19,670 INFO [stdout] (TaskWorker-1) rule.debug{trace send Participant aborted} : aborted sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.1 > 16:42:19,678 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:42:19,694 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive Participant aborted_13 > 16:42:19,694 INFO [stdout] (TaskWorker-2) Rule.execute for decommissioned key trace receive Participant aborted_13 > 16:42:19,694 INFO [stdout] (Periodic Recovery) Rule.execute called for trace send Participant rollback_16 > 16:42:19,694 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace send Participant rollback_16 > 16:42:19,710 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (Periodic Recovery) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}ParticipantService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-participant-binding.wsdl > 16:42:19,728 INFO [stdout] (TaskWorker-1) Rule.execute called for trace receive Participant rollback_20 > 16:42:19,728 INFO [stdout] (TaskWorker-1) trace receive Participant rollback execute > 16:42:19,729 INFO [stdout] (TaskWorker-1) rule.debug{trace receive Participant rollback} : rollback received for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:42:19,729 INFO [stdout] (TaskWorker-1) Rule.execute called for trace delete participant and exit JVM_10 > 16:42:19,729 INFO [stdout] (TaskWorker-1) trace delete participant and exit JVM execute > 16:42:19,729 INFO [stdout] (TaskWorker-1) Rule.execute called for trace send Participant aborted_21 > 16:42:19,729 INFO [stdout] (TaskWorker-1) trace send Participant aborted execute > 16:42:19,730 INFO [stdout] (TaskWorker-1) rule.debug{trace send Participant aborted} : aborted sent for Participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.2 > 16:42:19,738 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (TaskWorker-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CoordinatorService from WSDL: jar:file:/home/jenkins/.m2/repository/org/jboss/narayana/xts/jbossxts/5.4.1.Final-SNAPSHOT/jbossxts-5.4.1.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsat/_2006/_06/wsdl/wsat-coordinator-binding.wsdl > 16:42:19,752 INFO [stdout] (TaskWorker-2) Rule.execute called for trace receive Participant aborted_13 > 16:42:19,752 INFO [stdout] (TaskWorker-2) Rule.execute for decommissioned key trace receive Participant aborted_13 > 16:42:19,753 INFO [stdout] (Periodic Recovery) Rule.execute called for trace remove committed state_5 > 16:42:19,753 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace remove committed state_5 > 16:42:19,753 INFO [stdout] (Periodic Recovery) Rule.execute called for trace remove committed state and exit JVM_4 > 16:42:19,753 INFO [stdout] (Periodic Recovery) Rule.execute for decommissioned key trace remove committed state and exit JVM_4 > 16:42:19,753 INFO [stdout] (Periodic Recovery) Rule.execute called for trace subordinate coordinator rollback 2_9 > 16:42:19,754 INFO [stdout] (Periodic Recovery) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 16:42:19,754 INFO [stdout] (Periodic Recovery) calling installed(trace subordinate coordinator rollback 2) for helper classorg.jboss.byteman.rule.helper.Helper > 16:42:19,754 INFO [stdout] (Periodic Recovery) Installed rule using default helper : trace subordinate coordinator rollback 2 > 16:42:19,754 INFO [stdout] (Periodic Recovery) trace subordinate coordinator rollback 2 execute > 16:42:19,754 INFO [stdout] (Periodic Recovery) rule.debug{trace subordinate coordinator rollback 2} : rollback returned for subordinate coordinator BasicAction: 0:ffffac110007:-3ffa9bb3:582b3abd:19 status: ActionStatus.ABORTED > Nov 15, 2016 4:42:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:42:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:42:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:42:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:42:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:42:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:42:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:42:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:43:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:43:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:43:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:43:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:43:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:43:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:43:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:43:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:43:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:43:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:43:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:43:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:44:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:44:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:44:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:44:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:44:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:44:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:44:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:44:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:44:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:44:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:44:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:44:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:45:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:45:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:45:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:45:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:45:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:45:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:45:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:45:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:45:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:45:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:45:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:45:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:46:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:46:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:46:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:46:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:46:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:46:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:46:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:46:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:46:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:46:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:46:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:46:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:47:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:47:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:47:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:47:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:47:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:47:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:47:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:47:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:47:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:47:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:47:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:47:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:48:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:48:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:48:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:48:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:48:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:48:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:48:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:48:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:48:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:48:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:48:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:48:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:49:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:49:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:49:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:49:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:49:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:49:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:49:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:49:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:49:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:49:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:49:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:49:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:50:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:50:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:50:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:50:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:50:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:50:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:50:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:50:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:50:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:50:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:50:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:50:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:51:01 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:51:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:51:11 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:51:11 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:51:21 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:51:21 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:51:31 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:51:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:51:41 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:51:41 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:51:51 PM com.arjuna.qa.extension.BaseServerKillProcessor kill > INFO: jboss-as is still alive, sleeping for a further 10000ms > Nov 15, 2016 4:51:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommand > INFO: Executing shell command: 'ps aux | grep jboss-module[s] | awk '{print $2}' | xargs kill' > Nov 15, 2016 4:51:51 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > 16:51:51,969 INFO [org.jboss.as.server] (Thread-3) WFLYSRV0220: Server shutdown has been requested via an OS signal > 16:51:51,982 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-6) ARJUNA033007: InboundBridgeRecoveryManager stopping > 16:51:51,982 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 16:51:51,982 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-7) ARJUNA033014: OutboundBridgeRecoveryManager stopping > 16:51:51,984 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > 16:51:51,984 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 77) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 16:51:51,990 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0022: Unregistered web context: '/rest-tx' from server 'default-server' > 16:51:51,990 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 80) WFLYUT0022: Unregistered web context: '/xtstest' from server 'default-server' > 16:51:51,996 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 80) Stopping XTSServiceTestRunner > 16:51:51,996 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 80) Stopped XTSServiceTestRunner > 16:51:51,997 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 16:51:51,997 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 16:51:51,998 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 16:51:51,998 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 16:51:52,012 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 16:51:52,013 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 16:51:52,017 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 78) AMQ151003: resource adaptor stopped > 16:51:52,026 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment restat-web-5.4.1.Final-SNAPSHOT.war (runtime-name: restat-web-5.4.1.Final-SNAPSHOT.war) in 50ms > 16:51:52,031 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment xtstest.war (runtime-name: xtstest.war) in 56ms > 16:51:52,053 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.5.0 [ef9290cb-ab4d-11e6-b97f-0242ac110007] stopped, uptime 10 minutes > Nov 15, 2016 4:51:56 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > 16:51:59,834 WARN [org.apache.activemq.artemis.service.extensions.xa.recovery] (Periodic Recovery) AMQ122015: Can not connect to XARecoveryConfig [transportConfiguration=[TransportConfiguration(name=, factory=org-apache-activemq-artemis-core-remoting-impl-invm-InVMConnectorFactory) ?serverId=0], discoveryConfiguration=null, username=null, password=****, JNDI_NAME=java:/JmsXA] on auto-generated resource recovery: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:785) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.connect(ActiveMQXAResourceWrapper.java:311) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.getDelegate(ActiveMQXAResourceWrapper.java:239) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.recover(ActiveMQXAResourceWrapper.java:69) > at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.recover(ActiveMQXAResourceWrapperImpl.java:106) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:770) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:461) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:218) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) > 16:51:59,834 WARN [org.apache.activemq.artemis.service.extensions.xa.recovery] (Periodic Recovery) AMQ122008: XA Recovery can not connect to any broker on recovery [XARecoveryConfig [transportConfiguration=[TransportConfiguration(name=, factory=org-apache-activemq-artemis-core-remoting-impl-invm-InVMConnectorFactory) ?serverId=0], discoveryConfiguration=null, username=null, password=****, JNDI_NAME=java:/JmsXA]] > 16:51:59,835 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMFAIL: javax.transaction.xa.XAException: Error trying to connect to any providers for xa recovery > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.getDelegate(ActiveMQXAResourceWrapper.java:258) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.recover(ActiveMQXAResourceWrapper.java:69) > at org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperImpl.recover(ActiveMQXAResourceWrapperImpl.java:106) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:770) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:461) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:218) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=null] > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.connect(ActiveMQXAResourceWrapper.java:345) > at org.apache.activemq.artemis.service.extensions.xa.recovery.ActiveMQXAResourceWrapper.getDelegate(ActiveMQXAResourceWrapper.java:239) > ... 7 more > 16:51:59,836 INFO [org.jboss.as.webservices] (MSC service thread 1-5) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-coordinator > 16:51:59,836 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-c11 > 16:51:59,836 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-client > 16:51:59,836 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-participant > 16:51:59,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0022: Unregistered web context: '/ws-t11-coordinator' from server 'default-server' > 16:51:59,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: '/ws-c11' from server 'default-server' > 16:51:59,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0022: Unregistered web context: '/ws-t11-participant' from server 'default-server' > 16:51:59,837 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0022: Unregistered web context: '/ws-t11-client' from server 'default-server' > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-7) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 16:51:59,838 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 16:51:59,837 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 16:51:59,838 INFO [org.jboss.as.webservices] (MSC service thread 1-8) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 16:51:59,838 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-c11 > 16:51:59,838 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-coordinator > 16:51:59,838 INFO [org.jboss.as.webservices] (MSC service thread 1-6) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-client > 16:51:59,838 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-participant > 16:51:59,838 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0019: Host default-host stopping > 16:51:59,841 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0008: Undertow HTTP listener default suspending > 16:51:59,841 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HTTPS listener https suspending > 16:51:59,841 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 16:51:59,841 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HTTPS listener https stopped, was bound to 127.0.0.1:8443 > 16:51:59,842 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0004: Undertow 1.4.4.Final stopping > 16:51:59,849 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0050: WildFly Core 3.0.0.Alpha12 "Kenny" stopped in 7870ms > Nov 15, 2016 4:52:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor runShellCommandExitCode > INFO: Executing shell command: 'if [ "x`ps aux | grep 'jboss-module[s]'`" = "x" ]; then exit 1; fi' > Nov 15, 2016 4:52:01 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor shutdownJBoss > INFO: jboss-as shutdown after sending shutdown command > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2653) Make the service context id for JTS coordinator propagation configurable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2653. ------------------------------- > Make the service context id for JTS coordinator propagation configurable > ------------------------------------------------------------------------ > > Key: JBTM-2653 > URL: https://issues.jboss.org/browse/JBTM-2653 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS > Affects Versions: 5.3.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.6.0.Final > > > JTS transaction propagation uses a CORBA service context to transmit the coordinator object reference. We use a proprietary id to identify this context but if we want to interoperate with foreign transaction managers we need to use the standard value of zero. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2766) Allow Transactional Driver to be used with commons-dbcp in Tomcat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2766. ------------------------------- > Allow Transactional Driver to be used with commons-dbcp in Tomcat > ----------------------------------------------------------------- > > Key: JBTM-2766 > URL: https://issues.jboss.org/browse/JBTM-2766 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.6.0.Final > > > Transactional driver does not provide connection pooling but commons-dbcp (as used in Tomcat) does. We should test it and provide a demonstration and blog post of its usage. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2623) WildFly to GlassFish interop: Check that transaction propagation works In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2623. ------------------------------- > WildFly to GlassFish interop: Check that transaction propagation works > ---------------------------------------------------------------------- > > Key: JBTM-2623 > URL: https://issues.jboss.org/browse/JBTM-2623 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.6.0.Final > > > This subtask is for testing transaction propagation only, JBTM-2873 is for the recovery part of this issue. > This task facilitates the resolution of JBTM-223 Check WL-to-JBossTS interoperability (via JTS). > Whilst developing a test for recovery with WebLogic I was unable to make progress due to issue \[1\] (basically registering resources for recovery fails). Checking recovery using glassfish may be easier since the source code is readily available and may help with figuring out the correct solution with WL. > \[1\] According to [https://docs.oracle.com/cd/E12839_01/web.1111/e13731/jtatxexp.htm#WLJTA279] > XA resources can be registered for recovery via a singleton bean that runs at start up and registers them with the WL transaction manager. When I do this I get the exception as shown: > {quote} > javax.transaction.SystemException: Resource 'Dummy'can be registered only in a server process > at org.glassfish.transaction.TransactionManagerImplCommon.registerStaticResource(TransactionManagerImplCommon.java:695) > at org.jboss.narayana.RecoveryBean.register(RecoveryBean.java:61) > at org.jboss.narayana.RecoveryBean.init(RecoveryBean.java:30) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethod(Jsr250Metadata.java:377) > at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethods(Jsr250Metadata.java:352) > at com.oracle.pitchfork.intercept.InterceptionMetadata.invokeLifecycleMethods(InterceptionMetadata.java:399) > at weblogic.ejb.container.injection.EjbComponentCreatorImpl.invokePostConstruct(EjbComponentCreatorImpl.java:55) > at weblogic.ejb.container.manager.SingletonSessionManager.constructAndInitBean(SingletonSessionManager.java:330) > at weblogic.ejb.container.manager.SingletonSessionManager.access$300(SingletonSessionManager.java:62) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.doActualInit(SingletonSessionManager.java:753) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.initInternal(SingletonSessionManager.java:701) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.init(SingletonSessionManager.java:588) > at weblogic.ejb.container.manager.SingletonSessionManager.init(SingletonSessionManager.java:255) > at weblogic.ejb.container.manager.SingletonSessionManager.perhapsInit(SingletonSessionManager.java:251) > at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:968) > at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:597) > at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360) > at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138) > at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124) > at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:216) > at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:211) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:73) > at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24) > at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258) > at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48) > at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) > at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:226) > at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:418) > at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51) > at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200) > at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) > at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240) > at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) > at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) > at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:210) > at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:118) > at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:78) > at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.glassfish.hk2.utilities.reflection.ReflectionHelper.invoke(ReflectionHelper.java:1017) > at org.jvnet.hk2.internal.ClazzCreator.postConstructMe(ClazzCreator.java:388) > at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:430) > at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456) > at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225) > at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82) > at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98) > at org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:606) > at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:77) > at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:231) > at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:254) > at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:413) > at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456) > at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225) > at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82) > at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:87) > at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1162) > at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1147) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:263) > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2873) WildFly to GlassFish interop: check that recovery works In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2873: -------------------------------- Fix Version/s: 5.next (was: 5.6.0.Final) > WildFly to GlassFish interop: check that recovery works > ------------------------------------------------------- > > Key: JBTM-2873 > URL: https://issues.jboss.org/browse/JBTM-2873 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS > Affects Versions: 5.5.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Check interoperability between WildFly and GlassFish. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:02 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2865) Cache store can get an NPE as work is written to outside of _workList lock In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2865. ------------------------------- > Cache store can get an NPE as work is written to outside of _workList lock > -------------------------------------------------------------------------- > > Key: JBTM-2865 > URL: https://issues.jboss.org/browse/JBTM-2865 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.6.0.Final > > > {code} > java.lang.NullPointerException > at com.arjuna.ats.internal.arjuna.objectstore.AsyncStore.getState(CacheStore.java:579) > at com.arjuna.ats.internal.arjuna.objectstore.CacheStore.read_state(CacheStore.java:130) > at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.read_state_internal(FileSystemStore.java:331) > at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.read_committed(FileSystemStore.java:103) > at com.hp.mwtests.ts.arjuna.objectstore.ThreadWriter.run(CachedTest.java:69) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:03 -0400 (EDT) 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 ] Tom Jenkinson updated JBTM-2841: -------------------------------- Fix Version/s: 5.next (was: 5.6.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.2.3#72005) From issues at jboss.org Wed May 24 05:04:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:03 -0400 (EDT) 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 ] Tom Jenkinson updated JBTM-2851: -------------------------------- Fix Version/s: 5.next (was: 5.6.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.2.3#72005) From issues at jboss.org Wed May 24 05:04:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2867) Investigate un-_workList protected access to _work object In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2867: -------------------------------- Fix Version/s: 5.next (was: 5.6.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.2.3#72005) From issues at jboss.org Wed May 24 05:04:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2833) Move deprecated tooling classes into an internal package In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2833: -------------------------------- Fix Version/s: 5.next (was: 5.6.0.Final) > Move deprecated tooling classes into an internal package > -------------------------------------------------------- > > Key: JBTM-2833 > URL: https://issues.jboss.org/browse/JBTM-2833 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tooling > Affects Versions: 5.5.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > commit 66a9291f56f (JBTM-2308]) "Mark classes deprecated since we need to rejig package names" marked many/most of the tooling instrumentation classes deprecated - these need to be moved to internal packages and the then marked as not deprecated. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 24 05:04:03 2017 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 May 2017 05:04:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2831) Fix RTS inbound bridge participant deserialiser registration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2831: -------------------------------- Fix Version/s: 5.next (was: 5.6.0.Final) > Fix RTS inbound bridge participant deserialiser registration > ------------------------------------------------------------ > > Key: JBTM-2831 > URL: https://issues.jboss.org/browse/JBTM-2831 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Inbound bridge participant deserialiser is registered when InboundBridgeManager is created [1]. That deserialiser is immediately used to recreate participants and update REST-AT coordinator via its HTTP resource. > In WildFly deserialiser registration used to be triggered by creating InboundBridgeManager instance in InboundBridgeService#start method. > However, Undertow subsystem update was introduced which collected and held all HTTP requests until application server completed boot-up. This caused a lock because HTTP call to REST-AT coordinator was being held and InboundBridgeService was waiting for the response. As a result server never completed boot. > Tom has removed that initialisation as a workaround [2]. Everything still works, because inbound bridge recovery manager initialises InboundBridgeManager too. However, only in the second pass. This causes warnings messages during the first cycle of the recovery by REST-AT recovery module. > I'm suggesting to remove deserialiser registration from InboundBridgeManager constructor to keep it as simple as possible and move it to other place were it could be invoked safely and on time e.g. start of first pass of InboundBridgeRecoveryModule. > [1] https://github.com/jbosstm/narayana/blob/5.5.0.Final/rts/at/bridge/src/main/java/org/jboss/narayana/rest/bridge/inbound/InboundBridgeManager.java#L60 > [2] https://github.com/wildfly/wildfly/commit/6bc2e6a20b665201505f12c1c22fda9768a083ea -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Tue May 30 13:28:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 30 May 2017 13:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2901) XARecoveryModule second pass shouldn't be executed if the state is not BETWEEN_PASSES In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2901: ------------------------------------- Summary: XARecoveryModule second pass shouldn't be executed if the state is not BETWEEN_PASSES Key: JBTM-2901 URL: https://issues.jboss.org/browse/JBTM-2901 Project: JBoss Transaction Manager Issue Type: Bug Components: Recovery Reporter: Gytis Trikleris Assignee: Michael Musgrove -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 31 03:51:00 2017 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 31 May 2017 03:51:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2901) XARecoveryModule second pass shouldn't be executed if the state is not BETWEEN_PASSES In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #1184 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > XARecoveryModule second pass shouldn't be executed if the state is not BETWEEN_PASSES > ------------------------------------------------------------------------------------- > > Key: JBTM-2901 > URL: https://issues.jboss.org/browse/JBTM-2901 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 31 09:52:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 31 May 2017 09:52:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2902) Transactional driver connections do not handle empty credentials correctly In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2902: ------------------------------------- Summary: Transactional driver connections do not handle empty credentials correctly Key: JBTM-2902 URL: https://issues.jboss.org/browse/JBTM-2902 Project: JBoss Transaction Manager Issue Type: Bug Components: Transactional Driver Reporter: Gytis Trikleris Assignee: Gytis Trikleris Transactional driver connections only check for null credentials. If they are empty strings they are used as actual username and password, which is incorrect. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 31 09:57:00 2017 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 31 May 2017 09:57:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2902) Transactional driver connections do not handle empty credentials correctly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2902: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1182 > Transactional driver connections do not handle empty credentials correctly > -------------------------------------------------------------------------- > > Key: JBTM-2902 > URL: https://issues.jboss.org/browse/JBTM-2902 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > > Transactional driver connections only check for null credentials. If they are empty strings they are used as actual username and password, which is incorrect. -- This message was sent by Atlassian JIRA (v7.2.3#72005) From issues at jboss.org Wed May 31 17:09:02 2017 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Wed, 31 May 2017 17:09:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2870) Provide way of getting suppressed exceptions out of SubordinateTransaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414623#comment-13414623 ] RH Bugzilla Integration commented on JBTM-2870: ----------------------------------------------- Vladimir Dosoudil changed the Status of [bug 1435549|https://bugzilla.redhat.com/show_bug.cgi?id=1435549] from MODIFIED to ON_QA > Provide way of getting suppressed exceptions out of SubordinateTransaction > -------------------------------------------------------------------------- > > Key: JBTM-2870 > URL: https://issues.jboss.org/browse/JBTM-2870 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 4.17.38, 5.5.5.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 4.17.40, 5.2.23.Final, 5.5.7.Final, 5.6.0.Final > > > We need to provide way how to pass suppressed exceptions of of the `SubordinateTransaction` to the caller. > This request came from customer case and https://bugzilla.redhat.com/show_bug.cgi?id=1435549 as we need to provide exceptions thrown from transaction resource. > The interface is used for controlling propagated transaction from one server to another in EAP/WFLY. > Callers are is ejb3 subsystem in EAP 6.4/7.0 and WFTC in EAP 7.1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)