From issues at jboss.org Mon Jan 4 01:59:00 2016 From: issues at jboss.org (=?UTF-8?Q?Ond=C5=99ej_Chaloupka_=28JIRA=29?=) Date: Mon, 4 Jan 2016 01:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2597) Failed commit during one-phase commit optimization only logs warning and lets EJB invocation succeed In-Reply-To: References: Message-ID: Ond?ej Chaloupka created JBTM-2597: -------------------------------------- Summary: Failed commit during one-phase commit optimization only logs warning and lets EJB invocation succeed Key: JBTM-2597 URL: https://issues.jboss.org/browse/JBTM-2597 Project: JBoss Transaction Manager Issue Type: Bug Environment: Ubuntu Linux 32Bit, Java 8, WildFly 8.2.1.Final Reporter: Ond?ej Chaloupka Assignee: Michael Musgrove Fix For: 5.2.10.Final I have an entity manager (Oracle XA datasource) and a JCA resource adapter supporting LocalTransaction in one transaction. Following scenario: - An entity with values equal to those in the database is merged - The commit() of the local-tx resource fails and throws a ResourceException All that happens is a warning being logged: {noformat} 00:34:47,619 WARN [com.arjuna.ats.jta] (default task-24) ARJUNA016039: onePhaseCommit on < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000101:25752588:566c9884:209, node_name=1, branch_uid=0:ffff7f000101:25752588:566c9884:211, subordinatenodename=null, eis_name=java:/FileDataSource > (LocalXAResourceImpl at 41ac4d[connectionListener=d5fa3f connectionManager=1e7041 warned=false currentXid=null productName=Generic JCA productVersion=1.0 jndiName=java:/FileDataSource]) failed with exception XAException.XA_RBROLLBACK: org.jboss.jca.core.spi.transaction.local.LocalXAException: IJ001156: Could not commit local transaction at org.jboss.jca.core.tx.jbossts.LocalXAResourceImpl.commit(LocalXAResourceImpl.java:180) [ironjacamar-core-impl-1.1.9.Final.jar:1.1.9.Final] at com.arjuna.ats.internal.jta.resources.arjunacore.XAOnePhaseResource.commit(XAOnePhaseResource.java:113) at com.arjuna.ats.internal.arjuna.abstractrecords.LastResourceRecord.topLevelPrepare(LastResourceRecord.java:152) at com.arjuna.ats.arjuna.coordinator.AbstractRecord.topLevelOnePhaseCommit(AbstractRecord.java:428) at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2317) at com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(BasicAction.java:2110) at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1481) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:96) at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1166) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:93) [wildfly-ejb3-8.2.1.Final.jar:8.2.1.Final] {noformat} and the EJB invocation succeeds. I would expect the EJB to receive a RollbackException since the commit failed with XAException.XA_RBROLLBACK. Debugging BasicAction.prepare(), I can see that because the outcome of prepare is TwoPhaseOutcome.PREPARE_READONLY, one phase commit optimization is applied and onePhaseCommit() is called where the outcome TwoPhaseOutcome.ONE_PHASE_ERROR isn't considered an error as far as I understand. Then TwoPhaseOutcome.PREPARE_ONE_PHASE_COMMITTED is returned from BasicAction.prepare(). I would never expect the EJB invocation to succeed if any participant in the transaction fails to commit. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:27:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:27:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2592) Incorrect warning messaging in ShadowingStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144361#comment-13144361 ] Tom Jenkinson commented on JBTM-2592: ------------------------------------- Hi Mark, it was added here: https://github.com/jbosstm/narayana/commit/e0cd8687ad9763c511a7878a2faddc46d5f87898 > Incorrect warning messaging in ShadowingStore > --------------------------------------------- > > Key: JBTM-2592 > URL: https://issues.jboss.org/browse/JBTM-2592 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > > warn_objectstore_ShadowingStore_6 currently says ... > "ShadowingStore::read_state() - no type name given for object state" > ... when in fact the else clause is triggered when the state isn't committed or uncommitted (typically when it's unknown and the state doesn't exist). > I'm not sure when this warning message was added because it wasn't there in JBossTS 4.8 or 4.15.3. > I'm going to fix this issue (the text). I'll create a separate issue because I think this should be info not warning. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:30:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2593) Suggest making this read_state INFO not WARN In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144362#comment-13144362 ] Tom Jenkinson commented on JBTM-2593: ------------------------------------- It was added for JBTM-2168 within commit https://github.com/jbosstm/narayana/commit/e0cd8687ad9763c511a7878a2faddc46d5f87898 > Suggest making this read_state INFO not WARN > -------------------------------------------- > > Key: JBTM-2593 > URL: https://issues.jboss.org/browse/JBTM-2593 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > > I'm not sure why it was added or why it's a warning. Maybe should be info or debug? > read_state operation, ShadowingStore_6 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:35:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:35:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2594) Link some doc chapters at higher levels on the project site In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144363#comment-13144363 ] Tom Jenkinson commented on JBTM-2594: ------------------------------------- I don't think we link to the specific blacktie docs, just its javadocs - and that is only because they aren't integrated into the main build. I will create a new issue to merge the BlackTie javadocs into the main Narayana ones. I agree that linking to specific sections of the docs would still be useful from the site. One thing we would need to consider is how to make sure docbook generates links that don't look random (#d0e16062 in your example). > Link some doc chapters at higher levels on the project site > ----------------------------------------------------------- > > Key: JBTM-2594 > URL: https://issues.jboss.org/browse/JBTM-2594 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Documentation > Affects Versions: 5.2.11.Final > Reporter: Mark Little > > On the main Narayana site (http://narayana.io) we call out the higher level components such as JTA, STM, Orb Portability etc. However, on the docs page (http://narayana.io/documentation/index.html), apart from Blacktie the reader needs to load and read through the entire doc (or manually search) for the relevant sections. Maybe link the relevant chapters (such as http://narayana.io/docs/project/index.html#d0e16062) in the docs pages and/or the top level of the site, so someone looking for the JTS or STM docs can click there immediately. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:37:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2598) Merge in BlackTie Javadocs to main Narayana javadocs In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2598: ----------------------------------- Summary: Merge in BlackTie Javadocs to main Narayana javadocs Key: JBTM-2598 URL: https://issues.jboss.org/browse/JBTM-2598 Project: JBoss Transaction Manager Issue Type: Task Components: Build System, Documentation Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Minor Fix For: 5.next The BlackTie javadocs are still separate http://narayana.io/documentation/index.html - it would be useful to ensure that they are in the same place as the rest of the Narayana javadocs. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:38:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2595) TransactionalDriver consuming all database connections In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2595: -------------------------------- Component/s: Transactional Driver > TransactionalDriver consuming all database connections > ------------------------------------------------------ > > Key: JBTM-2595 > URL: https://issues.jboss.org/browse/JBTM-2595 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA, Transactional Driver > Affects Versions: 5.2.11.Final > Environment: Windows 7, Java 8, Spring 4.1.7, Hibernate 5.0.1, PostgreSQL > Reporter: Karsten Ohme > > I'm using Narayana in a Spring / Hibernate Set Up for running a distributed Infinispan cache. During the start up of the application Spring Security is fetching several access control entries from the database. These are several hundred requests. The TransactionManager is creating always a new connection and I can see in the PostgreSQL console that all connections are used up until PostgreSQL is not allowing any connections anymore. > What is needed is a blocking feature. I think Apache DBCP has something like this and is blocking calls until connections are available again. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:46:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:46:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2591) WildFly quick start example fails to build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2591: -------------------------------- Component/s: (was: Application Server Integration) > WildFly quick start example fails to build > ------------------------------------------ > > Key: JBTM-2591 > URL: https://issues.jboss.org/browse/JBTM-2591 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Amos Feng > > Trying to build the example here ... > https://github.com/jbosstm/quickstart/tree/master/wildfly/setCheckedActionFactoryExample > The pom refers to a version of JTA that isn't in the repo, so it fails. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 19.553 s > [INFO] Finished at: 2015-12-24T15:30:31+00:00 > [INFO] Final Memory: 8M/149M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project setCheckedActionFactoryExample: Could not resolve dependencies for project org.jboss.narayana:setCheckedActionFactoryExample:war:0.0.1-SNAPSHOT: Could not find artifact org.jboss.narayana.jta:jta:jar:5.2.12.Final-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] > Changing to 5.2.9.Final at least lets the example build (and hopefully run). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:50:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:50:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2591) WildFly quick start example fails to build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144367#comment-13144367 ] Tom Jenkinson commented on JBTM-2591: ------------------------------------- I will add the following text to the Readme.md (https://github.com/jbosstm/quickstart/blob/master/wildfly/setCheckedActionFactoryExample/README.md): Replace: {quote} You will need a WildFly server {quote} {quote} If you are using the "master" version of the quickstarts, you will need to build Narayana master locally (https://github.com/jbosstm/narayana/). If you are using a tagged version of the quickstarts then the artifact should exist in JBoss nexus (or maven central). You will also need the current version of WildFly to run this quickstart. WildFly is available from http://wildfly.org/downloads/ {quote} > WildFly quick start example fails to build > ------------------------------------------ > > Key: JBTM-2591 > URL: https://issues.jboss.org/browse/JBTM-2591 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Amos Feng > > Trying to build the example here ... > https://github.com/jbosstm/quickstart/tree/master/wildfly/setCheckedActionFactoryExample > The pom refers to a version of JTA that isn't in the repo, so it fails. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 19.553 s > [INFO] Finished at: 2015-12-24T15:30:31+00:00 > [INFO] Final Memory: 8M/149M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project setCheckedActionFactoryExample: Could not resolve dependencies for project org.jboss.narayana:setCheckedActionFactoryExample:war:0.0.1-SNAPSHOT: Could not find artifact org.jboss.narayana.jta:jta:jar:5.2.12.Final-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] > Changing to 5.2.9.Final at least lets the example build (and hopefully run). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:50:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:50:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2591) WildFly quick start example fails to build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144367#comment-13144367 ] Tom Jenkinson edited comment on JBTM-2591 at 1/4/16 4:50 AM: ------------------------------------------------------------- I will add the following text to the Readme.md (https://github.com/jbosstm/quickstart/blob/master/wildfly/setCheckedActionFactoryExample/README.md): Replace: {quote} You will need a WildFly server {quote} With: {quote} If you are using the "master" version of the quickstarts, you will need to build Narayana master locally (https://github.com/jbosstm/narayana/). If you are using a tagged version of the quickstarts then the artifact should exist in JBoss nexus (or maven central). You will also need the current version of WildFly to run this quickstart. WildFly is available from http://wildfly.org/downloads/ {quote} was (Author: tomjenkinson): I will add the following text to the Readme.md (https://github.com/jbosstm/quickstart/blob/master/wildfly/setCheckedActionFactoryExample/README.md): Replace: {quote} You will need a WildFly server {quote} {quote} If you are using the "master" version of the quickstarts, you will need to build Narayana master locally (https://github.com/jbosstm/narayana/). If you are using a tagged version of the quickstarts then the artifact should exist in JBoss nexus (or maven central). You will also need the current version of WildFly to run this quickstart. WildFly is available from http://wildfly.org/downloads/ {quote} > WildFly quick start example fails to build > ------------------------------------------ > > Key: JBTM-2591 > URL: https://issues.jboss.org/browse/JBTM-2591 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Amos Feng > > Trying to build the example here ... > https://github.com/jbosstm/quickstart/tree/master/wildfly/setCheckedActionFactoryExample > The pom refers to a version of JTA that isn't in the repo, so it fails. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 19.553 s > [INFO] Finished at: 2015-12-24T15:30:31+00:00 > [INFO] Final Memory: 8M/149M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project setCheckedActionFactoryExample: Could not resolve dependencies for project org.jboss.narayana:setCheckedActionFactoryExample:war:0.0.1-SNAPSHOT: Could not find artifact org.jboss.narayana.jta:jta:jar:5.2.12.Final-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] > Changing to 5.2.9.Final at least lets the example build (and hopefully run). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:52:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:52:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2591) WildFly quick start example fails to build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #157 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > WildFly quick start example fails to build > ------------------------------------------ > > Key: JBTM-2591 > URL: https://issues.jboss.org/browse/JBTM-2591 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Amos Feng > > Trying to build the example here ... > https://github.com/jbosstm/quickstart/tree/master/wildfly/setCheckedActionFactoryExample > The pom refers to a version of JTA that isn't in the repo, so it fails. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 19.553 s > [INFO] Finished at: 2015-12-24T15:30:31+00:00 > [INFO] Final Memory: 8M/149M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project setCheckedActionFactoryExample: Could not resolve dependencies for project org.jboss.narayana:setCheckedActionFactoryExample:war:0.0.1-SNAPSHOT: Could not find artifact org.jboss.narayana.jta:jta:jar:5.2.12.Final-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] > Changing to 5.2.9.Final at least lets the example build (and hopefully run). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:53:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2591) WildFly quick start example fails to build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144369#comment-13144369 ] Tom Jenkinson commented on JBTM-2591: ------------------------------------- I linked in a PR > WildFly quick start example fails to build > ------------------------------------------ > > Key: JBTM-2591 > URL: https://issues.jboss.org/browse/JBTM-2591 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Amos Feng > > Trying to build the example here ... > https://github.com/jbosstm/quickstart/tree/master/wildfly/setCheckedActionFactoryExample > The pom refers to a version of JTA that isn't in the repo, so it fails. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 19.553 s > [INFO] Finished at: 2015-12-24T15:30:31+00:00 > [INFO] Final Memory: 8M/149M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project setCheckedActionFactoryExample: Could not resolve dependencies for project org.jboss.narayana:setCheckedActionFactoryExample:war:0.0.1-SNAPSHOT: Could not find artifact org.jboss.narayana.jta:jta:jar:5.2.12.Final-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] > Changing to 5.2.9.Final at least lets the example build (and hopefully run). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:58:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2592) Incorrect warning messaging in ShadowingStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2592: --------------------------------- > Incorrect warning messaging in ShadowingStore > --------------------------------------------- > > Key: JBTM-2592 > URL: https://issues.jboss.org/browse/JBTM-2592 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > > warn_objectstore_ShadowingStore_6 currently says ... > "ShadowingStore::read_state() - no type name given for object state" > ... when in fact the else clause is triggered when the state isn't committed or uncommitted (typically when it's unknown and the state doesn't exist). > I'm not sure when this warning message was added because it wasn't there in JBossTS 4.8 or 4.15.3. > I'm going to fix this issue (the text). I'll create a separate issue because I think this should be info not warning. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:58:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2592) Incorrect warning messaging in ShadowingStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2592: -------------------------------- Fix Version/s: 5.next > Incorrect warning messaging in ShadowingStore > --------------------------------------------- > > Key: JBTM-2592 > URL: https://issues.jboss.org/browse/JBTM-2592 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > Fix For: 5.next > > > warn_objectstore_ShadowingStore_6 currently says ... > "ShadowingStore::read_state() - no type name given for object state" > ... when in fact the else clause is triggered when the state isn't committed or uncommitted (typically when it's unknown and the state doesn't exist). > I'm not sure when this warning message was added because it wasn't there in JBossTS 4.8 or 4.15.3. > I'm going to fix this issue (the text). I'll create a separate issue because I think this should be info not warning. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:58:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2592) Incorrect warning messaging in ShadowingStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2592. ------------------------------- Resolution: Done > Incorrect warning messaging in ShadowingStore > --------------------------------------------- > > Key: JBTM-2592 > URL: https://issues.jboss.org/browse/JBTM-2592 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > Fix For: 5.next > > > warn_objectstore_ShadowingStore_6 currently says ... > "ShadowingStore::read_state() - no type name given for object state" > ... when in fact the else clause is triggered when the state isn't committed or uncommitted (typically when it's unknown and the state doesn't exist). > I'm not sure when this warning message was added because it wasn't there in JBossTS 4.8 or 4.15.3. > I'm going to fix this issue (the text). I'll create a separate issue because I think this should be info not warning. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:59:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2593) Suggest making this read_state INFO not WARN In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2593: --------------------------------- > Suggest making this read_state INFO not WARN > -------------------------------------------- > > Key: JBTM-2593 > URL: https://issues.jboss.org/browse/JBTM-2593 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > > I'm not sure why it was added or why it's a warning. Maybe should be info or debug? > read_state operation, ShadowingStore_6 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:59:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2593) Suggest making this read_state INFO not WARN In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2593: -------------------------------- Fix Version/s: 5.next > Suggest making this read_state INFO not WARN > -------------------------------------------- > > Key: JBTM-2593 > URL: https://issues.jboss.org/browse/JBTM-2593 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > Fix For: 5.next > > > I'm not sure why it was added or why it's a warning. Maybe should be info or debug? > read_state operation, ShadowingStore_6 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 04:59:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 04:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2593) Suggest making this read_state INFO not WARN In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2593. ------------------------------- Resolution: Done > Suggest making this read_state INFO not WARN > -------------------------------------------- > > Key: JBTM-2593 > URL: https://issues.jboss.org/browse/JBTM-2593 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > Fix For: 5.next > > > I'm not sure why it was added or why it's a warning. Maybe should be info or debug? > read_state operation, ShadowingStore_6 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 05:15:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 05:15:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144384#comment-13144384 ] Tom Jenkinson commented on JBTM-2583: ------------------------------------- Prototype: https://github.com/jbosstm/narayana/pull/957 > Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > ------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.later > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > There are a couple of advantages to this: > 1. In the common case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > 2. In the case where the recovery manager and transaction manager are distributed, the current behaviour of orphan detection can be employed (or the timeout interval extended) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 05:15:00 2016 From: issues at jboss.org (Anonymous (JIRA)) Date: Mon, 4 Jan 2016 05:15:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2583) Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when pull request #957 was created in GitHub --------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Try to contact the transaction status connection manager to determine if a transaction containing XAResources is still in-flight before relying on orphan detection > ------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2583 > URL: https://issues.jboss.org/browse/JBTM-2583 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.later > > > Currently we use a timeout based system to determine if prepared Xids that a ResourceManager knows about but where the transaction is not prepared yet are the result of a pre-prepare crash or whether it is just slow progress of the resources/transaction manager. > This issue is to record an enhancement to the recovery manager for XAResources to attempt to contact the transaction manager to determine if an Xid is indoubt before rolling it back. > > There are a couple of advantages to this: > 1. In the common case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > 2. In the case where the recovery manager and transaction manager are distributed, the current behaviour of orphan detection can be employed (or the timeout interval extended) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 06:05:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 06:05:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2595) TransactionalDriver consuming all database connections In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2595: -------------------------------- Issue Type: Feature Request (was: Bug) > TransactionalDriver consuming all database connections > ------------------------------------------------------ > > Key: JBTM-2595 > URL: https://issues.jboss.org/browse/JBTM-2595 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA, Transactional Driver > Affects Versions: 5.2.11.Final > Environment: Windows 7, Java 8, Spring 4.1.7, Hibernate 5.0.1, PostgreSQL > Reporter: Karsten Ohme > > I'm using Narayana in a Spring / Hibernate Set Up for running a distributed Infinispan cache. During the start up of the application Spring Security is fetching several access control entries from the database. These are several hundred requests. The TransactionManager is creating always a new connection and I can see in the PostgreSQL console that all connections are used up until PostgreSQL is not allowing any connections anymore. > What is needed is a blocking feature. I think Apache DBCP has something like this and is blocking calls until connections are available again. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 06:05:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 06:05:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2595) TransactionalDriver consuming all database connections In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2595: -------------------------------- Component/s: (was: JTA) > TransactionalDriver consuming all database connections > ------------------------------------------------------ > > Key: JBTM-2595 > URL: https://issues.jboss.org/browse/JBTM-2595 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transactional Driver > Affects Versions: 5.2.11.Final > Environment: Windows 7, Java 8, Spring 4.1.7, Hibernate 5.0.1, PostgreSQL > Reporter: Karsten Ohme > > I'm using Narayana in a Spring / Hibernate Set Up for running a distributed Infinispan cache. During the start up of the application Spring Security is fetching several access control entries from the database. These are several hundred requests. The TransactionManager is creating always a new connection and I can see in the PostgreSQL console that all connections are used up until PostgreSQL is not allowing any connections anymore. > What is needed is a blocking feature. I think Apache DBCP has something like this and is blocking calls until connections are available again. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 06:13:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 06:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2595) TransactionalDriver consuming all database connections In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144416#comment-13144416 ] Tom Jenkinson commented on JBTM-2595: ------------------------------------- This would be better discussed over in the forum: https://developer.jboss.org/en/jbosstm/content?filterID=contentstatus%5bpublished%5d~objecttype~objecttype%5bthread%5d When discussing, please provide the configuration you are using (including datasource configuration as pooling is implemented already in PostGres driver - org.postgresql.ds.PGPoolingDataSource). TransactionalDriver will reuse connections for the same transaction if configured to do so: https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jdbc/classes/com/arjuna/ats/internal/jdbc/ConnectionManager.java#L69 I will close this for now, we can reopen depending upon how the discussion goes. Thanks for your interest, Tom > TransactionalDriver consuming all database connections > ------------------------------------------------------ > > Key: JBTM-2595 > URL: https://issues.jboss.org/browse/JBTM-2595 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transactional Driver > Affects Versions: 5.2.11.Final > Environment: Windows 7, Java 8, Spring 4.1.7, Hibernate 5.0.1, PostgreSQL > Reporter: Karsten Ohme > > I'm using Narayana in a Spring / Hibernate Set Up for running a distributed Infinispan cache. During the start up of the application Spring Security is fetching several access control entries from the database. These are several hundred requests. The TransactionManager is creating always a new connection and I can see in the PostgreSQL console that all connections are used up until PostgreSQL is not allowing any connections anymore. > What is needed is a blocking feature. I think Apache DBCP has something like this and is blocking calls until connections are available again. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 06:13:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 Jan 2016 06:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2595) TransactionalDriver consuming all database connections In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2595. ------------------------------- Resolution: Incomplete Description > TransactionalDriver consuming all database connections > ------------------------------------------------------ > > Key: JBTM-2595 > URL: https://issues.jboss.org/browse/JBTM-2595 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transactional Driver > Affects Versions: 5.2.11.Final > Environment: Windows 7, Java 8, Spring 4.1.7, Hibernate 5.0.1, PostgreSQL > Reporter: Karsten Ohme > > I'm using Narayana in a Spring / Hibernate Set Up for running a distributed Infinispan cache. During the start up of the application Spring Security is fetching several access control entries from the database. These are several hundred requests. The TransactionManager is creating always a new connection and I can see in the PostgreSQL console that all connections are used up until PostgreSQL is not allowing any connections anymore. > What is needed is a blocking feature. I think Apache DBCP has something like this and is blocking calls until connections are available again. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 19:16:00 2016 From: issues at jboss.org (Luis Barreiro (JIRA)) Date: Mon, 4 Jan 2016 19:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artimes to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: Luis Barreiro created JBTM-2599: ----------------------------------- Summary: Update activemq-artimes to 1.1.0.wildfly-010 Key: JBTM-2599 URL: https://issues.jboss.org/browse/JBTM-2599 Project: JBoss Transaction Manager Issue Type: Bug Components: Application Server Integration Reporter: Luis Barreiro Assignee: Amos Feng -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 19:21:00 2016 From: issues at jboss.org (Anonymous (JIRA)) Date: Mon, 4 Jan 2016 19:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artimes to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Luis Barreiro created pull request #966 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Update activemq-artimes to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 4 20:59:00 2016 From: issues at jboss.org (Luis Barreiro (JIRA)) Date: Mon, 4 Jan 2016 20:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luis Barreiro updated JBTM-2599: -------------------------------- Summary: Update activemq-artemis to 1.1.0.wildfly-010 (was: Update activemq-artimes to 1.1.0.wildfly-010) > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 01:54:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 5 Jan 2016 01:54:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2600) Upgrade Wildfly to 10.0.0.Final-SNAPSHOT In-Reply-To: References: Message-ID: Amos Feng created JBTM-2600: ------------------------------- Summary: Upgrade Wildfly to 10.0.0.Final-SNAPSHOT Key: JBTM-2600 URL: https://issues.jboss.org/browse/JBTM-2600 Project: JBoss Transaction Manager Issue Type: Task Components: Application Server Integration Reporter: Amos Feng Assignee: Amos Feng -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 06:24:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 5 Jan 2016 06:24:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2600) Upgrade Wildfly to 10.0.0.Final-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Amos Feng created pull request #967 in GitHub --------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade Wildfly to 10.0.0.Final-SNAPSHOT > ---------------------------------------- > > Key: JBTM-2600 > URL: https://issues.jboss.org/browse/JBTM-2600 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 07:29:00 2016 From: issues at jboss.org (=?UTF-8?Q?St=C3=A5le_Pedersen_=28JIRA=29?=) Date: Tue, 5 Jan 2016 07:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] St?le Pedersen updated JBTM-2599: --------------------------------- Priority: Blocker (was: Major) > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Amos Feng > Priority: Blocker > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 07:29:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 5 Jan 2016 07:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2601) Blacktie subsystem pom using old version of narayana-jts-idlj In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2601: ------------------------------------- Summary: Blacktie subsystem pom using old version of narayana-jts-idlj Key: JBTM-2601 URL: https://issues.jboss.org/browse/JBTM-2601 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Reporter: Gytis Trikleris Assignee: Amos Feng Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 07:29:01 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 5 Jan 2016 07:29:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2601) Blacktie subsystem pom using old version of narayana-jts-idlj In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144936#comment-13144936 ] Gytis Trikleris commented on JBTM-2601: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-catelyn/1072 > Blacktie subsystem pom using old version of narayana-jts-idlj > ------------------------------------------------------------- > > Key: JBTM-2601 > URL: https://issues.jboss.org/browse/JBTM-2601 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 07:30:00 2016 From: issues at jboss.org (=?UTF-8?Q?St=C3=A5le_Pedersen_=28JIRA=29?=) Date: Tue, 5 Jan 2016 07:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144937#comment-13144937 ] St?le Pedersen commented on JBTM-2599: -------------------------------------- Without this fix we cannot use the aio journal, this is critical to get into WF10. > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Amos Feng > Priority: Blocker > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 07:32:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 5 Jan 2016 07:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2588) WildFly BAParticipantCompletionTestCase failed with UndeclaredThrowableException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144939#comment-13144939 ] Gytis Trikleris commented on JBTM-2588: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/PROFILE=XTS,jdk=jdk8.latest,label=linux/1015 > WildFly BAParticipantCompletionTestCase failed with UndeclaredThrowableException > -------------------------------------------------------------------------------- > > Key: JBTM-2588 > URL: https://issues.jboss.org/browse/JBTM-2588 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase > ------------------------------------------------------------------------------- > Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 103.782 sec <<< FAILURE! - in org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase > testWSBAParticipantClientCancel(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 59.832 sec <<< ERROR! > java.lang.reflect.UndeclaredThrowableException: null > at com.sun.proxy.$Proxy25.runTestMethod(Unknown Source) > at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:80) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.io.IOException: Unable to invoke invoke(), status=WAITING > at org.jboss.remotingjmx.protocol.v2.ClientConnection$TheConnection.invoke(ClientConnection.java:1072) > at org.jboss.as.arquillian.container.ManagementClient$MBeanConnectionProxy.invoke(ManagementClient.java:560) > at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:298) > at com.sun.proxy.$Proxy25.runTestMethod(Unknown Source) > at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:80) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 07:32:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 5 Jan 2016 07:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2588) WildFly XTS tests failed with UndeclaredThrowableException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2588: ---------------------------------- Summary: WildFly XTS tests failed with UndeclaredThrowableException (was: WildFly BAParticipantCompletionTestCase failed with UndeclaredThrowableException) > WildFly XTS tests failed with UndeclaredThrowableException > ---------------------------------------------------------- > > Key: JBTM-2588 > URL: https://issues.jboss.org/browse/JBTM-2588 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase > ------------------------------------------------------------------------------- > Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 103.782 sec <<< FAILURE! - in org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase > testWSBAParticipantClientCancel(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 59.832 sec <<< ERROR! > java.lang.reflect.UndeclaredThrowableException: null > at com.sun.proxy.$Proxy25.runTestMethod(Unknown Source) > at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:80) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.io.IOException: Unable to invoke invoke(), status=WAITING > at org.jboss.remotingjmx.protocol.v2.ClientConnection$TheConnection.invoke(ClientConnection.java:1072) > at org.jboss.as.arquillian.container.ManagementClient$MBeanConnectionProxy.invoke(ManagementClient.java:560) > at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:298) > at com.sun.proxy.$Proxy25.runTestMethod(Unknown Source) > at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:80) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 07:45:01 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 5 Jan 2016 07:45:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2601) Blacktie subsystem pom using old version of narayana-jts-idlj In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144954#comment-13144954 ] Amos Feng commented on JBTM-2601: --------------------------------- I think it might be related to JBTM-2600 > Blacktie subsystem pom using old version of narayana-jts-idlj > ------------------------------------------------------------- > > Key: JBTM-2601 > URL: https://issues.jboss.org/browse/JBTM-2601 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 07:46:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 5 Jan 2016 07:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2599: ---------------------------- Fix Version/s: 5.next > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 07:55:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 5 Jan 2016 07:55:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2602) QA test suite failure on DB2: TestGroup_txcore_lockrecord In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2602: ------------------------------------- Summary: QA test suite failure on DB2: TestGroup_txcore_lockrecord Key: JBTM-2602 URL: https://issues.jboss.org/browse/JBTM-2602 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Gytis Trikleris Assignee: Michael Musgrove Priority: Minor Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 09:07:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 09:07:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2600) Upgrade Wildfly to 10.0.0.Final-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2600: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade Wildfly to 10.0.0.Final-SNAPSHOT > ---------------------------------------- > > Key: JBTM-2600 > URL: https://issues.jboss.org/browse/JBTM-2600 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 09:26:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 5 Jan 2016 09:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2601) Blacktie subsystem pom using old version of narayana-jts-idlj In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng resolved JBTM-2601. ----------------------------- Resolution: Done > Blacktie subsystem pom using old version of narayana-jts-idlj > ------------------------------------------------------------- > > Key: JBTM-2601 > URL: https://issues.jboss.org/browse/JBTM-2601 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 09:35:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 09:35:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2601) Blacktie subsystem pom using old version of narayana-jts-idlj In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145017#comment-13145017 ] Tom Jenkinson commented on JBTM-2601: ------------------------------------- +1, I guess it is using .CR5-SNAPSHOT version of WFLY rather than the .Final-SNAPSHOT version > Blacktie subsystem pom using old version of narayana-jts-idlj > ------------------------------------------------------------- > > Key: JBTM-2601 > URL: https://issues.jboss.org/browse/JBTM-2601 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 10:12:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 10:12:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145053#comment-13145053 ] Tom Jenkinson commented on JBTM-2599: ------------------------------------- [~stalep] I have no problem with doing a release with this in but I think Narayana will use the one in WFLY anyway so you could just upgrade the version of the journal in there? > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 10:27:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 10:27:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145065#comment-13145065 ] Tom Jenkinson commented on JBTM-2599: ------------------------------------- Maybe WFLY pulls our version of Artemis transitively or something? Anyway, will merge when the PR passes - should be an hour or two. > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 10:31:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 10:31:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2599: ----------------------------------- Assignee: Luis Barreiro (was: Amos Feng) > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 11:01:00 2016 From: issues at jboss.org (Luis Barreiro (JIRA)) Date: Tue, 5 Jan 2016 11:01:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145088#comment-13145088 ] Luis Barreiro commented on JBTM-2599: ------------------------------------- [~tomjenkinson] WildFly ships with it's own Artemis (including the journal) and Narayana reuses it. One of the last changes that went in WF10-CR5 was the upgrade of Artemis and among other things the JounalImpl now has an extra feature, making it backwards incompatible. Sure the fix could be made on Artemis side, but having it this way is the right way to do it and allow us to be able to explore that feature in the future. > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:17:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:17:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145166#comment-13145166 ] Tom Jenkinson commented on JBTM-2599: ------------------------------------- [~lbarreiro] - understood. Will do the release as the PR passed. It will be tomorrow AM (UK) though. I don't think characterising this as a bug (in Narayana) is correct so changing the issue type. Also, please can you add a description? Probably just replicate your comment https://issues.jboss.org/browse/JBTM-2599?focusedCommentId=13145088&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13145088 > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:17:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:17:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2599: -------------------------------- Issue Type: Component Upgrade (was: Bug) > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:18:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:18:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2599: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:20:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:20:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2589) JTA QA testsuite failure: JTATests01_Test006 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2589: --------------------------------- > JTA QA testsuite failure: JTATests01_Test006 > -------------------------------------------- > > Key: JBTM-2589 > URL: https://issues.jboss.org/browse/JBTM-2589 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA, Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:20:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:20:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2589) JTA QA testsuite failure: JTATests01_Test006 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2589: -------------------------------- Fix Version/s: (was: 5.next) > JTA QA testsuite failure: JTATests01_Test006 > -------------------------------------------- > > Key: JBTM-2589 > URL: https://issues.jboss.org/browse/JBTM-2589 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA, Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:20:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:20:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2589) JTA QA testsuite failure: JTATests01_Test006 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2589. ------------------------------- Resolution: Won't Fix > JTA QA testsuite failure: JTATests01_Test006 > -------------------------------------------- > > Key: JBTM-2589 > URL: https://issues.jboss.org/browse/JBTM-2589 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA, Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:21:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2600) Upgrade Wildfly to 10.0.0.Final-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2600: -------------------------------- Fix Version/s: 5.next > Upgrade Wildfly to 10.0.0.Final-SNAPSHOT > ---------------------------------------- > > Key: JBTM-2600 > URL: https://issues.jboss.org/browse/JBTM-2600 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:21:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2601) Blacktie subsystem pom using old version of narayana-jts-idlj In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2601: --------------------------------- > Blacktie subsystem pom using old version of narayana-jts-idlj > ------------------------------------------------------------- > > Key: JBTM-2601 > URL: https://issues.jboss.org/browse/JBTM-2601 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:21:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:21:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2601) Blacktie subsystem pom using old version of narayana-jts-idlj In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2601. ------------------------------- Fix Version/s: (was: 5.next) Resolution: Duplicate Issue > Blacktie subsystem pom using old version of narayana-jts-idlj > ------------------------------------------------------------- > > Key: JBTM-2601 > URL: https://issues.jboss.org/browse/JBTM-2601 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2591) WildFly quick start example fails to build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2591: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > WildFly quick start example fails to build > ------------------------------------------ > > Key: JBTM-2591 > URL: https://issues.jboss.org/browse/JBTM-2591 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.next > > > Trying to build the example here ... > https://github.com/jbosstm/quickstart/tree/master/wildfly/setCheckedActionFactoryExample > The pom refers to a version of JTA that isn't in the repo, so it fails. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 19.553 s > [INFO] Finished at: 2015-12-24T15:30:31+00:00 > [INFO] Final Memory: 8M/149M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project setCheckedActionFactoryExample: Could not resolve dependencies for project org.jboss.narayana:setCheckedActionFactoryExample:war:0.0.1-SNAPSHOT: Could not find artifact org.jboss.narayana.jta:jta:jar:5.2.12.Final-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] > Changing to 5.2.9.Final at least lets the example build (and hopefully run). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2591) WildFly quick start example fails to build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2591: -------------------------------- Issue Type: Task (was: Bug) > WildFly quick start example fails to build > ------------------------------------------ > > Key: JBTM-2591 > URL: https://issues.jboss.org/browse/JBTM-2591 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.next > > > Trying to build the example here ... > https://github.com/jbosstm/quickstart/tree/master/wildfly/setCheckedActionFactoryExample > The pom refers to a version of JTA that isn't in the repo, so it fails. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 19.553 s > [INFO] Finished at: 2015-12-24T15:30:31+00:00 > [INFO] Final Memory: 8M/149M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project setCheckedActionFactoryExample: Could not resolve dependencies for project org.jboss.narayana:setCheckedActionFactoryExample:war:0.0.1-SNAPSHOT: Could not find artifact org.jboss.narayana.jta:jta:jar:5.2.12.Final-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] > Changing to 5.2.9.Final at least lets the example build (and hopefully run). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2591) Improve WildFly quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2591: -------------------------------- Summary: Improve WildFly quickstart documentation (was: WildFly quick start example fails to build) > Improve WildFly quickstart documentation > ---------------------------------------- > > Key: JBTM-2591 > URL: https://issues.jboss.org/browse/JBTM-2591 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.next > > > Trying to build the example here ... > https://github.com/jbosstm/quickstart/tree/master/wildfly/setCheckedActionFactoryExample > The pom refers to a version of JTA that isn't in the repo, so it fails. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 19.553 s > [INFO] Finished at: 2015-12-24T15:30:31+00:00 > [INFO] Final Memory: 8M/149M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project setCheckedActionFactoryExample: Could not resolve dependencies for project org.jboss.narayana:setCheckedActionFactoryExample:war:0.0.1-SNAPSHOT: Could not find artifact org.jboss.narayana.jta:jta:jar:5.2.12.Final-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] > Changing to 5.2.9.Final at least lets the example build (and hopefully run). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2600) Upgrade Wildfly to 10.0.0.Final-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2600. ------------------------------- > Upgrade Wildfly to 10.0.0.Final-SNAPSHOT > ---------------------------------------- > > Key: JBTM-2600 > URL: https://issues.jboss.org/browse/JBTM-2600 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.2.12.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2599. ------------------------------- > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 5.2.12.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2591) Improve WildFly quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2591. ------------------------------- > Improve WildFly quickstart documentation > ---------------------------------------- > > Key: JBTM-2591 > URL: https://issues.jboss.org/browse/JBTM-2591 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.2.12.Final > > > Trying to build the example here ... > https://github.com/jbosstm/quickstart/tree/master/wildfly/setCheckedActionFactoryExample > The pom refers to a version of JTA that isn't in the repo, so it fails. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 19.553 s > [INFO] Finished at: 2015-12-24T15:30:31+00:00 > [INFO] Final Memory: 8M/149M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project setCheckedActionFactoryExample: Could not resolve dependencies for project org.jboss.narayana:setCheckedActionFactoryExample:war:0.0.1-SNAPSHOT: Could not find artifact org.jboss.narayana.jta:jta:jar:5.2.12.Final-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] > Changing to 5.2.9.Final at least lets the example build (and hopefully run). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2590) Compensations quickstarts need to include nexus as a repo in case the maven central sync has not fired In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2590. ------------------------------- > Compensations quickstarts need to include nexus as a repo in case the maven central sync has not fired > ------------------------------------------------------------------------------------------------------ > > Key: JBTM-2590 > URL: https://issues.jboss.org/browse/JBTM-2590 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.2.12.Final > > > Discovered in current build: > {quote} > Downloading: http://repo.maven.apache.org/maven2/org/jboss/narayana/xts/jbossxts/5.2.11.Final/jbossxts-5.2.11.Final.pom > > [WARNING] The POM for org.jboss.narayana.xts:jbossxts:jar:api:5.2.11.Final is missing, no dependency information available > Downloading: http://repo.maven.apache.org/maven2/org/jboss/narayana/compensations/compensations/5.2.11.Final/compensations-5.2.11.Final.pom > > [WARNING] The POM for org.jboss.narayana.compensations:compensations:jar:5.2.11.Final is missing, no dependency information available > Downloading: http://repo.maven.apache.org/maven2/org/jboss/narayana/xts/jbossxts/5.2.11.Final/jbossxts-5.2.11.Final-api.jar > Downloading: http://repo.maven.apache.org/maven2/org/jboss/narayana/compensations/compensations/5.2.11.Final/compensations-5.2.11.Final.jar > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2602) QA test suite failure on DB2: TestGroup_txcore_lockrecord In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2602: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > QA test suite failure on DB2: TestGroup_txcore_lockrecord > --------------------------------------------------------- > > Key: JBTM-2602 > URL: https://issues.jboss.org/browse/JBTM-2602 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2598) Merge in BlackTie Javadocs to main Narayana javadocs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2598: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Merge in BlackTie Javadocs to main Narayana javadocs > ---------------------------------------------------- > > Key: JBTM-2598 > URL: https://issues.jboss.org/browse/JBTM-2598 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > The BlackTie javadocs are still separate http://narayana.io/documentation/index.html - it would be useful to ensure that they are in the same place as the rest of the Narayana javadocs. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2588) WildFly XTS tests failed with UndeclaredThrowableException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2588: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > WildFly XTS tests failed with UndeclaredThrowableException > ---------------------------------------------------------- > > Key: JBTM-2588 > URL: https://issues.jboss.org/browse/JBTM-2588 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase > ------------------------------------------------------------------------------- > Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 103.782 sec <<< FAILURE! - in org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase > testWSBAParticipantClientCancel(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 59.832 sec <<< ERROR! > java.lang.reflect.UndeclaredThrowableException: null > at com.sun.proxy.$Proxy25.runTestMethod(Unknown Source) > at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:80) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.io.IOException: Unable to invoke invoke(), status=WAITING > at org.jboss.remotingjmx.protocol.v2.ClientConnection$TheConnection.invoke(ClientConnection.java:1072) > at org.jboss.as.arquillian.container.ManagementClient$MBeanConnectionProxy.invoke(ManagementClient.java:560) > at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:298) > at com.sun.proxy.$Proxy25.runTestMethod(Unknown Source) > at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:80) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2586) XTS tests failures in WF testsuite In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2586: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > XTS tests failures in WF testsuite > ---------------------------------- > > Key: JBTM-2586 > URL: https://issues.jboss.org/browse/JBTM-2586 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > {code} > Running org.jboss.as.test.xts.wsat.client.ATTestCase > Tests run: 9, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 11.74 sec <<< FAILURE! - in org.jboss.as.test.xts.wsat.client.ATTestCase > testWSATApplicationExceptionCommit(org.jboss.as.test.xts.wsat.client.ATTestCase) Time elapsed: 0.286 sec <<< ERROR! > org.jboss.arquillian.test.spi.ArquillianProxyException: javax.xml.ws.soap.SOAPFaultException : Error when enlisting participants [Proxied because : Original exception caused: class java.io.NotSerializableException: com.sun.xml.messaging.saaj.soap.ver1_1.SOAPPart1_1Impl] > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:86) > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:52) > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:41) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:112) > at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:140) > at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:71) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:798) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1669) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > at com.sun.proxy.$Proxy176.invoke(Unknown Source) > at org.jboss.as.test.xts.wsat.client.ATTestCase.testWSATApplicationExceptionCommit(ATTestCase.java:227) > testWSATRollbackOnly(org.jboss.as.test.xts.wsat.client.ATTestCase) Time elapsed: 0.12 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.startTransaction(UserTransactionImple.java:308) > at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.begin(UserTransactionImple.java:80) > at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.begin(UserTransactionImple.java:70) > at org.jboss.as.test.xts.wsat.client.ATTestCase.testWSATRollbackOnly(ATTestCase.java:172) > Running org.jboss.as.test.xts.annotation.client.TransactionalTestCase > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.725 sec <<< FAILURE! - in org.jboss.as.test.xts.annotation.client.TransactionalTestCase > testActiveTransaction(org.jboss.as.test.xts.annotation.client.TransactionalTestCase) Time elapsed: 0.018 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.startTransaction(UserTransactionImple.java:308) > at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.begin(UserTransactionImple.java:80) > at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.begin(UserTransactionImple.java:70) > at org.jboss.as.test.xts.annotation.client.TransactionalTestCase.testActiveTransaction(TransactionalTestCase.java:78) > Running org.jboss.as.test.xts.annotation.client.CompensatableTestCase > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.411 sec <<< FAILURE! - in org.jboss.as.test.xts.annotation.client.CompensatableTestCase > testActiveTransaction(org.jboss.as.test.xts.annotation.client.CompensatableTestCase) Time elapsed: 0.054 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.annotation.client.CompensatableTestCase.testActiveTransaction(CompensatableTestCase.java:77) > Running org.jboss.as.test.xts.annotation.compensationScoped.CompensationScopedTestCase > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.876 sec - in org.jboss.as.test.xts.annotation.compensationScoped.CompensationScopedTestCase > Running org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase > Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 1.648 sec <<< FAILURE! - in org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase > testWSBAParticipantApplicationException(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.236 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantApplicationException(BAParticipantCompletionTestCase.java:218) > testWSBAParticipantCannotComplete(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.104 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantCannotComplete(BAParticipantCompletionTestCase.java:177) > testWSBAParticipantClientCancelNotComplete(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.095 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantClientCancelNotComplete(BAParticipantCompletionTestCase.java:161) > testWSBAParticipantDoNotComplete(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.07 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantDoNotComplete(BAParticipantCompletionTestCase.java:141) > testWSBAParticipantCompleteSimple(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.067 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantCompleteSimple(BAParticipantCompletionTestCase.java:125) > testWSBAParticipantCompleteSingle(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.106 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantCompleteSingle(BAParticipantCompletionTestCase.java:114) > testWSBAParticipantClientCancel(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.101 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantClientCancel(BAParticipantCompletionTestCase.java:202) > Running org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase > Tests run: 6, Failures: 2, Errors: 4, Skipped: 0, Time elapsed: 0.585 sec <<< FAILURE! - in org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase > testWSBACoordinatorSimple(org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase) Time elapsed: 0.002 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.testWSBACoordinatorSimple(BACoordinatorCompletionTestCase.java:106) > testWSBACoordinatorSingle(org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase) Time elapsed: 0.002 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.testWSBACoordinatorSingle(BACoordinatorCompletionTestCase.java:97) > testWSBACoordinatorCannotComplete(org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase) Time elapsed: 0.002 sec <<< FAILURE! > java.lang.AssertionError: Another status order expected for the bacoordinator_completition_service1 expected:<[CANCEL]> but was: > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.jboss.as.test.xts.base.BaseFunctionalTest.assertEventLog(BaseFunctionalTest.java:85) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.assertEventLogClient1(BACoordinatorCompletionTestCase.java:194) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.testWSBACoordinatorCannotComplete(BACoordinatorCompletionTestCase.java:134) > testWSBACoordinatorApplicationException(org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase) Time elapsed: 0.359 sec <<< ERROR! > org.jboss.arquillian.test.spi.ArquillianProxyException: javax.xml.ws.soap.SOAPFaultException : Fault occurred while processing. [Proxied because : Original exception caused: class java.io.NotSerializableException: com.sun.xml.messaging.saaj.soap.ver1_1.SOAPPart1_1Impl] > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:86) > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:52) > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:41) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:112) > at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:140) > at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:71) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:798) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1669) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > at com.sun.proxy.$Proxy255.saveData(Unknown Source) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.testWSBACoordinatorApplicationException(BACoordinatorCompletionTestCase.java:163) > testWSBACoordinatorCompletionFailToComplete(org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase) Time elapsed: 0.097 sec <<< FAILURE! > java.lang.AssertionError: Another status order expected for the bacoordinator_completition_service1 expected:<[COMPLETE, CONFIRM_COMPLETED, COMPENSATE]> but was: > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.jboss.as.test.xts.base.BaseFunctionalTest.assertEventLog(BaseFunctionalTest.java:85) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.assertEventLogClient1(BACoordinatorCompletionTestCase.java:194) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.testWSBACoordinatorCompletionFailToComplete(BACoordinatorCompletionTestCase.java:185) > testWSBACoordinatorClientCancel(org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase) Time elapsed: 0.06 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.testWSBACoordinatorClientCancel(BACoordinatorCompletionTestCase.java:142) > Results : > Failed tests: > BACoordinatorCompletionTestCase.testWSBACoordinatorCannotComplete:134->assertEventLogClient1:194->BaseFunctionalTest.assertEventLog:85 Another status order expected for the bacoordinator_completition_service1 expected:<[CANCEL]> but was: > BACoordinatorCompletionTestCase.testWSBACoordinatorCompletionFailToComplete:185->assertEventLogClient1:194->BaseFunctionalTest.assertEventLog:85 Another status order expected for the bacoordinator_completition_service1 expected:<[COMPLETE, CONFIRM_COMPLETED, COMPENSATE]> but was: > Tests in error: > ATTestCase.testWSATApplicationExceptionCommit:227 ? ArquillianProxy javax.xml.... > ATTestCase.testWSATRollbackOnly:172 ? System org.apache.cxf.wsdl11.WSDLRuntime... > TransactionalTestCase.testActiveTransaction:78 ? System org.apache.cxf.wsdl11.... > CompensatableTestCase.testActiveTransaction:77 ? System org.apache.cxf.wsdl11.... > BAParticipantCompletionTestCase.testWSBAParticipantApplicationException:218 ? System > BAParticipantCompletionTestCase.testWSBAParticipantCannotComplete:177 ? System > BAParticipantCompletionTestCase.testWSBAParticipantClientCancelNotComplete:161 ? System > BAParticipantCompletionTestCase.testWSBAParticipantDoNotComplete:141 ? System ... > BAParticipantCompletionTestCase.testWSBAParticipantCompleteSimple:125 ? System > BAParticipantCompletionTestCase.testWSBAParticipantCompleteSingle:114 ? System > BAParticipantCompletionTestCase.testWSBAParticipantClientCancel:202 ? System o... > BACoordinatorCompletionTestCase.testWSBACoordinatorSimple:106 ? System org.apa... > BACoordinatorCompletionTestCase.testWSBACoordinatorSingle:97 ? System org.apac... > BACoordinatorCompletionTestCase.testWSBACoordinatorApplicationException:163 ? ArquillianProxy > BACoordinatorCompletionTestCase.testWSBACoordinatorClientCancel:142 ? System o... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2580) Create a Narayana troubleshooting guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2580: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Create a Narayana troubleshooting guide > --------------------------------------- > > Key: JBTM-2580 > URL: https://issues.jboss.org/browse/JBTM-2580 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > This information may already exist but is possibly fragmented. This issue is to record the fact that we need to collate this. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2522) Update performance comparison tests to use JMH In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2522: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Update performance comparison tests to use JMH > ---------------------------------------------- > > Key: JBTM-2522 > URL: https://issues.jboss.org/browse/JBTM-2522 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2517) Update the Narayana Release Process doc to include performance figures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2517: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Update the Narayana Release Process doc to include performance figures > ---------------------------------------------------------------------- > > Key: JBTM-2517 > URL: https://issues.jboss.org/browse/JBTM-2517 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing, Release Process > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Include a description in the NRP document of how to blog about performance figures when releasing a new version of Narayana -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2498: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2497) Update or remove references of HornetQ to Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2497: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Update or remove references of HornetQ to Artemis > ------------------------------------------------- > > Key: JBTM-2497 > URL: https://issues.jboss.org/browse/JBTM-2497 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator, Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > There were reports of HornetQ still in at least the fooapp QS. We should try to remove references to the specific implementation unless necessary and in those cases use the correct name which is now Artemis. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2495: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' 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. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' 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. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2481) Automate NRP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2481: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2480: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Provide documentation of how to integrate with Karaf > ---------------------------------------------------- > > Key: JBTM-2480 > URL: https://issues.jboss.org/browse/JBTM-2480 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > This should include recovery information -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2433: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > TransactionRolledBackException in MultiCloseTest > ------------------------------------------------ > > Key: JBTM-2433 > URL: https://issues.jboss.org/browse/JBTM-2433 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt > > > It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion. > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! > testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2458) Think of the possibility to improve Compensations API with lambdas In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2458: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Think of the possibility to improve Compensations API with lambdas > ------------------------------------------------------------------ > > Key: JBTM-2458 > URL: https://issues.jboss.org/browse/JBTM-2458 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Emmanuel suggested to reduce verbosity in Compensations API by making it possible to use lambdas for handler implementation. > We should try to think of the best API changes to introduce that. > We could rewrite MongoDB quickstart to make it easier to visualise the difference. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2305) Incomplete tooling documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2305: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Incomplete tooling documentation > -------------------------------- > > Key: JBTM-2305 > URL: https://issues.jboss.org/browse/JBTM-2305 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > For tooling the docs defer to the wildfly/EAP cli for "5.1.1. Browse and Manage Transactions Using an Application Server". We had some text in the README explaining how to view the tooling MBeans but the equivalent needs to be added to the development_guide too for use with standalone narayana. > In addition the docs need to explain how to extend the tooling for new abstract records (basically the user needs to create a JMX MBean for the new type and register it with the ObjStoreBrowser). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2298) Use Project Atomic for docker image(s) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2298: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Use Project Atomic for docker image(s) > -------------------------------------- > > Key: JBTM-2298 > URL: https://issues.jboss.org/browse/JBTM-2298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > > When I created the initial docker (POC) image I did so using a standard Fedora base image. We should also look at supporting the Project Atomic docker image, since it's important for Red Hat. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2115) Not all classes are under code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2115: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1804: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > JTS remote tests not run and no code coverage > --------------------------------------------- > > Key: JBTM-1804 > URL: https://issues.jboss.org/browse/JBTM-1804 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.next > > > The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build. > It would then be beneficial to have them instrumented by emma to get code coverage. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2234) out of memory when logging more messages than heap size (surefire issue) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2234: -------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > out of memory when logging more messages than heap size (surefire issue) > ------------------------------------------------------------------------ > > Key: JBTM-2234 > URL: https://issues.jboss.org/browse/JBTM-2234 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.0.2 > Environment: JTS testing > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > Running com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 on JacORB with about 500000 transactions results in an OOM error because surefire keeps in logs in memory until the test has finished. > In this particular test jacorb logs messages at INFO level for each transaction resulting in excessive memory requirements. We can't make the heap too large because the default JVM is 32 bit. However, we could fix it by reducing the jacorb log level to WARN. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 13:46:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 Jan 2016 13:46:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-855: ------------------------------- Fix Version/s: 5.next (was: 5.2.12.Final) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 5 19:11:00 2016 From: issues at jboss.org (=?UTF-8?Q?St=C3=A5le_Pedersen_=28JIRA=29?=) Date: Tue, 5 Jan 2016 19:11:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145226#comment-13145226 ] St?le Pedersen commented on JBTM-2599: -------------------------------------- thanks a lot [~tomjenkinson]! - really nice to get this into wf10. > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 5.2.12.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 6 03:20:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 Jan 2016 03:20:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2599) Update activemq-artemis to 1.1.0.wildfly-010 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145267#comment-13145267 ] Tom Jenkinson commented on JBTM-2599: ------------------------------------- No problem and thanks to [~lbarreiro] for the contribution. > Update activemq-artemis to 1.1.0.wildfly-010 > -------------------------------------------- > > Key: JBTM-2599 > URL: https://issues.jboss.org/browse/JBTM-2599 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: Application Server Integration > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Blocker > Fix For: 5.2.12.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 6 05:54:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 Jan 2016 05:54:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2603) Http request fails with internal server error in EnabledContextPropagationTests In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2603: ------------------------------------- Summary: Http request fails with internal server error in EnabledContextPropagationTests Key: JBTM-2603 URL: https://issues.jboss.org/browse/JBTM-2603 Project: JBoss Transaction Manager Issue Type: Bug Components: TxBridge Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.next {code} testNoTransactionWithDisabledJTAOverWSATFeature(org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests) Time elapsed: 76.255 sec <<< ERROR! org.apache.http.client.HttpResponseException: Internal Server Error at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:68) at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:54) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035) at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.makeRequest(EnabledContextPropagationTests.java:377) at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.testNoTransactionWithDisabledJTAOverWSATFeature(EnabledContextPropagationTests.java:256) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 6 07:58:00 2016 From: issues at jboss.org (Mark Little (JIRA)) Date: Wed, 6 Jan 2016 07:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2593) Suggest making this read_state INFO not WARN In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145404#comment-13145404 ] Mark Little commented on JBTM-2593: ----------------------------------- Thanks Tom. > Suggest making this read_state INFO not WARN > -------------------------------------------- > > Key: JBTM-2593 > URL: https://issues.jboss.org/browse/JBTM-2593 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.2.11.Final > Reporter: Mark Little > Assignee: Mark Little > Priority: Minor > Fix For: 5.2.12.Final > > > I'm not sure why it was added or why it's a warning. Maybe should be info or debug? > read_state operation, ShadowingStore_6 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 6 16:10:00 2016 From: issues at jboss.org (Johnathon Lee (JIRA)) Date: Wed, 6 Jan 2016 16:10:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-223) Check WL-to-JBossTS interoperability (via JTS). In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johnathon Lee updated JBTM-223: ------------------------------- > Check WL-to-JBossTS interoperability (via JTS). > ----------------------------------------------- > > Key: JBTM-223 > URL: https://issues.jboss.org/browse/JBTM-223 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Mark Little > Assignee: Michael Musgrove > Fix For: 6.later > > > Extensible header structure corba call > key value slot ids > slot for transaction context is not in the well known slot > tx context was not defined so we used the market leader at the time -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 6 17:48:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 Jan 2016 17:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2588) WildFly XTS tests failed with UndeclaredThrowableException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2588: -------------------------------- Priority: Major (was: Minor) > WildFly XTS tests failed with UndeclaredThrowableException > ---------------------------------------------------------- > > Key: JBTM-2588 > URL: https://issues.jboss.org/browse/JBTM-2588 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase > ------------------------------------------------------------------------------- > Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 103.782 sec <<< FAILURE! - in org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase > testWSBAParticipantClientCancel(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 59.832 sec <<< ERROR! > java.lang.reflect.UndeclaredThrowableException: null > at com.sun.proxy.$Proxy25.runTestMethod(Unknown Source) > at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:80) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.io.IOException: Unable to invoke invoke(), status=WAITING > at org.jboss.remotingjmx.protocol.v2.ClientConnection$TheConnection.invoke(ClientConnection.java:1072) > at org.jboss.as.arquillian.container.ManagementClient$MBeanConnectionProxy.invoke(ManagementClient.java:560) > at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:298) > at com.sun.proxy.$Proxy25.runTestMethod(Unknown Source) > at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:80) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 6 17:48:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 Jan 2016 17:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2586) XTS tests failures in WF testsuite In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2586: -------------------------------- Priority: Major (was: Minor) > XTS tests failures in WF testsuite > ---------------------------------- > > Key: JBTM-2586 > URL: https://issues.jboss.org/browse/JBTM-2586 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > {code} > Running org.jboss.as.test.xts.wsat.client.ATTestCase > Tests run: 9, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 11.74 sec <<< FAILURE! - in org.jboss.as.test.xts.wsat.client.ATTestCase > testWSATApplicationExceptionCommit(org.jboss.as.test.xts.wsat.client.ATTestCase) Time elapsed: 0.286 sec <<< ERROR! > org.jboss.arquillian.test.spi.ArquillianProxyException: javax.xml.ws.soap.SOAPFaultException : Error when enlisting participants [Proxied because : Original exception caused: class java.io.NotSerializableException: com.sun.xml.messaging.saaj.soap.ver1_1.SOAPPart1_1Impl] > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:86) > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:52) > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:41) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:112) > at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:140) > at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:71) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:798) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1669) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > at com.sun.proxy.$Proxy176.invoke(Unknown Source) > at org.jboss.as.test.xts.wsat.client.ATTestCase.testWSATApplicationExceptionCommit(ATTestCase.java:227) > testWSATRollbackOnly(org.jboss.as.test.xts.wsat.client.ATTestCase) Time elapsed: 0.12 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.startTransaction(UserTransactionImple.java:308) > at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.begin(UserTransactionImple.java:80) > at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.begin(UserTransactionImple.java:70) > at org.jboss.as.test.xts.wsat.client.ATTestCase.testWSATRollbackOnly(ATTestCase.java:172) > Running org.jboss.as.test.xts.annotation.client.TransactionalTestCase > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.725 sec <<< FAILURE! - in org.jboss.as.test.xts.annotation.client.TransactionalTestCase > testActiveTransaction(org.jboss.as.test.xts.annotation.client.TransactionalTestCase) Time elapsed: 0.018 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.startTransaction(UserTransactionImple.java:308) > at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.begin(UserTransactionImple.java:80) > at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.begin(UserTransactionImple.java:70) > at org.jboss.as.test.xts.annotation.client.TransactionalTestCase.testActiveTransaction(TransactionalTestCase.java:78) > Running org.jboss.as.test.xts.annotation.client.CompensatableTestCase > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.411 sec <<< FAILURE! - in org.jboss.as.test.xts.annotation.client.CompensatableTestCase > testActiveTransaction(org.jboss.as.test.xts.annotation.client.CompensatableTestCase) Time elapsed: 0.054 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.annotation.client.CompensatableTestCase.testActiveTransaction(CompensatableTestCase.java:77) > Running org.jboss.as.test.xts.annotation.compensationScoped.CompensationScopedTestCase > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.876 sec - in org.jboss.as.test.xts.annotation.compensationScoped.CompensationScopedTestCase > Running org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase > Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 1.648 sec <<< FAILURE! - in org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase > testWSBAParticipantApplicationException(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.236 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantApplicationException(BAParticipantCompletionTestCase.java:218) > testWSBAParticipantCannotComplete(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.104 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantCannotComplete(BAParticipantCompletionTestCase.java:177) > testWSBAParticipantClientCancelNotComplete(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.095 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantClientCancelNotComplete(BAParticipantCompletionTestCase.java:161) > testWSBAParticipantDoNotComplete(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.07 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantDoNotComplete(BAParticipantCompletionTestCase.java:141) > testWSBAParticipantCompleteSimple(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.067 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantCompleteSimple(BAParticipantCompletionTestCase.java:125) > testWSBAParticipantCompleteSingle(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.106 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantCompleteSingle(BAParticipantCompletionTestCase.java:114) > testWSBAParticipantClientCancel(org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase) Time elapsed: 0.101 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.participantcompletion.client.BAParticipantCompletionTestCase.testWSBAParticipantClientCancel(BAParticipantCompletionTestCase.java:202) > Running org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase > Tests run: 6, Failures: 2, Errors: 4, Skipped: 0, Time elapsed: 0.585 sec <<< FAILURE! - in org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase > testWSBACoordinatorSimple(org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase) Time elapsed: 0.002 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.testWSBACoordinatorSimple(BACoordinatorCompletionTestCase.java:106) > testWSBACoordinatorSingle(org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase) Time elapsed: 0.002 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.testWSBACoordinatorSingle(BACoordinatorCompletionTestCase.java:97) > testWSBACoordinatorCannotComplete(org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase) Time elapsed: 0.002 sec <<< FAILURE! > java.lang.AssertionError: Another status order expected for the bacoordinator_completition_service1 expected:<[CANCEL]> but was: > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.jboss.as.test.xts.base.BaseFunctionalTest.assertEventLog(BaseFunctionalTest.java:85) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.assertEventLogClient1(BACoordinatorCompletionTestCase.java:194) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.testWSBACoordinatorCannotComplete(BACoordinatorCompletionTestCase.java:134) > testWSBACoordinatorApplicationException(org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase) Time elapsed: 0.359 sec <<< ERROR! > org.jboss.arquillian.test.spi.ArquillianProxyException: javax.xml.ws.soap.SOAPFaultException : Fault occurred while processing. [Proxied because : Original exception caused: class java.io.NotSerializableException: com.sun.xml.messaging.saaj.soap.ver1_1.SOAPPart1_1Impl] > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:86) > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:52) > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:41) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:112) > at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:140) > at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:71) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:798) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1669) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > at com.sun.proxy.$Proxy255.saveData(Unknown Source) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.testWSBACoordinatorApplicationException(BACoordinatorCompletionTestCase.java:163) > testWSBACoordinatorCompletionFailToComplete(org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase) Time elapsed: 0.097 sec <<< FAILURE! > java.lang.AssertionError: Another status order expected for the bacoordinator_completition_service1 expected:<[COMPLETE, CONFIRM_COMPLETED, COMPENSATE]> but was: > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.jboss.as.test.xts.base.BaseFunctionalTest.assertEventLog(BaseFunctionalTest.java:85) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.assertEventLogClient1(BACoordinatorCompletionTestCase.java:194) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.testWSBACoordinatorCompletionFailToComplete(BACoordinatorCompletionTestCase.java:185) > testWSBACoordinatorClientCancel(org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase) Time elapsed: 0.06 sec <<< ERROR! > com.arjuna.wst.SystemException: org.apache.cxf.wsdl11.WSDLRuntimeException: Part parameters defined as element {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CreateCoordinationContext which is not in the schema. > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.startTransaction(UserBusinessActivityImple.java:374) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:117) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.begin(UserBusinessActivityImple.java:107) > at org.jboss.as.test.xts.wsba.coordinatorcompletion.client.BACoordinatorCompletionTestCase.testWSBACoordinatorClientCancel(BACoordinatorCompletionTestCase.java:142) > Results : > Failed tests: > BACoordinatorCompletionTestCase.testWSBACoordinatorCannotComplete:134->assertEventLogClient1:194->BaseFunctionalTest.assertEventLog:85 Another status order expected for the bacoordinator_completition_service1 expected:<[CANCEL]> but was: > BACoordinatorCompletionTestCase.testWSBACoordinatorCompletionFailToComplete:185->assertEventLogClient1:194->BaseFunctionalTest.assertEventLog:85 Another status order expected for the bacoordinator_completition_service1 expected:<[COMPLETE, CONFIRM_COMPLETED, COMPENSATE]> but was: > Tests in error: > ATTestCase.testWSATApplicationExceptionCommit:227 ? ArquillianProxy javax.xml.... > ATTestCase.testWSATRollbackOnly:172 ? System org.apache.cxf.wsdl11.WSDLRuntime... > TransactionalTestCase.testActiveTransaction:78 ? System org.apache.cxf.wsdl11.... > CompensatableTestCase.testActiveTransaction:77 ? System org.apache.cxf.wsdl11.... > BAParticipantCompletionTestCase.testWSBAParticipantApplicationException:218 ? System > BAParticipantCompletionTestCase.testWSBAParticipantCannotComplete:177 ? System > BAParticipantCompletionTestCase.testWSBAParticipantClientCancelNotComplete:161 ? System > BAParticipantCompletionTestCase.testWSBAParticipantDoNotComplete:141 ? System ... > BAParticipantCompletionTestCase.testWSBAParticipantCompleteSimple:125 ? System > BAParticipantCompletionTestCase.testWSBAParticipantCompleteSingle:114 ? System > BAParticipantCompletionTestCase.testWSBAParticipantClientCancel:202 ? System o... > BACoordinatorCompletionTestCase.testWSBACoordinatorSimple:106 ? System org.apa... > BACoordinatorCompletionTestCase.testWSBACoordinatorSingle:97 ? System org.apac... > BACoordinatorCompletionTestCase.testWSBACoordinatorApplicationException:163 ? ArquillianProxy > BACoordinatorCompletionTestCase.testWSBACoordinatorClientCancel:142 ? System o... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 6 17:48:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 Jan 2016 17:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2603) Http request fails with internal server error in EnabledContextPropagationTests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2603: -------------------------------- Priority: Major (was: Minor) > Http request fails with internal server error in EnabledContextPropagationTests > ------------------------------------------------------------------------------- > > Key: JBTM-2603 > URL: https://issues.jboss.org/browse/JBTM-2603 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > {code} > testNoTransactionWithDisabledJTAOverWSATFeature(org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests) Time elapsed: 76.255 sec <<< ERROR! > org.apache.http.client.HttpResponseException: Internal Server Error > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:68) > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:54) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.makeRequest(EnabledContextPropagationTests.java:377) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.testNoTransactionWithDisabledJTAOverWSATFeature(EnabledContextPropagationTests.java:256) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 6 17:49:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 Jan 2016 17:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2603) Http request fails with internal server error in EnabledContextPropagationTests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2603: -------------------------------- Priority: Minor (was: Major) > Http request fails with internal server error in EnabledContextPropagationTests > ------------------------------------------------------------------------------- > > Key: JBTM-2603 > URL: https://issues.jboss.org/browse/JBTM-2603 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > {code} > testNoTransactionWithDisabledJTAOverWSATFeature(org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests) Time elapsed: 76.255 sec <<< ERROR! > org.apache.http.client.HttpResponseException: Internal Server Error > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:68) > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:54) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.makeRequest(EnabledContextPropagationTests.java:377) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.testNoTransactionWithDisabledJTAOverWSATFeature(EnabledContextPropagationTests.java:256) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 7 07:07:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 7 Jan 2016 07:07:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2604) Use servlet protocol in arquillian tests In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2604: ------------------------------------- Summary: Use servlet protocol in arquillian tests Key: JBTM-2604 URL: https://issues.jboss.org/browse/JBTM-2604 Project: JBoss Transaction Manager Issue Type: Task Components: JTA, REST, TxBridge, TXFramework, XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next https://issues.jboss.org/browse/WFLY-5949 was caused by using jmx protocol instead of servlet in arquillian tests. Therefore, to make sure this doesn't happen in other tests, we should set servlet as a default protocol in all arquillian tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 7 07:15:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 7 Jan 2016 07:15:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2604) Use servlet protocol in arquillian tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #968 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Use servlet protocol in arquillian tests > ---------------------------------------- > > Key: JBTM-2604 > URL: https://issues.jboss.org/browse/JBTM-2604 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA, REST, TxBridge, TXFramework, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > https://issues.jboss.org/browse/WFLY-5949 was caused by using jmx protocol instead of servlet in arquillian tests. Therefore, to make sure this doesn't happen in other tests, we should set servlet as a default protocol in all arquillian tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 7 07:16:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 7 Jan 2016 07:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2604) Use servlet protocol in arquillian tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2604: ---------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/968 > Use servlet protocol in arquillian tests > ---------------------------------------- > > Key: JBTM-2604 > URL: https://issues.jboss.org/browse/JBTM-2604 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA, REST, TxBridge, TXFramework, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > https://issues.jboss.org/browse/WFLY-5949 was caused by using jmx protocol instead of servlet in arquillian tests. Therefore, to make sure this doesn't happen in other tests, we should set servlet as a default protocol in all arquillian tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 7 11:46:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 7 Jan 2016 11:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2604) Use servlet protocol in arquillian tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2604: ---------------------------------- Component/s: (was: JTA) (was: REST) (was: TxBridge) (was: TXFramework) > Use servlet protocol in arquillian tests > ---------------------------------------- > > Key: JBTM-2604 > URL: https://issues.jboss.org/browse/JBTM-2604 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > https://issues.jboss.org/browse/WFLY-5949 was caused by using jmx protocol instead of servlet in arquillian tests. Therefore, to make sure this doesn't happen in other tests, we should set servlet as a default protocol in all arquillian tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 7 11:46:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 7 Jan 2016 11:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2604) Use servlet protocol in xts arquillian tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2604: ---------------------------------- Summary: Use servlet protocol in xts arquillian tests (was: Use servlet protocol in arquillian tests) > Use servlet protocol in xts arquillian tests > -------------------------------------------- > > Key: JBTM-2604 > URL: https://issues.jboss.org/browse/JBTM-2604 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > https://issues.jboss.org/browse/WFLY-5949 was caused by using jmx protocol instead of servlet in arquillian tests. Therefore, to make sure this doesn't happen in other tests, we should set servlet as a default protocol in all arquillian tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 8 04:22:02 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 8 Jan 2016 04:22:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2603) Socket read timed out in EnabledContextPropagationTests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2603: ---------------------------------- Summary: Socket read timed out in EnabledContextPropagationTests (was: Http request fails with internal server error in EnabledContextPropagationTests) > Socket read timed out in EnabledContextPropagationTests > ------------------------------------------------------- > > Key: JBTM-2603 > URL: https://issues.jboss.org/browse/JBTM-2603 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > {code} > testNoTransactionWithDisabledJTAOverWSATFeature(org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests) Time elapsed: 76.255 sec <<< ERROR! > org.apache.http.client.HttpResponseException: Internal Server Error > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:68) > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:54) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.makeRequest(EnabledContextPropagationTests.java:377) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.testNoTransactionWithDisabledJTAOverWSATFeature(EnabledContextPropagationTests.java:256) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 8 04:24:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 8 Jan 2016 04:24:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2603) Socket read timed out in EnabledContextPropagationTests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2603: ---------------------------------- Description: Test output: {code} testNoTransactionWithDisabledJTAOverWSATFeature(org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests) Time elapsed: 76.255 sec <<< ERROR! org.apache.http.client.HttpResponseException: Internal Server Error at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:68) at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:54) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035) at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.makeRequest(EnabledContextPropagationTests.java:377) at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.testNoTransactionWithDisabledJTAOverWSATFeature(EnabledContextPropagationTests.java:256) {code} Server log: {code} [0mJan 06, 2016 12:53:47 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start INFO: Manual starting of a server instance Jan 06, 2016 12:53:47 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal WARNING: Bundles path is deprecated and no longer used. Jan 06, 2016 12:53:47 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dorg.jboss.byteman.debug=true, -Dorg.jboss.byteman.verbose=true, -Dorg.jboss.byteman.contrib.dtest.rmiregistry.port=1199, -javaagent:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/txbridge/target/byteman/byteman.jar=port:9091,listener:true,sys:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/txbridge/target/byteman/byteman-dtest.jar, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-xts.xml] Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 TransformListener() : accepting requests on localhost:9091 00:53:48,689 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.0.Final 00:53:49,098 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final 00:53:49,246 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Core 2.0.5.Final "Kenny" starting 00:53:51,591 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) 00:53:51,629 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.4.Final 00:53:51,659 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.4.Final 00:53:51,751 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 40) WFLYCLINF0001: Activating Infinispan subsystem. 00:53:51,743 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 00:53:51,771 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 39) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors 00:53:51,815 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 41) WFLYIIOP0001: Activating IIOP Subsystem 00:53:51,837 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 47) WFLYJSF0007: Activated the following JSF Implementations: [main] 00:53:51,847 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.1.Final) 00:53:51,913 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2 00:53:51,958 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.17.Final-wildfly-1 00:53:51,994 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. 00:53:52,039 INFO [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem 00:53:52,039 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 61) WFLYWS0002: Activating WebServices Extension 00:53:52,076 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem 00:53:52,066 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.4.Final 00:53:52,227 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.11.Final starting 00:53:52,237 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0003: Undertow 1.3.11.Final starting 00:53:52,593 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 32 (per class), which is derived from thread worker pool sizing. 00:53:52,594 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 8 (per class), which is derived from the number of CPUs on this host. 00:53:52,713 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service 00:53:52,723 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] 00:53:52,887 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] 00:53:52,934 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. 00:53:52,938 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting 00:53:53,155 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 00:53:53,521 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. 00:53:53,575 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-4) WFLYIIOP0009: CORBA ORB Service started 00:53:53,916 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final 00:53:54,002 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "restat-web-5.2.13.Final-SNAPSHOT.war" (runtime-name: "restat-web-5.2.13.Final-SNAPSHOT.war") 00:53:54,004 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/deployments 00:53:54,004 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "xtstest.war" (runtime-name: "xtstest.war") 00:53:54,192 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/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/paging) 00:53:54,248 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.2.Final (Apache CXF 3.1.4) 00:53:54,351 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221013: Using NIO Journal 00:53:54,505 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-c11 00:53:54,506 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-client 00:53:54,511 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-coordinator 00:53:54,659 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) 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 00:53:54,661 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) 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 00:53:54,667 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 00:53:54,667 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 00:53:54,668 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 00:53:54,668 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 00:53:54,669 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 00:53:54,670 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 00:53:54,723 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 00:53:54,724 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 00:53:54,724 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 00:53:54,966 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE 00:53:54,988 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP 00:53:55,029 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ 00:53:55,034 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP 00:53:55,155 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-participant 00:53:55,156 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 00:53:55,168 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 00:53:55,169 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 00:53:56,128 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}CompletionCoordinatorService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl 00:53:56,138 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from class com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl 00:53:56,137 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) 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 00:53:56,131 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationParticipantPortType 00:53:57,259 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live 00:53:57,276 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010 [nodeID=7842cabe-b404-11e5-9b8e-a55e51d89294] 00:53:57,412 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/ws-t11-client/TerminationParticipantService 00:53:57,419 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService 00:53:57,412 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService 00:53:57,532 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-c11/ActivationService 00:53:57,685 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorService.wsdl 00:53:57,704 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationCoordinatorPortType 00:53:57,705 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/ActivationService.wsdl 00:53:57,713 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from class com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl 00:53:57,701 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/TerminationParticipantService.wsdl 00:53:57,715 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService from class com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl 00:53:57,721 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithCoordinatorCompletionParticipantService.wsdl 00:53:57,731 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}ParticipantService from class com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl 00:53:57,749 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService 00:53:57,773 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/ws-t11-client/CompletionInitiatorService 00:53:57,779 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-c11/RegistrationService 00:53:57,785 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorService.wsdl 00:53:57,795 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService from class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl 00:53:57,804 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/ParticipantService 00:53:57,808 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService 00:53:57,822 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/CompletionInitiatorService.wsdl 00:53:57,831 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorRPCPortTypeImplService.wsdl 00:53:57,827 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/RegistrationService.wsdl 00:53:57,836 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}BusinessAgreementWithCoordinatorCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl 00:53:57,842 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/ParticipantService.wsdl 00:53:57,851 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl 00:53:57,903 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService 00:53:57,953 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithParticipantCompletionParticipantService.wsdl 00:53:57,960 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService 00:53:57,988 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".ActivationService 00:53:58,005 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".RegistrationService 00:53:58,014 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService 00:53:58,015 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService 00:53:58,025 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithCoordinatorCompletionCoordinatorService.wsdl 00:53:58,027 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}BusinessAgreementWithParticipantCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl 00:53:58,044 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] 00:53:58,045 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService 00:53:58,052 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService 00:53:58,053 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService 00:53:58,061 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService 00:53:58,063 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor 00:53:58,070 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor 00:53:58,111 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor 00:53:58,119 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor 00:53:58,123 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithParticipantCompletionCoordinatorService.wsdl 00:53:58,124 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}CoordinatorService from class com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl 00:53:58,145 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CoordinatorService 00:53:58,182 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 64) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 00:53:58,193 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CoordinatorService.wsdl 00:53:58,203 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}CompletionCoordinatorRPCService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl 00:53:58,210 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory 00:53:58,212 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221003: trying to deploy queue jms.queue.DLQ 00:53:58,217 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-c11 00:53:58,228 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 65) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue 00:53:58,235 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService 00:53:58,261 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorRPCService.wsdl 00:53:58,287 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-client 00:53:58,297 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-participant 00:53:58,352 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0021: Registered web context: /ws-t11-client 00:53:58,359 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: /ws-c11 00:53:58,360 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService 00:53:58,359 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0021: Registered web context: /ws-t11-participant 00:53:58,361 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService 00:53:58,361 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService 00:53:58,362 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService 00:53:58,362 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService 00:53:58,364 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService 00:53:58,366 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService 00:53:58,390 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-coordinator 00:53:58,402 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0021: Registered web context: /ws-t11-coordinator 00:53:58,413 WARN [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0005: Secure listener for protocol: 'HTTP/1.1' not found! Using non secure port! 00:53:58,517 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.restat-web-5.2.13.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. 00:53:58,523 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.restat-web-5.2.13.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. 00:53:58,591 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA 00:53:58,776 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033006: InboundBridgeRecoveryManager starting 00:53:58,777 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033013: OutboundBridgeRecoveryManager starting 00:53:58,821 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) Resource adaptor started 00:53:58,821 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatoractivemq-ra 00:53:58,823 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] 00:53:58,823 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory 00:53:58,950 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. 00:53:58,995 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment xtstest.war 00:53:59,138 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.2.2.Final 00:53:59,403 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0021: Registered web context: /rest-tx 00:53:59,533 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: xtstest.war 00:53:59,587 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.3.2 (Final) 00:53:59,600 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 00:53:59,601 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 00:53:59,601 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 00:53:59,602 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 00:53:59,616 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl 00:53:59,679 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest1 00:53:59,689 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl 00:53:59,690 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl 00:53:59,693 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest2 00:53:59,719 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl 00:53:59,722 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl 00:53:59,726 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest3 00:53:59,737 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl 00:53:59,740 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl 00:53:59,743 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtssubordinateservicetest1 00:53:59,750 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl 00:53:59,780 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two 00:53:59,781 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One 00:53:59,784 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One 00:53:59,785 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three 00:53:59,792 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0009: Starting weld service for deployment xtstest.war 00:54:00,907 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 65) Starting XTSServiceTestRunner 00:54:00,908 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 65) Started XTSServiceTestRunner 00:54:00,925 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 65) Initializing Mojarra 2.2.12-jbossorg-2 20150729-1131 for context '/xtstest' 00:54:01,758 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0021: Registered web context: /xtstest 00:54:01,792 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") 00:54:01,794 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "restat-web-5.2.13.Final-SNAPSHOT.war" (runtime-name : "restat-web-5.2.13.Final-SNAPSHOT.war") 00:54:02,073 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management 00:54:02,074 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 00:54:02,074 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.0.5.Final "Kenny" started in 13928ms - Started 567 of 876 services (423 services are lazy, passive or on-demand) Jan 06, 2016 12:54:02 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start INFO: Automatic deploying of the managed deployment with name txbridge-outbound-tests-service for the container with name jboss 00:54:02,228 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/9b/70e2a1644d4faf24e750f2cf3b295db924703a/content 00:54:02,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "txbridge-outbound-tests-service.war" (runtime-name: "txbridge-outbound-tests-service.war") 00:54:02,258 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-service.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. 00:54:02,329 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=OutboundTestServiceATServlet address=http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl implementor=org.jboss.jbossts.txbridge.tests.outbound.service.TestATServiceImpl serviceName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService portName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplPort annotationWsdlLocation=null wsdlLocationOverride=null mtomEnabled=false 00:54:02,329 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=OutboundTestServiceNonATServlet address=http://localhost:8080/txbridge-outbound-tests-service/TestNonATServiceImpl implementor=org.jboss.jbossts.txbridge.tests.outbound.service.TestNonATServiceImpl serviceName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplService portName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplPort annotationWsdlLocation=null wsdlLocationOverride=null mtomEnabled=false 00:54:02,350 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from class org.jboss.jbossts.txbridge.tests.outbound.service.TestATServiceImpl 00:54:02,377 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl 00:54:02,392 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/txbridge-outbound-tests-service.war/TestATServiceImplService.wsdl 00:54:02,396 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplService from class org.jboss.jbossts.txbridge.tests.outbound.service.TestNonATServiceImpl 00:54:02,399 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/txbridge-outbound-tests-service/TestNonATServiceImpl 00:54:02,404 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/txbridge-outbound-tests-service.war/TestNonATServiceImplService.wsdl 00:54:02,422 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceATServlet 00:54:02,422 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceNonATServlet 00:54:02,434 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /txbridge-outbound-tests-service 00:54:02,492 INFO [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "txbridge-outbound-tests-service.war" (runtime-name : "txbridge-outbound-tests-service.war") Jan 06, 2016 12:54:02 AM org.jboss.remotingjmx.Util warnDeprecated WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. Jan 06, 2016 12:54:02 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start INFO: Automatic deploying of the managed deployment with name txbridge-outbound-tests-client for the container with name jboss 00:54:02,720 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/b3/6bdfaa5feca5ff426c038cb7f2f2fed119847f/content 00:54:02,723 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "txbridge-outbound-tests-client.war" (runtime-name: "txbridge-outbound-tests-client.war") 00:54:02,746 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-client.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. 00:54:02,746 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-client.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. 00:54:02,810 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /txbridge-outbound-tests-client 00:54:02,823 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "txbridge-outbound-tests-client.war" (runtime-name : "txbridge-outbound-tests-client.war") 00:54:03,077 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from WSDL: http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl?wsdl 00:54:03,099 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from WSDL: http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl?wsdl 00:55:03,344 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default task-1) Interceptor for {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService#{http://client.outbound.tests.txbridge.jbossts.jboss.org/}doNothing has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not send Message. at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) at com.sun.proxy.$Proxy137.doNothing(Unknown Source) at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:140) at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.doPost(TestATClient.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl: Read timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) ... 39 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:170) at java.net.SocketInputStream.read(SocketInputStream.java:141) at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) at java.io.BufferedInputStream.read(BufferedInputStream.java:345) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) ... 42 more 00:55:03,349 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /txbridge-outbound-tests-client//testATClient: java.lang.RuntimeException: javax.xml.ws.WebServiceException: Could not send Message. at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:148) at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.doPost(TestATClient.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: javax.xml.ws.WebServiceException: Could not send Message. at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:150) at com.sun.proxy.$Proxy137.doNothing(Unknown Source) at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:140) ... 30 more Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl: Read timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) ... 32 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:170) at java.net.SocketInputStream.read(SocketInputStream.java:141) at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) at java.io.BufferedInputStream.read(BufferedInputStream.java:345) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) ... 42 more Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop INFO: Automatic undeploying of the managed deployment with name txbridge-outbound-tests-service from the container with name jboss 00:55:03,375 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 70) WFLYUT0022: Unregistered web context: /txbridge-outbound-tests-service 00:55:03,387 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceNonATServlet 00:55:03,389 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceATServlet 00:55:03,452 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment txbridge-outbound-tests-service.war (runtime-name: txbridge-outbound-tests-service.war) in 85ms 00:55:03,469 INFO [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/9b/70e2a1644d4faf24e750f2cf3b295db924703a/content 00:55:03,469 INFO [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0009: Undeployed "txbridge-outbound-tests-service.war" (runtime-name: "txbridge-outbound-tests-service.war") Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop INFO: Automatic undeploying of the managed deployment with name txbridge-outbound-tests-client from the container with name jboss 00:55:03,481 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Unregistered web context: /txbridge-outbound-tests-client 00:55:03,491 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment txbridge-outbound-tests-client.war (runtime-name: txbridge-outbound-tests-client.war) in 12ms 00:55:03,502 INFO [org.jboss.as.repository] (management-handler-thread - 6) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/b3/6bdfaa5feca5ff426c038cb7f2f2fed119847f/content 00:55:03,502 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0009: Undeployed "txbridge-outbound-tests-client.war" (runtime-name: "txbridge-outbound-tests-client.war") Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop INFO: Manual stopping of a server instance 00:55:03,508 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0211: Suspending server with 0ms timeout. 00:55:03,512 INFO [org.jboss.as.server] (Thread-3) WFLYSRV0220: Server shutdown has been requested. 00:55:03,544 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-3) ARJUNA033014: OutboundBridgeRecoveryManager stopping 00:55:03,545 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-1) ARJUNA033007: InboundBridgeRecoveryManager stopping 00:55:03,557 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Unregistered web context: /rest-tx 00:55:03,567 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory 00:55:03,577 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: /xtstest 00:55:03,582 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] 00:55:03,587 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 71) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory 00:55:03,604 ERROR [org.jboss.remoting.resource] (Remoting "brandon:MANAGEMENT" task-8) Close action for Channel ID 25c56b1d (inbound) of Remoting connection 01cf11a2 to /127.0.0.1:47100 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588) at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327) at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138) at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261) at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534) at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372) at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437) at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114) at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57) at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 00:55:03,608 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-coordinator 00:55:03,612 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-client 00:55:03,612 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0022: Unregistered web context: /ws-t11-client 00:55:03,613 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-participant 00:55:03,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0022: Unregistered web context: /ws-t11-participant 00:55:03,613 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-c11 00:55:03,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0022: Unregistered web context: /ws-c11 00:55:03,617 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /ws-t11-coordinator 00:55:03,617 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService 00:55:03,618 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService 00:55:03,620 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".RegistrationService 00:55:03,621 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-client 00:55:03,620 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".ActivationService 00:55:03,624 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-c11 00:55:03,634 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService 00:55:03,634 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService 00:55:03,635 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService 00:55:03,637 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService 00:55:03,637 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService 00:55:03,641 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService 00:55:03,643 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService 00:55:03,643 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-participant 00:55:03,644 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-coordinator 00:55:03,655 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 74) Stopping XTSServiceTestRunner 00:55:03,656 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 74) Stopped XTSServiceTestRunner 00:55:03,657 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 75) AMQ151003: resource adaptor stopped 00:55:03,678 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment restat-web-5.2.13.Final-SNAPSHOT.war (runtime-name: restat-web-5.2.13.Final-SNAPSHOT.war) in 159ms 00:55:03,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0019: Host default-host stopping 00:55:03,711 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One 00:55:03,712 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One 00:55:03,711 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two 00:55:03,713 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three 00:55:03,714 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0010: Stopping weld service for deployment xtstest.war 00:55:03,772 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] 00:55:03,787 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = h2 00:55:03,805 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010 [7842cabe-b404-11e5-9b8e-a55e51d89294] stopped 00:55:03,806 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending 00:55:03,807 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 00:55:03,808 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.3.11.Final stopping 00:55:03,827 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment xtstest.war (runtime-name: xtstest.war) in 308ms 00:55:03,836 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.0.5.Final "Kenny" stopped in 284ms {code} was: {code} testNoTransactionWithDisabledJTAOverWSATFeature(org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests) Time elapsed: 76.255 sec <<< ERROR! org.apache.http.client.HttpResponseException: Internal Server Error at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:68) at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:54) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035) at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.makeRequest(EnabledContextPropagationTests.java:377) at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.testNoTransactionWithDisabledJTAOverWSATFeature(EnabledContextPropagationTests.java:256) {code} > Socket read timed out in EnabledContextPropagationTests > ------------------------------------------------------- > > Key: JBTM-2603 > URL: https://issues.jboss.org/browse/JBTM-2603 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Test output: > {code} > testNoTransactionWithDisabledJTAOverWSATFeature(org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests) Time elapsed: 76.255 sec <<< ERROR! > org.apache.http.client.HttpResponseException: Internal Server Error > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:68) > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:54) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.makeRequest(EnabledContextPropagationTests.java:377) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.testNoTransactionWithDisabledJTAOverWSATFeature(EnabledContextPropagationTests.java:256) > {code} > Server log: > {code} > [0mJan 06, 2016 12:53:47 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance > Jan 06, 2016 12:53:47 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > Jan 06, 2016 12:53:47 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dorg.jboss.byteman.debug=true, -Dorg.jboss.byteman.verbose=true, -Dorg.jboss.byteman.contrib.dtest.rmiregistry.port=1199, -javaagent:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/txbridge/target/byteman/byteman.jar=port:9091,listener:true,sys:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/txbridge/target/byteman/byteman-dtest.jar, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-xts.xml] > Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 00:53:48,689 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.0.Final > 00:53:49,098 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 00:53:49,246 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Core 2.0.5.Final "Kenny" starting > 00:53:51,591 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 00:53:51,629 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.4.Final > 00:53:51,659 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.4.Final > 00:53:51,751 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 40) WFLYCLINF0001: Activating Infinispan subsystem. > 00:53:51,743 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 00:53:51,771 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 39) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 00:53:51,815 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 41) WFLYIIOP0001: Activating IIOP Subsystem > 00:53:51,837 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 47) WFLYJSF0007: Activated the following JSF Implementations: [main] > 00:53:51,847 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.1.Final) > 00:53:51,913 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2 > 00:53:51,958 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.17.Final-wildfly-1 > 00:53:51,994 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. > 00:53:52,039 INFO [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem > 00:53:52,039 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 61) WFLYWS0002: Activating WebServices Extension > 00:53:52,076 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem > 00:53:52,066 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.4.Final > 00:53:52,227 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.11.Final starting > 00:53:52,237 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0003: Undertow 1.3.11.Final starting > 00:53:52,593 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 32 (per class), which is derived from thread worker pool sizing. > 00:53:52,594 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 8 (per class), which is derived from the number of CPUs on this host. > 00:53:52,713 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service > 00:53:52,723 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 00:53:52,887 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 00:53:52,934 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. > 00:53:52,938 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 00:53:53,155 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 00:53:53,521 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 00:53:53,575 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-4) WFLYIIOP0009: CORBA ORB Service started > 00:53:53,916 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final > 00:53:54,002 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "restat-web-5.2.13.Final-SNAPSHOT.war" (runtime-name: "restat-web-5.2.13.Final-SNAPSHOT.war") > 00:53:54,004 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/deployments > 00:53:54,004 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "xtstest.war" (runtime-name: "xtstest.war") > 00:53:54,192 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/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 00:53:54,248 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.2.Final (Apache CXF 3.1.4) > 00:53:54,351 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221013: Using NIO Journal > 00:53:54,505 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-c11 > 00:53:54,506 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-client > 00:53:54,511 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-coordinator > 00:53:54,659 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) 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 > 00:53:54,661 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) 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 > 00:53:54,667 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:54,667 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:54,668 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,668 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,669 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,670 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,723 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,724 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,724 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,966 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 00:53:54,988 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 00:53:55,029 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 00:53:55,034 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 00:53:55,155 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-participant > 00:53:55,156 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:55,168 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:55,169 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:56,128 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}CompletionCoordinatorService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > 00:53:56,138 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from class com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > 00:53:56,137 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) 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 > 00:53:56,131 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationParticipantPortType > 00:53:57,259 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live > 00:53:57,276 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010 [nodeID=7842cabe-b404-11e5-9b8e-a55e51d89294] > 00:53:57,412 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/ws-t11-client/TerminationParticipantService > 00:53:57,419 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > 00:53:57,412 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > 00:53:57,532 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-c11/ActivationService > 00:53:57,685 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorService.wsdl > 00:53:57,704 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationCoordinatorPortType > 00:53:57,705 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/ActivationService.wsdl > 00:53:57,713 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from class com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > 00:53:57,701 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/TerminationParticipantService.wsdl > 00:53:57,715 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService from class com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > 00:53:57,721 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithCoordinatorCompletionParticipantService.wsdl > 00:53:57,731 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}ParticipantService from class com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > 00:53:57,749 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > 00:53:57,773 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/ws-t11-client/CompletionInitiatorService > 00:53:57,779 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-c11/RegistrationService > 00:53:57,785 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorService.wsdl > 00:53:57,795 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService from class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > 00:53:57,804 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/ParticipantService > 00:53:57,808 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > 00:53:57,822 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/CompletionInitiatorService.wsdl > 00:53:57,831 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorRPCPortTypeImplService.wsdl > 00:53:57,827 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/RegistrationService.wsdl > 00:53:57,836 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}BusinessAgreementWithCoordinatorCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > 00:53:57,842 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/ParticipantService.wsdl > 00:53:57,851 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > 00:53:57,903 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > 00:53:57,953 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithParticipantCompletionParticipantService.wsdl > 00:53:57,960 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:53:57,988 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 00:53:58,005 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 00:53:58,014 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 00:53:58,015 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 00:53:58,025 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithCoordinatorCompletionCoordinatorService.wsdl > 00:53:58,027 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}BusinessAgreementWithParticipantCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > 00:53:58,044 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 00:53:58,045 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 00:53:58,052 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 00:53:58,053 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 00:53:58,061 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > 00:53:58,063 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 00:53:58,070 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 00:53:58,111 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 00:53:58,119 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 00:53:58,123 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithParticipantCompletionCoordinatorService.wsdl > 00:53:58,124 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}CoordinatorService from class com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > 00:53:58,145 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CoordinatorService > 00:53:58,182 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 64) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 00:53:58,193 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CoordinatorService.wsdl > 00:53:58,203 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}CompletionCoordinatorRPCService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > 00:53:58,210 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 00:53:58,212 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221003: trying to deploy queue jms.queue.DLQ > 00:53:58,217 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-c11 > 00:53:58,228 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 65) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 00:53:58,235 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > 00:53:58,261 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorRPCService.wsdl > 00:53:58,287 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-client > 00:53:58,297 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-participant > 00:53:58,352 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0021: Registered web context: /ws-t11-client > 00:53:58,359 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: /ws-c11 > 00:53:58,360 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:53:58,359 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0021: Registered web context: /ws-t11-participant > 00:53:58,361 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 00:53:58,361 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 00:53:58,362 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 00:53:58,362 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 00:53:58,364 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 00:53:58,366 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 00:53:58,390 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-coordinator > 00:53:58,402 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0021: Registered web context: /ws-t11-coordinator > 00:53:58,413 WARN [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0005: Secure listener for protocol: 'HTTP/1.1' not found! Using non secure port! > 00:53:58,517 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.restat-web-5.2.13.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:53:58,523 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.restat-web-5.2.13.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:53:58,591 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 00:53:58,776 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033006: InboundBridgeRecoveryManager starting > 00:53:58,777 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033013: OutboundBridgeRecoveryManager starting > 00:53:58,821 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) Resource adaptor started > 00:53:58,821 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatoractivemq-ra > 00:53:58,823 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 00:53:58,823 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 00:53:58,950 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. > 00:53:58,995 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment xtstest.war > 00:53:59,138 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.2.2.Final > 00:53:59,403 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0021: Registered web context: /rest-tx > 00:53:59,533 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: xtstest.war > 00:53:59,587 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.3.2 (Final) > 00:53:59,600 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,601 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,601 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,602 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,616 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,679 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest1 > 00:53:59,689 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,690 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,693 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest2 > 00:53:59,719 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,722 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,726 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest3 > 00:53:59,737 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,740 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,743 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtssubordinateservicetest1 > 00:53:59,750 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,780 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 00:53:59,781 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 00:53:59,784 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 00:53:59,785 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 00:53:59,792 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0009: Starting weld service for deployment xtstest.war > 00:54:00,907 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 65) Starting XTSServiceTestRunner > 00:54:00,908 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 65) Started XTSServiceTestRunner > 00:54:00,925 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 65) Initializing Mojarra 2.2.12-jbossorg-2 20150729-1131 for context '/xtstest' > 00:54:01,758 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0021: Registered web context: /xtstest > 00:54:01,792 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") > 00:54:01,794 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "restat-web-5.2.13.Final-SNAPSHOT.war" (runtime-name : "restat-web-5.2.13.Final-SNAPSHOT.war") > 00:54:02,073 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 00:54:02,074 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 00:54:02,074 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.0.5.Final "Kenny" started in 13928ms - Started 567 of 876 services (423 services are lazy, passive or on-demand) > Jan 06, 2016 12:54:02 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Automatic deploying of the managed deployment with name txbridge-outbound-tests-service for the container with name jboss > 00:54:02,228 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/9b/70e2a1644d4faf24e750f2cf3b295db924703a/content > 00:54:02,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "txbridge-outbound-tests-service.war" (runtime-name: "txbridge-outbound-tests-service.war") > 00:54:02,258 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-service.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:54:02,329 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=OutboundTestServiceATServlet > address=http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl > implementor=org.jboss.jbossts.txbridge.tests.outbound.service.TestATServiceImpl > serviceName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService > portName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplPort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 00:54:02,329 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=OutboundTestServiceNonATServlet > address=http://localhost:8080/txbridge-outbound-tests-service/TestNonATServiceImpl > implementor=org.jboss.jbossts.txbridge.tests.outbound.service.TestNonATServiceImpl > serviceName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplService > portName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplPort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 00:54:02,350 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from class org.jboss.jbossts.txbridge.tests.outbound.service.TestATServiceImpl > 00:54:02,377 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl > 00:54:02,392 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/txbridge-outbound-tests-service.war/TestATServiceImplService.wsdl > 00:54:02,396 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplService from class org.jboss.jbossts.txbridge.tests.outbound.service.TestNonATServiceImpl > 00:54:02,399 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/txbridge-outbound-tests-service/TestNonATServiceImpl > 00:54:02,404 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/txbridge-outbound-tests-service.war/TestNonATServiceImplService.wsdl > 00:54:02,422 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceATServlet > 00:54:02,422 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceNonATServlet > 00:54:02,434 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /txbridge-outbound-tests-service > 00:54:02,492 INFO [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "txbridge-outbound-tests-service.war" (runtime-name : "txbridge-outbound-tests-service.war") > Jan 06, 2016 12:54:02 AM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > Jan 06, 2016 12:54:02 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Automatic deploying of the managed deployment with name txbridge-outbound-tests-client for the container with name jboss > 00:54:02,720 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/b3/6bdfaa5feca5ff426c038cb7f2f2fed119847f/content > 00:54:02,723 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "txbridge-outbound-tests-client.war" (runtime-name: "txbridge-outbound-tests-client.war") > 00:54:02,746 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-client.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:54:02,746 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-client.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 00:54:02,810 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /txbridge-outbound-tests-client > 00:54:02,823 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "txbridge-outbound-tests-client.war" (runtime-name : "txbridge-outbound-tests-client.war") > 00:54:03,077 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from WSDL: http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl?wsdl > 00:54:03,099 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from WSDL: http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl?wsdl > 00:55:03,344 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default task-1) Interceptor for {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService#{http://client.outbound.tests.txbridge.jbossts.jboss.org/}doNothing has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not send Message. > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > at com.sun.proxy.$Proxy137.doNothing(Unknown Source) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:140) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.doPost(TestATClient.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl: Read timed out > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > ... 39 more > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > ... 42 more > 00:55:03,349 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /txbridge-outbound-tests-client//testATClient: java.lang.RuntimeException: javax.xml.ws.WebServiceException: Could not send Message. > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:148) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.doPost(TestATClient.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: javax.xml.ws.WebServiceException: Could not send Message. > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:150) > at com.sun.proxy.$Proxy137.doNothing(Unknown Source) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:140) > ... 30 more > Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl: Read timed out > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > ... 32 more > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > ... 42 more > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Automatic undeploying of the managed deployment with name txbridge-outbound-tests-service from the container with name jboss > 00:55:03,375 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 70) WFLYUT0022: Unregistered web context: /txbridge-outbound-tests-service > 00:55:03,387 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceNonATServlet > 00:55:03,389 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceATServlet > 00:55:03,452 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment txbridge-outbound-tests-service.war (runtime-name: txbridge-outbound-tests-service.war) in 85ms > 00:55:03,469 INFO [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/9b/70e2a1644d4faf24e750f2cf3b295db924703a/content > 00:55:03,469 INFO [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0009: Undeployed "txbridge-outbound-tests-service.war" (runtime-name: "txbridge-outbound-tests-service.war") > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Automatic undeploying of the managed deployment with name txbridge-outbound-tests-client from the container with name jboss > 00:55:03,481 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Unregistered web context: /txbridge-outbound-tests-client > 00:55:03,491 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment txbridge-outbound-tests-client.war (runtime-name: txbridge-outbound-tests-client.war) in 12ms > 00:55:03,502 INFO [org.jboss.as.repository] (management-handler-thread - 6) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/b3/6bdfaa5feca5ff426c038cb7f2f2fed119847f/content > 00:55:03,502 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0009: Undeployed "txbridge-outbound-tests-client.war" (runtime-name: "txbridge-outbound-tests-client.war") > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 00:55:03,508 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0211: Suspending server with 0ms timeout. > 00:55:03,512 INFO [org.jboss.as.server] (Thread-3) WFLYSRV0220: Server shutdown has been requested. > 00:55:03,544 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-3) ARJUNA033014: OutboundBridgeRecoveryManager stopping > 00:55:03,545 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-1) ARJUNA033007: InboundBridgeRecoveryManager stopping > 00:55:03,557 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Unregistered web context: /rest-tx > 00:55:03,567 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 00:55:03,577 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: /xtstest > 00:55:03,582 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > 00:55:03,587 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 71) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory > 00:55:03,604 ERROR [org.jboss.remoting.resource] (Remoting "brandon:MANAGEMENT" task-8) Close action for Channel ID 25c56b1d (inbound) of Remoting connection 01cf11a2 to /127.0.0.1:47100 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating > at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588) > at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327) > at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138) > at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261) > at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534) > at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372) > at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437) > at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114) > at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > 00:55:03,608 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-coordinator > 00:55:03,612 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-client > 00:55:03,612 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0022: Unregistered web context: /ws-t11-client > 00:55:03,613 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-participant > 00:55:03,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0022: Unregistered web context: /ws-t11-participant > 00:55:03,613 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-c11 > 00:55:03,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0022: Unregistered web context: /ws-c11 > 00:55:03,617 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /ws-t11-coordinator > 00:55:03,617 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 00:55:03,618 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 00:55:03,620 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 00:55:03,621 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-client > 00:55:03,620 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 00:55:03,624 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-c11 > 00:55:03,634 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 00:55:03,634 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 00:55:03,635 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 00:55:03,637 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 00:55:03,637 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 00:55:03,641 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 00:55:03,643 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:55:03,643 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-participant > 00:55:03,644 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-coordinator > 00:55:03,655 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 74) Stopping XTSServiceTestRunner > 00:55:03,656 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 74) Stopped XTSServiceTestRunner > 00:55:03,657 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 75) AMQ151003: resource adaptor stopped > 00:55:03,678 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment restat-web-5.2.13.Final-SNAPSHOT.war (runtime-name: restat-web-5.2.13.Final-SNAPSHOT.war) in 159ms > 00:55:03,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0019: Host default-host stopping > 00:55:03,711 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 00:55:03,712 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 00:55:03,711 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 00:55:03,713 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 00:55:03,714 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0010: Stopping weld service for deployment xtstest.war > 00:55:03,772 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 00:55:03,787 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 00:55:03,805 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010 [7842cabe-b404-11e5-9b8e-a55e51d89294] stopped > 00:55:03,806 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending > 00:55:03,807 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 00:55:03,808 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.3.11.Final stopping > 00:55:03,827 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment xtstest.war (runtime-name: xtstest.war) in 308ms > 00:55:03,836 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.0.5.Final "Kenny" stopped in 284ms > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 8 05:35:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 8 Jan 2016 05:35:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2605) Narayana Spring integration In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2605: ------------------------------------- Summary: Narayana Spring integration Key: JBTM-2605 URL: https://issues.jboss.org/browse/JBTM-2605 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator, Documentation, JTA Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next This is a wrapper for all subtasks related with Spring integration. As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 8 05:36:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 8 Jan 2016 05:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-855: --------------------------------- Parent: JBTM-2605 Issue Type: Sub-task (was: Task) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 8 05:41:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 8 Jan 2016 05:41:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2606) Create Spring Boot starter for Narayana In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2606: ------------------------------------- Summary: Create Spring Boot starter for Narayana Key: JBTM-2606 URL: https://issues.jboss.org/browse/JBTM-2606 Project: JBoss Transaction Manager Issue Type: Sub-task Components: JTA Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next Spring provides a bunch of Spring Boot starter artefacts in order to make integration of certain projects easier. We should investigate having one for Narayana. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 8 06:25:00 2016 From: issues at jboss.org (Jive JIRA Integration (JIRA)) Date: Fri, 8 Jan 2016 06:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2458) Think of the possibility to improve Compensations API with lambdas In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jive JIRA Integration updated JBTM-2458: ---------------------------------------- Forum Reference: https://developer.jboss.org/message/948585#948585 > Think of the possibility to improve Compensations API with lambdas > ------------------------------------------------------------------ > > Key: JBTM-2458 > URL: https://issues.jboss.org/browse/JBTM-2458 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Emmanuel suggested to reduce verbosity in Compensations API by making it possible to use lambdas for handler implementation. > We should try to think of the best API changes to introduce that. > We could rewrite MongoDB quickstart to make it easier to visualise the difference. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 8 10:46:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 Jan 2016 10:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-855: ------------------------------- Priority: Major (was: Minor) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 8 13:44:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 8 Jan 2016 13:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2604) Use servlet protocol in xts arquillian tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2604: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use servlet protocol in xts arquillian tests > -------------------------------------------- > > Key: JBTM-2604 > URL: https://issues.jboss.org/browse/JBTM-2604 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > https://issues.jboss.org/browse/WFLY-5949 was caused by using jmx protocol instead of servlet in arquillian tests. Therefore, to make sure this doesn't happen in other tests, we should set servlet as a default protocol in all arquillian tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 12 03:58:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 12 Jan 2016 03:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2607) Slight docs issue on wording of heuristic outcomes In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2607: ----------------------------------- Summary: Slight docs issue on wording of heuristic outcomes Key: JBTM-2607 URL: https://issues.jboss.org/browse/JBTM-2607 Project: JBoss Transaction Manager Issue Type: Bug Components: Documentation Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next The text makes it sound like heuristic rollback can be achieved from only a subset of resources rolling back. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 12 04:02:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 12 Jan 2016 04:02:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2607) Slight docs issue on wording of heuristic outcomes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #35 in GitHub ------------------------------------------------------------------------------------------ Status: Pull Request Sent (was: Open) > Slight docs issue on wording of heuristic outcomes > -------------------------------------------------- > > Key: JBTM-2607 > URL: https://issues.jboss.org/browse/JBTM-2607 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > The text makes it sound like heuristic rollback can be achieved from only a subset of resources rolling back. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 12 04:03:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 12 Jan 2016 04:03:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2607) Slight docs issue on wording of heuristic outcomes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2607: -------------------------------- Priority: Minor (was: Major) > Slight docs issue on wording of heuristic outcomes > -------------------------------------------------- > > Key: JBTM-2607 > URL: https://issues.jboss.org/browse/JBTM-2607 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > The text makes it sound like heuristic rollback can be achieved from only a subset of resources rolling back. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 12 16:53:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 12 Jan 2016 16:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2607) Slight docs issue on wording of heuristic outcomes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2607: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Slight docs issue on wording of heuristic outcomes > -------------------------------------------------- > > Key: JBTM-2607 > URL: https://issues.jboss.org/browse/JBTM-2607 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > The text makes it sound like heuristic rollback can be achieved from only a subset of resources rolling back. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 14 05:13:00 2016 From: issues at jboss.org (Jive JIRA Integration (JIRA)) Date: Thu, 14 Jan 2016 05:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2605) Narayana Spring integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jive JIRA Integration updated JBTM-2605: ---------------------------------------- Forum Reference: https://developer.jboss.org/message/948921#948921 > Narayana Spring integration > --------------------------- > > Key: JBTM-2605 > URL: https://issues.jboss.org/browse/JBTM-2605 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, Documentation, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > This is a wrapper for all subtasks related with Spring integration. > As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 15 05:06:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 15 Jan 2016 05:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2603) Socket read timed out in EnabledContextPropagationTests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149218#comment-13149218 ] Gytis Trikleris commented on JBTM-2603: --------------------------------------- Reproduction job failed only once in 130 runs, so will have to find a way to trigger the failure locally. However, since it's not failing very often I'm leaving the issue as minor. > Socket read timed out in EnabledContextPropagationTests > ------------------------------------------------------- > > Key: JBTM-2603 > URL: https://issues.jboss.org/browse/JBTM-2603 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Test output: > {code} > testNoTransactionWithDisabledJTAOverWSATFeature(org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests) Time elapsed: 76.255 sec <<< ERROR! > org.apache.http.client.HttpResponseException: Internal Server Error > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:68) > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:54) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.makeRequest(EnabledContextPropagationTests.java:377) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.testNoTransactionWithDisabledJTAOverWSATFeature(EnabledContextPropagationTests.java:256) > {code} > Server log: > {code} > [0mJan 06, 2016 12:53:47 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance > Jan 06, 2016 12:53:47 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > Jan 06, 2016 12:53:47 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dorg.jboss.byteman.debug=true, -Dorg.jboss.byteman.verbose=true, -Dorg.jboss.byteman.contrib.dtest.rmiregistry.port=1199, -javaagent:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/txbridge/target/byteman/byteman.jar=port:9091,listener:true,sys:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/txbridge/target/byteman/byteman-dtest.jar, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-xts.xml] > Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 00:53:48,689 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.0.Final > 00:53:49,098 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 00:53:49,246 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Core 2.0.5.Final "Kenny" starting > 00:53:51,591 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 00:53:51,629 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.4.Final > 00:53:51,659 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.4.Final > 00:53:51,751 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 40) WFLYCLINF0001: Activating Infinispan subsystem. > 00:53:51,743 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 00:53:51,771 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 39) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 00:53:51,815 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 41) WFLYIIOP0001: Activating IIOP Subsystem > 00:53:51,837 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 47) WFLYJSF0007: Activated the following JSF Implementations: [main] > 00:53:51,847 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.1.Final) > 00:53:51,913 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2 > 00:53:51,958 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.17.Final-wildfly-1 > 00:53:51,994 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. > 00:53:52,039 INFO [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem > 00:53:52,039 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 61) WFLYWS0002: Activating WebServices Extension > 00:53:52,076 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem > 00:53:52,066 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.4.Final > 00:53:52,227 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.11.Final starting > 00:53:52,237 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0003: Undertow 1.3.11.Final starting > 00:53:52,593 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 32 (per class), which is derived from thread worker pool sizing. > 00:53:52,594 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 8 (per class), which is derived from the number of CPUs on this host. > 00:53:52,713 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service > 00:53:52,723 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 00:53:52,887 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 00:53:52,934 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. > 00:53:52,938 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 00:53:53,155 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 00:53:53,521 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 00:53:53,575 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-4) WFLYIIOP0009: CORBA ORB Service started > 00:53:53,916 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final > 00:53:54,002 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "restat-web-5.2.13.Final-SNAPSHOT.war" (runtime-name: "restat-web-5.2.13.Final-SNAPSHOT.war") > 00:53:54,004 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/deployments > 00:53:54,004 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "xtstest.war" (runtime-name: "xtstest.war") > 00:53:54,192 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/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 00:53:54,248 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.2.Final (Apache CXF 3.1.4) > 00:53:54,351 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221013: Using NIO Journal > 00:53:54,505 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-c11 > 00:53:54,506 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-client > 00:53:54,511 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-coordinator > 00:53:54,659 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) 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 > 00:53:54,661 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) 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 > 00:53:54,667 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:54,667 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:54,668 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,668 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,669 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,670 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,723 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,724 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,724 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,966 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 00:53:54,988 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 00:53:55,029 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 00:53:55,034 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 00:53:55,155 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-participant > 00:53:55,156 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:55,168 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:55,169 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:56,128 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}CompletionCoordinatorService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > 00:53:56,138 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from class com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > 00:53:56,137 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) 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 > 00:53:56,131 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationParticipantPortType > 00:53:57,259 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live > 00:53:57,276 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010 [nodeID=7842cabe-b404-11e5-9b8e-a55e51d89294] > 00:53:57,412 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/ws-t11-client/TerminationParticipantService > 00:53:57,419 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > 00:53:57,412 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > 00:53:57,532 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-c11/ActivationService > 00:53:57,685 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorService.wsdl > 00:53:57,704 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationCoordinatorPortType > 00:53:57,705 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/ActivationService.wsdl > 00:53:57,713 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from class com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > 00:53:57,701 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/TerminationParticipantService.wsdl > 00:53:57,715 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService from class com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > 00:53:57,721 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithCoordinatorCompletionParticipantService.wsdl > 00:53:57,731 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}ParticipantService from class com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > 00:53:57,749 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > 00:53:57,773 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/ws-t11-client/CompletionInitiatorService > 00:53:57,779 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-c11/RegistrationService > 00:53:57,785 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorService.wsdl > 00:53:57,795 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService from class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > 00:53:57,804 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/ParticipantService > 00:53:57,808 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > 00:53:57,822 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/CompletionInitiatorService.wsdl > 00:53:57,831 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorRPCPortTypeImplService.wsdl > 00:53:57,827 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/RegistrationService.wsdl > 00:53:57,836 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}BusinessAgreementWithCoordinatorCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > 00:53:57,842 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/ParticipantService.wsdl > 00:53:57,851 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > 00:53:57,903 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > 00:53:57,953 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithParticipantCompletionParticipantService.wsdl > 00:53:57,960 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:53:57,988 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 00:53:58,005 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 00:53:58,014 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 00:53:58,015 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 00:53:58,025 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithCoordinatorCompletionCoordinatorService.wsdl > 00:53:58,027 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}BusinessAgreementWithParticipantCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > 00:53:58,044 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 00:53:58,045 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 00:53:58,052 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 00:53:58,053 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 00:53:58,061 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > 00:53:58,063 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 00:53:58,070 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 00:53:58,111 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 00:53:58,119 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 00:53:58,123 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithParticipantCompletionCoordinatorService.wsdl > 00:53:58,124 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}CoordinatorService from class com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > 00:53:58,145 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CoordinatorService > 00:53:58,182 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 64) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 00:53:58,193 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CoordinatorService.wsdl > 00:53:58,203 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}CompletionCoordinatorRPCService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > 00:53:58,210 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 00:53:58,212 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221003: trying to deploy queue jms.queue.DLQ > 00:53:58,217 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-c11 > 00:53:58,228 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 65) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 00:53:58,235 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > 00:53:58,261 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorRPCService.wsdl > 00:53:58,287 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-client > 00:53:58,297 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-participant > 00:53:58,352 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0021: Registered web context: /ws-t11-client > 00:53:58,359 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: /ws-c11 > 00:53:58,360 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:53:58,359 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0021: Registered web context: /ws-t11-participant > 00:53:58,361 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 00:53:58,361 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 00:53:58,362 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 00:53:58,362 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 00:53:58,364 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 00:53:58,366 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 00:53:58,390 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-coordinator > 00:53:58,402 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0021: Registered web context: /ws-t11-coordinator > 00:53:58,413 WARN [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0005: Secure listener for protocol: 'HTTP/1.1' not found! Using non secure port! > 00:53:58,517 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.restat-web-5.2.13.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:53:58,523 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.restat-web-5.2.13.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:53:58,591 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 00:53:58,776 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033006: InboundBridgeRecoveryManager starting > 00:53:58,777 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033013: OutboundBridgeRecoveryManager starting > 00:53:58,821 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) Resource adaptor started > 00:53:58,821 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatoractivemq-ra > 00:53:58,823 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 00:53:58,823 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 00:53:58,950 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. > 00:53:58,995 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment xtstest.war > 00:53:59,138 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.2.2.Final > 00:53:59,403 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0021: Registered web context: /rest-tx > 00:53:59,533 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: xtstest.war > 00:53:59,587 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.3.2 (Final) > 00:53:59,600 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,601 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,601 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,602 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,616 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,679 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest1 > 00:53:59,689 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,690 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,693 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest2 > 00:53:59,719 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,722 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,726 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest3 > 00:53:59,737 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,740 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,743 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtssubordinateservicetest1 > 00:53:59,750 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,780 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 00:53:59,781 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 00:53:59,784 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 00:53:59,785 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 00:53:59,792 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0009: Starting weld service for deployment xtstest.war > 00:54:00,907 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 65) Starting XTSServiceTestRunner > 00:54:00,908 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 65) Started XTSServiceTestRunner > 00:54:00,925 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 65) Initializing Mojarra 2.2.12-jbossorg-2 20150729-1131 for context '/xtstest' > 00:54:01,758 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0021: Registered web context: /xtstest > 00:54:01,792 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") > 00:54:01,794 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "restat-web-5.2.13.Final-SNAPSHOT.war" (runtime-name : "restat-web-5.2.13.Final-SNAPSHOT.war") > 00:54:02,073 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 00:54:02,074 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 00:54:02,074 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.0.5.Final "Kenny" started in 13928ms - Started 567 of 876 services (423 services are lazy, passive or on-demand) > Jan 06, 2016 12:54:02 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Automatic deploying of the managed deployment with name txbridge-outbound-tests-service for the container with name jboss > 00:54:02,228 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/9b/70e2a1644d4faf24e750f2cf3b295db924703a/content > 00:54:02,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "txbridge-outbound-tests-service.war" (runtime-name: "txbridge-outbound-tests-service.war") > 00:54:02,258 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-service.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:54:02,329 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=OutboundTestServiceATServlet > address=http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl > implementor=org.jboss.jbossts.txbridge.tests.outbound.service.TestATServiceImpl > serviceName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService > portName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplPort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 00:54:02,329 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=OutboundTestServiceNonATServlet > address=http://localhost:8080/txbridge-outbound-tests-service/TestNonATServiceImpl > implementor=org.jboss.jbossts.txbridge.tests.outbound.service.TestNonATServiceImpl > serviceName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplService > portName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplPort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 00:54:02,350 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from class org.jboss.jbossts.txbridge.tests.outbound.service.TestATServiceImpl > 00:54:02,377 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl > 00:54:02,392 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/txbridge-outbound-tests-service.war/TestATServiceImplService.wsdl > 00:54:02,396 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplService from class org.jboss.jbossts.txbridge.tests.outbound.service.TestNonATServiceImpl > 00:54:02,399 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/txbridge-outbound-tests-service/TestNonATServiceImpl > 00:54:02,404 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/txbridge-outbound-tests-service.war/TestNonATServiceImplService.wsdl > 00:54:02,422 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceATServlet > 00:54:02,422 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceNonATServlet > 00:54:02,434 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /txbridge-outbound-tests-service > 00:54:02,492 INFO [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "txbridge-outbound-tests-service.war" (runtime-name : "txbridge-outbound-tests-service.war") > Jan 06, 2016 12:54:02 AM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > Jan 06, 2016 12:54:02 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Automatic deploying of the managed deployment with name txbridge-outbound-tests-client for the container with name jboss > 00:54:02,720 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/b3/6bdfaa5feca5ff426c038cb7f2f2fed119847f/content > 00:54:02,723 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "txbridge-outbound-tests-client.war" (runtime-name: "txbridge-outbound-tests-client.war") > 00:54:02,746 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-client.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:54:02,746 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-client.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 00:54:02,810 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /txbridge-outbound-tests-client > 00:54:02,823 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "txbridge-outbound-tests-client.war" (runtime-name : "txbridge-outbound-tests-client.war") > 00:54:03,077 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from WSDL: http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl?wsdl > 00:54:03,099 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from WSDL: http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl?wsdl > 00:55:03,344 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default task-1) Interceptor for {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService#{http://client.outbound.tests.txbridge.jbossts.jboss.org/}doNothing has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not send Message. > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > at com.sun.proxy.$Proxy137.doNothing(Unknown Source) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:140) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.doPost(TestATClient.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl: Read timed out > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > ... 39 more > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > ... 42 more > 00:55:03,349 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /txbridge-outbound-tests-client//testATClient: java.lang.RuntimeException: javax.xml.ws.WebServiceException: Could not send Message. > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:148) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.doPost(TestATClient.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: javax.xml.ws.WebServiceException: Could not send Message. > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:150) > at com.sun.proxy.$Proxy137.doNothing(Unknown Source) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:140) > ... 30 more > Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl: Read timed out > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > ... 32 more > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > ... 42 more > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Automatic undeploying of the managed deployment with name txbridge-outbound-tests-service from the container with name jboss > 00:55:03,375 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 70) WFLYUT0022: Unregistered web context: /txbridge-outbound-tests-service > 00:55:03,387 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceNonATServlet > 00:55:03,389 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceATServlet > 00:55:03,452 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment txbridge-outbound-tests-service.war (runtime-name: txbridge-outbound-tests-service.war) in 85ms > 00:55:03,469 INFO [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/9b/70e2a1644d4faf24e750f2cf3b295db924703a/content > 00:55:03,469 INFO [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0009: Undeployed "txbridge-outbound-tests-service.war" (runtime-name: "txbridge-outbound-tests-service.war") > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Automatic undeploying of the managed deployment with name txbridge-outbound-tests-client from the container with name jboss > 00:55:03,481 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Unregistered web context: /txbridge-outbound-tests-client > 00:55:03,491 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment txbridge-outbound-tests-client.war (runtime-name: txbridge-outbound-tests-client.war) in 12ms > 00:55:03,502 INFO [org.jboss.as.repository] (management-handler-thread - 6) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/b3/6bdfaa5feca5ff426c038cb7f2f2fed119847f/content > 00:55:03,502 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0009: Undeployed "txbridge-outbound-tests-client.war" (runtime-name: "txbridge-outbound-tests-client.war") > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 00:55:03,508 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0211: Suspending server with 0ms timeout. > 00:55:03,512 INFO [org.jboss.as.server] (Thread-3) WFLYSRV0220: Server shutdown has been requested. > 00:55:03,544 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-3) ARJUNA033014: OutboundBridgeRecoveryManager stopping > 00:55:03,545 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-1) ARJUNA033007: InboundBridgeRecoveryManager stopping > 00:55:03,557 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Unregistered web context: /rest-tx > 00:55:03,567 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 00:55:03,577 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: /xtstest > 00:55:03,582 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > 00:55:03,587 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 71) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory > 00:55:03,604 ERROR [org.jboss.remoting.resource] (Remoting "brandon:MANAGEMENT" task-8) Close action for Channel ID 25c56b1d (inbound) of Remoting connection 01cf11a2 to /127.0.0.1:47100 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating > at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588) > at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327) > at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138) > at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261) > at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534) > at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372) > at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437) > at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114) > at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > 00:55:03,608 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-coordinator > 00:55:03,612 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-client > 00:55:03,612 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0022: Unregistered web context: /ws-t11-client > 00:55:03,613 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-participant > 00:55:03,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0022: Unregistered web context: /ws-t11-participant > 00:55:03,613 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-c11 > 00:55:03,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0022: Unregistered web context: /ws-c11 > 00:55:03,617 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /ws-t11-coordinator > 00:55:03,617 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 00:55:03,618 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 00:55:03,620 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 00:55:03,621 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-client > 00:55:03,620 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 00:55:03,624 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-c11 > 00:55:03,634 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 00:55:03,634 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 00:55:03,635 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 00:55:03,637 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 00:55:03,637 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 00:55:03,641 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 00:55:03,643 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:55:03,643 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-participant > 00:55:03,644 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-coordinator > 00:55:03,655 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 74) Stopping XTSServiceTestRunner > 00:55:03,656 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 74) Stopped XTSServiceTestRunner > 00:55:03,657 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 75) AMQ151003: resource adaptor stopped > 00:55:03,678 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment restat-web-5.2.13.Final-SNAPSHOT.war (runtime-name: restat-web-5.2.13.Final-SNAPSHOT.war) in 159ms > 00:55:03,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0019: Host default-host stopping > 00:55:03,711 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 00:55:03,712 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 00:55:03,711 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 00:55:03,713 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 00:55:03,714 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0010: Stopping weld service for deployment xtstest.war > 00:55:03,772 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 00:55:03,787 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 00:55:03,805 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010 [7842cabe-b404-11e5-9b8e-a55e51d89294] stopped > 00:55:03,806 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending > 00:55:03,807 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 00:55:03,808 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.3.11.Final stopping > 00:55:03,827 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment xtstest.war (runtime-name: xtstest.war) in 308ms > 00:55:03,836 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.0.5.Final "Kenny" stopped in 284ms > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 15 05:11:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 15 Jan 2016 05:11:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2603) Socket read timed out in EnabledContextPropagationTests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149218#comment-13149218 ] Gytis Trikleris edited comment on JBTM-2603 at 1/15/16 5:10 AM: ---------------------------------------------------------------- Reproduction job failed only once [1] in 130 runs, so will have to find a way to trigger the failure locally. However, since it's not failing very often I'm leaving the issue as minor. [1] http://albany.eng.hst.ams2.redhat.com/view/Narayana-JBTM/job/JBTM-2603/117/ was (Author: gytis): Reproduction job failed only once in 130 runs, so will have to find a way to trigger the failure locally. However, since it's not failing very often I'm leaving the issue as minor. > Socket read timed out in EnabledContextPropagationTests > ------------------------------------------------------- > > Key: JBTM-2603 > URL: https://issues.jboss.org/browse/JBTM-2603 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Test output: > {code} > testNoTransactionWithDisabledJTAOverWSATFeature(org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests) Time elapsed: 76.255 sec <<< ERROR! > org.apache.http.client.HttpResponseException: Internal Server Error > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:68) > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:54) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.makeRequest(EnabledContextPropagationTests.java:377) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.testNoTransactionWithDisabledJTAOverWSATFeature(EnabledContextPropagationTests.java:256) > {code} > Server log: > {code} > [0mJan 06, 2016 12:53:47 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance > Jan 06, 2016 12:53:47 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > Jan 06, 2016 12:53:47 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dorg.jboss.byteman.debug=true, -Dorg.jboss.byteman.verbose=true, -Dorg.jboss.byteman.contrib.dtest.rmiregistry.port=1199, -javaagent:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/txbridge/target/byteman/byteman.jar=port:9091,listener:true,sys:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/txbridge/target/byteman/byteman-dtest.jar, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-xts.xml] > Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 00:53:48,689 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.0.Final > 00:53:49,098 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 00:53:49,246 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Core 2.0.5.Final "Kenny" starting > 00:53:51,591 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 00:53:51,629 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.4.Final > 00:53:51,659 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.4.Final > 00:53:51,751 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 40) WFLYCLINF0001: Activating Infinispan subsystem. > 00:53:51,743 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 00:53:51,771 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 39) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 00:53:51,815 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 41) WFLYIIOP0001: Activating IIOP Subsystem > 00:53:51,837 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 47) WFLYJSF0007: Activated the following JSF Implementations: [main] > 00:53:51,847 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.1.Final) > 00:53:51,913 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2 > 00:53:51,958 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.17.Final-wildfly-1 > 00:53:51,994 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. > 00:53:52,039 INFO [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem > 00:53:52,039 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 61) WFLYWS0002: Activating WebServices Extension > 00:53:52,076 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem > 00:53:52,066 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.4.Final > 00:53:52,227 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.11.Final starting > 00:53:52,237 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0003: Undertow 1.3.11.Final starting > 00:53:52,593 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 32 (per class), which is derived from thread worker pool sizing. > 00:53:52,594 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 8 (per class), which is derived from the number of CPUs on this host. > 00:53:52,713 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service > 00:53:52,723 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 00:53:52,887 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 00:53:52,934 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. > 00:53:52,938 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 00:53:53,155 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 00:53:53,521 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 00:53:53,575 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-4) WFLYIIOP0009: CORBA ORB Service started > 00:53:53,916 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final > 00:53:54,002 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "restat-web-5.2.13.Final-SNAPSHOT.war" (runtime-name: "restat-web-5.2.13.Final-SNAPSHOT.war") > 00:53:54,004 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/deployments > 00:53:54,004 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "xtstest.war" (runtime-name: "xtstest.war") > 00:53:54,192 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/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 00:53:54,248 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.2.Final (Apache CXF 3.1.4) > 00:53:54,351 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221013: Using NIO Journal > 00:53:54,505 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-c11 > 00:53:54,506 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-client > 00:53:54,511 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-coordinator > 00:53:54,659 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) 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 > 00:53:54,661 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) 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 > 00:53:54,667 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:54,667 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:54,668 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,668 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,669 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,670 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,723 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,724 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,724 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,966 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 00:53:54,988 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 00:53:55,029 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 00:53:55,034 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 00:53:55,155 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-participant > 00:53:55,156 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:55,168 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:55,169 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:56,128 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}CompletionCoordinatorService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > 00:53:56,138 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from class com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > 00:53:56,137 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) 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 > 00:53:56,131 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationParticipantPortType > 00:53:57,259 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live > 00:53:57,276 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010 [nodeID=7842cabe-b404-11e5-9b8e-a55e51d89294] > 00:53:57,412 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/ws-t11-client/TerminationParticipantService > 00:53:57,419 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > 00:53:57,412 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > 00:53:57,532 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-c11/ActivationService > 00:53:57,685 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorService.wsdl > 00:53:57,704 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationCoordinatorPortType > 00:53:57,705 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/ActivationService.wsdl > 00:53:57,713 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from class com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > 00:53:57,701 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/TerminationParticipantService.wsdl > 00:53:57,715 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService from class com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > 00:53:57,721 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithCoordinatorCompletionParticipantService.wsdl > 00:53:57,731 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}ParticipantService from class com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > 00:53:57,749 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > 00:53:57,773 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/ws-t11-client/CompletionInitiatorService > 00:53:57,779 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-c11/RegistrationService > 00:53:57,785 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorService.wsdl > 00:53:57,795 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService from class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > 00:53:57,804 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/ParticipantService > 00:53:57,808 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > 00:53:57,822 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/CompletionInitiatorService.wsdl > 00:53:57,831 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorRPCPortTypeImplService.wsdl > 00:53:57,827 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/RegistrationService.wsdl > 00:53:57,836 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}BusinessAgreementWithCoordinatorCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > 00:53:57,842 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/ParticipantService.wsdl > 00:53:57,851 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > 00:53:57,903 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > 00:53:57,953 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithParticipantCompletionParticipantService.wsdl > 00:53:57,960 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:53:57,988 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 00:53:58,005 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 00:53:58,014 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 00:53:58,015 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 00:53:58,025 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithCoordinatorCompletionCoordinatorService.wsdl > 00:53:58,027 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}BusinessAgreementWithParticipantCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > 00:53:58,044 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 00:53:58,045 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 00:53:58,052 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 00:53:58,053 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 00:53:58,061 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > 00:53:58,063 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 00:53:58,070 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 00:53:58,111 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 00:53:58,119 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 00:53:58,123 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithParticipantCompletionCoordinatorService.wsdl > 00:53:58,124 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}CoordinatorService from class com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > 00:53:58,145 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CoordinatorService > 00:53:58,182 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 64) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 00:53:58,193 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CoordinatorService.wsdl > 00:53:58,203 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}CompletionCoordinatorRPCService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > 00:53:58,210 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 00:53:58,212 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221003: trying to deploy queue jms.queue.DLQ > 00:53:58,217 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-c11 > 00:53:58,228 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 65) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 00:53:58,235 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > 00:53:58,261 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorRPCService.wsdl > 00:53:58,287 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-client > 00:53:58,297 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-participant > 00:53:58,352 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0021: Registered web context: /ws-t11-client > 00:53:58,359 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: /ws-c11 > 00:53:58,360 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:53:58,359 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0021: Registered web context: /ws-t11-participant > 00:53:58,361 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 00:53:58,361 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 00:53:58,362 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 00:53:58,362 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 00:53:58,364 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 00:53:58,366 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 00:53:58,390 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-coordinator > 00:53:58,402 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0021: Registered web context: /ws-t11-coordinator > 00:53:58,413 WARN [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0005: Secure listener for protocol: 'HTTP/1.1' not found! Using non secure port! > 00:53:58,517 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.restat-web-5.2.13.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:53:58,523 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.restat-web-5.2.13.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:53:58,591 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 00:53:58,776 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033006: InboundBridgeRecoveryManager starting > 00:53:58,777 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033013: OutboundBridgeRecoveryManager starting > 00:53:58,821 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) Resource adaptor started > 00:53:58,821 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatoractivemq-ra > 00:53:58,823 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 00:53:58,823 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 00:53:58,950 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. > 00:53:58,995 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment xtstest.war > 00:53:59,138 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.2.2.Final > 00:53:59,403 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0021: Registered web context: /rest-tx > 00:53:59,533 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: xtstest.war > 00:53:59,587 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.3.2 (Final) > 00:53:59,600 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,601 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,601 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,602 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,616 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,679 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest1 > 00:53:59,689 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,690 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,693 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest2 > 00:53:59,719 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,722 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,726 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest3 > 00:53:59,737 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,740 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,743 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtssubordinateservicetest1 > 00:53:59,750 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,780 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 00:53:59,781 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 00:53:59,784 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 00:53:59,785 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 00:53:59,792 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0009: Starting weld service for deployment xtstest.war > 00:54:00,907 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 65) Starting XTSServiceTestRunner > 00:54:00,908 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 65) Started XTSServiceTestRunner > 00:54:00,925 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 65) Initializing Mojarra 2.2.12-jbossorg-2 20150729-1131 for context '/xtstest' > 00:54:01,758 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0021: Registered web context: /xtstest > 00:54:01,792 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") > 00:54:01,794 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "restat-web-5.2.13.Final-SNAPSHOT.war" (runtime-name : "restat-web-5.2.13.Final-SNAPSHOT.war") > 00:54:02,073 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 00:54:02,074 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 00:54:02,074 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.0.5.Final "Kenny" started in 13928ms - Started 567 of 876 services (423 services are lazy, passive or on-demand) > Jan 06, 2016 12:54:02 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Automatic deploying of the managed deployment with name txbridge-outbound-tests-service for the container with name jboss > 00:54:02,228 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/9b/70e2a1644d4faf24e750f2cf3b295db924703a/content > 00:54:02,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "txbridge-outbound-tests-service.war" (runtime-name: "txbridge-outbound-tests-service.war") > 00:54:02,258 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-service.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:54:02,329 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=OutboundTestServiceATServlet > address=http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl > implementor=org.jboss.jbossts.txbridge.tests.outbound.service.TestATServiceImpl > serviceName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService > portName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplPort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 00:54:02,329 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=OutboundTestServiceNonATServlet > address=http://localhost:8080/txbridge-outbound-tests-service/TestNonATServiceImpl > implementor=org.jboss.jbossts.txbridge.tests.outbound.service.TestNonATServiceImpl > serviceName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplService > portName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplPort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 00:54:02,350 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from class org.jboss.jbossts.txbridge.tests.outbound.service.TestATServiceImpl > 00:54:02,377 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl > 00:54:02,392 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/txbridge-outbound-tests-service.war/TestATServiceImplService.wsdl > 00:54:02,396 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplService from class org.jboss.jbossts.txbridge.tests.outbound.service.TestNonATServiceImpl > 00:54:02,399 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/txbridge-outbound-tests-service/TestNonATServiceImpl > 00:54:02,404 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/txbridge-outbound-tests-service.war/TestNonATServiceImplService.wsdl > 00:54:02,422 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceATServlet > 00:54:02,422 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceNonATServlet > 00:54:02,434 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /txbridge-outbound-tests-service > 00:54:02,492 INFO [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "txbridge-outbound-tests-service.war" (runtime-name : "txbridge-outbound-tests-service.war") > Jan 06, 2016 12:54:02 AM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > Jan 06, 2016 12:54:02 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Automatic deploying of the managed deployment with name txbridge-outbound-tests-client for the container with name jboss > 00:54:02,720 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/b3/6bdfaa5feca5ff426c038cb7f2f2fed119847f/content > 00:54:02,723 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "txbridge-outbound-tests-client.war" (runtime-name: "txbridge-outbound-tests-client.war") > 00:54:02,746 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-client.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:54:02,746 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-client.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 00:54:02,810 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /txbridge-outbound-tests-client > 00:54:02,823 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "txbridge-outbound-tests-client.war" (runtime-name : "txbridge-outbound-tests-client.war") > 00:54:03,077 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from WSDL: http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl?wsdl > 00:54:03,099 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from WSDL: http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl?wsdl > 00:55:03,344 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default task-1) Interceptor for {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService#{http://client.outbound.tests.txbridge.jbossts.jboss.org/}doNothing has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not send Message. > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > at com.sun.proxy.$Proxy137.doNothing(Unknown Source) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:140) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.doPost(TestATClient.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl: Read timed out > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > ... 39 more > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > ... 42 more > 00:55:03,349 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /txbridge-outbound-tests-client//testATClient: java.lang.RuntimeException: javax.xml.ws.WebServiceException: Could not send Message. > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:148) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.doPost(TestATClient.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: javax.xml.ws.WebServiceException: Could not send Message. > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:150) > at com.sun.proxy.$Proxy137.doNothing(Unknown Source) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:140) > ... 30 more > Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl: Read timed out > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > ... 32 more > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > ... 42 more > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Automatic undeploying of the managed deployment with name txbridge-outbound-tests-service from the container with name jboss > 00:55:03,375 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 70) WFLYUT0022: Unregistered web context: /txbridge-outbound-tests-service > 00:55:03,387 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceNonATServlet > 00:55:03,389 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceATServlet > 00:55:03,452 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment txbridge-outbound-tests-service.war (runtime-name: txbridge-outbound-tests-service.war) in 85ms > 00:55:03,469 INFO [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/9b/70e2a1644d4faf24e750f2cf3b295db924703a/content > 00:55:03,469 INFO [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0009: Undeployed "txbridge-outbound-tests-service.war" (runtime-name: "txbridge-outbound-tests-service.war") > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Automatic undeploying of the managed deployment with name txbridge-outbound-tests-client from the container with name jboss > 00:55:03,481 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Unregistered web context: /txbridge-outbound-tests-client > 00:55:03,491 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment txbridge-outbound-tests-client.war (runtime-name: txbridge-outbound-tests-client.war) in 12ms > 00:55:03,502 INFO [org.jboss.as.repository] (management-handler-thread - 6) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/b3/6bdfaa5feca5ff426c038cb7f2f2fed119847f/content > 00:55:03,502 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0009: Undeployed "txbridge-outbound-tests-client.war" (runtime-name: "txbridge-outbound-tests-client.war") > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 00:55:03,508 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0211: Suspending server with 0ms timeout. > 00:55:03,512 INFO [org.jboss.as.server] (Thread-3) WFLYSRV0220: Server shutdown has been requested. > 00:55:03,544 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-3) ARJUNA033014: OutboundBridgeRecoveryManager stopping > 00:55:03,545 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-1) ARJUNA033007: InboundBridgeRecoveryManager stopping > 00:55:03,557 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Unregistered web context: /rest-tx > 00:55:03,567 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 00:55:03,577 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: /xtstest > 00:55:03,582 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > 00:55:03,587 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 71) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory > 00:55:03,604 ERROR [org.jboss.remoting.resource] (Remoting "brandon:MANAGEMENT" task-8) Close action for Channel ID 25c56b1d (inbound) of Remoting connection 01cf11a2 to /127.0.0.1:47100 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating > at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588) > at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327) > at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138) > at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261) > at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534) > at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372) > at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437) > at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114) > at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > 00:55:03,608 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-coordinator > 00:55:03,612 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-client > 00:55:03,612 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0022: Unregistered web context: /ws-t11-client > 00:55:03,613 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-participant > 00:55:03,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0022: Unregistered web context: /ws-t11-participant > 00:55:03,613 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-c11 > 00:55:03,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0022: Unregistered web context: /ws-c11 > 00:55:03,617 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /ws-t11-coordinator > 00:55:03,617 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 00:55:03,618 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 00:55:03,620 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 00:55:03,621 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-client > 00:55:03,620 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 00:55:03,624 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-c11 > 00:55:03,634 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 00:55:03,634 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 00:55:03,635 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 00:55:03,637 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 00:55:03,637 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 00:55:03,641 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 00:55:03,643 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:55:03,643 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-participant > 00:55:03,644 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-coordinator > 00:55:03,655 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 74) Stopping XTSServiceTestRunner > 00:55:03,656 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 74) Stopped XTSServiceTestRunner > 00:55:03,657 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 75) AMQ151003: resource adaptor stopped > 00:55:03,678 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment restat-web-5.2.13.Final-SNAPSHOT.war (runtime-name: restat-web-5.2.13.Final-SNAPSHOT.war) in 159ms > 00:55:03,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0019: Host default-host stopping > 00:55:03,711 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 00:55:03,712 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 00:55:03,711 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 00:55:03,713 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 00:55:03,714 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0010: Stopping weld service for deployment xtstest.war > 00:55:03,772 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 00:55:03,787 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 00:55:03,805 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010 [7842cabe-b404-11e5-9b8e-a55e51d89294] stopped > 00:55:03,806 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending > 00:55:03,807 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 00:55:03,808 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.3.11.Final stopping > 00:55:03,827 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment xtstest.war (runtime-name: xtstest.war) in 308ms > 00:55:03,836 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.0.5.Final "Kenny" stopped in 284ms > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 15 05:47:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 15 Jan 2016 05:47:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2603) Socket read timed out in EnabledContextPropagationTests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149248#comment-13149248 ] Tom Jenkinson commented on JBTM-2603: ------------------------------------- Might as well disable the reproduction job then and delete the original CI failure so it doesn't clutter the CI report if you have the logs you need in the reproducting CI job. > Socket read timed out in EnabledContextPropagationTests > ------------------------------------------------------- > > Key: JBTM-2603 > URL: https://issues.jboss.org/browse/JBTM-2603 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Test output: > {code} > testNoTransactionWithDisabledJTAOverWSATFeature(org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests) Time elapsed: 76.255 sec <<< ERROR! > org.apache.http.client.HttpResponseException: Internal Server Error > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:68) > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:54) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.makeRequest(EnabledContextPropagationTests.java:377) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.testNoTransactionWithDisabledJTAOverWSATFeature(EnabledContextPropagationTests.java:256) > {code} > Server log: > {code} > [0mJan 06, 2016 12:53:47 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance > Jan 06, 2016 12:53:47 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > Jan 06, 2016 12:53:47 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dorg.jboss.byteman.debug=true, -Dorg.jboss.byteman.verbose=true, -Dorg.jboss.byteman.contrib.dtest.rmiregistry.port=1199, -javaagent:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/txbridge/target/byteman/byteman.jar=port:9091,listener:true,sys:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/txbridge/target/byteman/byteman-dtest.jar, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-xts.xml] > Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 00:53:48,689 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.0.Final > 00:53:49,098 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 00:53:49,246 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Core 2.0.5.Final "Kenny" starting > 00:53:51,591 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 00:53:51,629 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.4.Final > 00:53:51,659 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.4.Final > 00:53:51,751 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 40) WFLYCLINF0001: Activating Infinispan subsystem. > 00:53:51,743 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 00:53:51,771 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 39) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 00:53:51,815 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 41) WFLYIIOP0001: Activating IIOP Subsystem > 00:53:51,837 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 47) WFLYJSF0007: Activated the following JSF Implementations: [main] > 00:53:51,847 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.1.Final) > 00:53:51,913 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2 > 00:53:51,958 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.17.Final-wildfly-1 > 00:53:51,994 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. > 00:53:52,039 INFO [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem > 00:53:52,039 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 61) WFLYWS0002: Activating WebServices Extension > 00:53:52,076 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem > 00:53:52,066 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.4.Final > 00:53:52,227 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.11.Final starting > 00:53:52,237 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0003: Undertow 1.3.11.Final starting > 00:53:52,593 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 32 (per class), which is derived from thread worker pool sizing. > 00:53:52,594 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 8 (per class), which is derived from the number of CPUs on this host. > 00:53:52,713 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service > 00:53:52,723 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 00:53:52,887 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 00:53:52,934 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. > 00:53:52,938 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 00:53:53,155 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 00:53:53,521 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 00:53:53,575 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-4) WFLYIIOP0009: CORBA ORB Service started > 00:53:53,916 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final > 00:53:54,002 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "restat-web-5.2.13.Final-SNAPSHOT.war" (runtime-name: "restat-web-5.2.13.Final-SNAPSHOT.war") > 00:53:54,004 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/deployments > 00:53:54,004 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "xtstest.war" (runtime-name: "xtstest.war") > 00:53:54,192 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/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 00:53:54,248 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.2.Final (Apache CXF 3.1.4) > 00:53:54,351 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221013: Using NIO Journal > 00:53:54,505 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-c11 > 00:53:54,506 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-client > 00:53:54,511 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-coordinator > 00:53:54,659 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) 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 > 00:53:54,661 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) 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 > 00:53:54,667 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:54,667 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:54,668 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,668 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,669 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,670 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,723 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,724 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,724 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,966 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 00:53:54,988 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 00:53:55,029 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 00:53:55,034 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 00:53:55,155 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-participant > 00:53:55,156 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:55,168 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:55,169 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:56,128 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}CompletionCoordinatorService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > 00:53:56,138 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from class com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > 00:53:56,137 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) 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 > 00:53:56,131 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationParticipantPortType > 00:53:57,259 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live > 00:53:57,276 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010 [nodeID=7842cabe-b404-11e5-9b8e-a55e51d89294] > 00:53:57,412 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/ws-t11-client/TerminationParticipantService > 00:53:57,419 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > 00:53:57,412 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > 00:53:57,532 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-c11/ActivationService > 00:53:57,685 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorService.wsdl > 00:53:57,704 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationCoordinatorPortType > 00:53:57,705 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/ActivationService.wsdl > 00:53:57,713 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from class com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > 00:53:57,701 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/TerminationParticipantService.wsdl > 00:53:57,715 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService from class com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > 00:53:57,721 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithCoordinatorCompletionParticipantService.wsdl > 00:53:57,731 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}ParticipantService from class com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > 00:53:57,749 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > 00:53:57,773 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/ws-t11-client/CompletionInitiatorService > 00:53:57,779 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-c11/RegistrationService > 00:53:57,785 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorService.wsdl > 00:53:57,795 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService from class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > 00:53:57,804 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/ParticipantService > 00:53:57,808 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > 00:53:57,822 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/CompletionInitiatorService.wsdl > 00:53:57,831 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorRPCPortTypeImplService.wsdl > 00:53:57,827 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/RegistrationService.wsdl > 00:53:57,836 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}BusinessAgreementWithCoordinatorCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > 00:53:57,842 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/ParticipantService.wsdl > 00:53:57,851 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > 00:53:57,903 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > 00:53:57,953 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithParticipantCompletionParticipantService.wsdl > 00:53:57,960 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:53:57,988 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 00:53:58,005 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 00:53:58,014 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 00:53:58,015 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 00:53:58,025 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithCoordinatorCompletionCoordinatorService.wsdl > 00:53:58,027 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}BusinessAgreementWithParticipantCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > 00:53:58,044 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 00:53:58,045 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 00:53:58,052 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 00:53:58,053 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 00:53:58,061 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > 00:53:58,063 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 00:53:58,070 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 00:53:58,111 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 00:53:58,119 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 00:53:58,123 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithParticipantCompletionCoordinatorService.wsdl > 00:53:58,124 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}CoordinatorService from class com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > 00:53:58,145 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CoordinatorService > 00:53:58,182 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 64) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 00:53:58,193 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CoordinatorService.wsdl > 00:53:58,203 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}CompletionCoordinatorRPCService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > 00:53:58,210 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 00:53:58,212 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221003: trying to deploy queue jms.queue.DLQ > 00:53:58,217 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-c11 > 00:53:58,228 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 65) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 00:53:58,235 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > 00:53:58,261 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorRPCService.wsdl > 00:53:58,287 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-client > 00:53:58,297 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-participant > 00:53:58,352 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0021: Registered web context: /ws-t11-client > 00:53:58,359 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: /ws-c11 > 00:53:58,360 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:53:58,359 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0021: Registered web context: /ws-t11-participant > 00:53:58,361 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 00:53:58,361 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 00:53:58,362 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 00:53:58,362 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 00:53:58,364 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 00:53:58,366 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 00:53:58,390 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-coordinator > 00:53:58,402 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0021: Registered web context: /ws-t11-coordinator > 00:53:58,413 WARN [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0005: Secure listener for protocol: 'HTTP/1.1' not found! Using non secure port! > 00:53:58,517 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.restat-web-5.2.13.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:53:58,523 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.restat-web-5.2.13.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:53:58,591 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 00:53:58,776 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033006: InboundBridgeRecoveryManager starting > 00:53:58,777 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033013: OutboundBridgeRecoveryManager starting > 00:53:58,821 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) Resource adaptor started > 00:53:58,821 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatoractivemq-ra > 00:53:58,823 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 00:53:58,823 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 00:53:58,950 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. > 00:53:58,995 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment xtstest.war > 00:53:59,138 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.2.2.Final > 00:53:59,403 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0021: Registered web context: /rest-tx > 00:53:59,533 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: xtstest.war > 00:53:59,587 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.3.2 (Final) > 00:53:59,600 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,601 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,601 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,602 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,616 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,679 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest1 > 00:53:59,689 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,690 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,693 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest2 > 00:53:59,719 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,722 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,726 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest3 > 00:53:59,737 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,740 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,743 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtssubordinateservicetest1 > 00:53:59,750 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,780 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 00:53:59,781 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 00:53:59,784 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 00:53:59,785 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 00:53:59,792 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0009: Starting weld service for deployment xtstest.war > 00:54:00,907 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 65) Starting XTSServiceTestRunner > 00:54:00,908 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 65) Started XTSServiceTestRunner > 00:54:00,925 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 65) Initializing Mojarra 2.2.12-jbossorg-2 20150729-1131 for context '/xtstest' > 00:54:01,758 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0021: Registered web context: /xtstest > 00:54:01,792 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") > 00:54:01,794 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "restat-web-5.2.13.Final-SNAPSHOT.war" (runtime-name : "restat-web-5.2.13.Final-SNAPSHOT.war") > 00:54:02,073 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 00:54:02,074 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 00:54:02,074 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.0.5.Final "Kenny" started in 13928ms - Started 567 of 876 services (423 services are lazy, passive or on-demand) > Jan 06, 2016 12:54:02 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Automatic deploying of the managed deployment with name txbridge-outbound-tests-service for the container with name jboss > 00:54:02,228 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/9b/70e2a1644d4faf24e750f2cf3b295db924703a/content > 00:54:02,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "txbridge-outbound-tests-service.war" (runtime-name: "txbridge-outbound-tests-service.war") > 00:54:02,258 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-service.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:54:02,329 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=OutboundTestServiceATServlet > address=http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl > implementor=org.jboss.jbossts.txbridge.tests.outbound.service.TestATServiceImpl > serviceName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService > portName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplPort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 00:54:02,329 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=OutboundTestServiceNonATServlet > address=http://localhost:8080/txbridge-outbound-tests-service/TestNonATServiceImpl > implementor=org.jboss.jbossts.txbridge.tests.outbound.service.TestNonATServiceImpl > serviceName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplService > portName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplPort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 00:54:02,350 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from class org.jboss.jbossts.txbridge.tests.outbound.service.TestATServiceImpl > 00:54:02,377 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl > 00:54:02,392 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/txbridge-outbound-tests-service.war/TestATServiceImplService.wsdl > 00:54:02,396 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplService from class org.jboss.jbossts.txbridge.tests.outbound.service.TestNonATServiceImpl > 00:54:02,399 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/txbridge-outbound-tests-service/TestNonATServiceImpl > 00:54:02,404 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/txbridge-outbound-tests-service.war/TestNonATServiceImplService.wsdl > 00:54:02,422 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceATServlet > 00:54:02,422 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceNonATServlet > 00:54:02,434 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /txbridge-outbound-tests-service > 00:54:02,492 INFO [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "txbridge-outbound-tests-service.war" (runtime-name : "txbridge-outbound-tests-service.war") > Jan 06, 2016 12:54:02 AM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > Jan 06, 2016 12:54:02 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Automatic deploying of the managed deployment with name txbridge-outbound-tests-client for the container with name jboss > 00:54:02,720 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/b3/6bdfaa5feca5ff426c038cb7f2f2fed119847f/content > 00:54:02,723 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "txbridge-outbound-tests-client.war" (runtime-name: "txbridge-outbound-tests-client.war") > 00:54:02,746 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-client.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:54:02,746 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-client.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 00:54:02,810 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /txbridge-outbound-tests-client > 00:54:02,823 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "txbridge-outbound-tests-client.war" (runtime-name : "txbridge-outbound-tests-client.war") > 00:54:03,077 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from WSDL: http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl?wsdl > 00:54:03,099 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from WSDL: http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl?wsdl > 00:55:03,344 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default task-1) Interceptor for {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService#{http://client.outbound.tests.txbridge.jbossts.jboss.org/}doNothing has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not send Message. > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > at com.sun.proxy.$Proxy137.doNothing(Unknown Source) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:140) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.doPost(TestATClient.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl: Read timed out > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > ... 39 more > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > ... 42 more > 00:55:03,349 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /txbridge-outbound-tests-client//testATClient: java.lang.RuntimeException: javax.xml.ws.WebServiceException: Could not send Message. > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:148) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.doPost(TestATClient.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: javax.xml.ws.WebServiceException: Could not send Message. > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:150) > at com.sun.proxy.$Proxy137.doNothing(Unknown Source) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:140) > ... 30 more > Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl: Read timed out > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > ... 32 more > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > ... 42 more > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Automatic undeploying of the managed deployment with name txbridge-outbound-tests-service from the container with name jboss > 00:55:03,375 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 70) WFLYUT0022: Unregistered web context: /txbridge-outbound-tests-service > 00:55:03,387 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceNonATServlet > 00:55:03,389 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceATServlet > 00:55:03,452 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment txbridge-outbound-tests-service.war (runtime-name: txbridge-outbound-tests-service.war) in 85ms > 00:55:03,469 INFO [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/9b/70e2a1644d4faf24e750f2cf3b295db924703a/content > 00:55:03,469 INFO [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0009: Undeployed "txbridge-outbound-tests-service.war" (runtime-name: "txbridge-outbound-tests-service.war") > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Automatic undeploying of the managed deployment with name txbridge-outbound-tests-client from the container with name jboss > 00:55:03,481 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Unregistered web context: /txbridge-outbound-tests-client > 00:55:03,491 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment txbridge-outbound-tests-client.war (runtime-name: txbridge-outbound-tests-client.war) in 12ms > 00:55:03,502 INFO [org.jboss.as.repository] (management-handler-thread - 6) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/b3/6bdfaa5feca5ff426c038cb7f2f2fed119847f/content > 00:55:03,502 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0009: Undeployed "txbridge-outbound-tests-client.war" (runtime-name: "txbridge-outbound-tests-client.war") > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 00:55:03,508 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0211: Suspending server with 0ms timeout. > 00:55:03,512 INFO [org.jboss.as.server] (Thread-3) WFLYSRV0220: Server shutdown has been requested. > 00:55:03,544 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-3) ARJUNA033014: OutboundBridgeRecoveryManager stopping > 00:55:03,545 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-1) ARJUNA033007: InboundBridgeRecoveryManager stopping > 00:55:03,557 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Unregistered web context: /rest-tx > 00:55:03,567 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 00:55:03,577 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: /xtstest > 00:55:03,582 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > 00:55:03,587 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 71) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory > 00:55:03,604 ERROR [org.jboss.remoting.resource] (Remoting "brandon:MANAGEMENT" task-8) Close action for Channel ID 25c56b1d (inbound) of Remoting connection 01cf11a2 to /127.0.0.1:47100 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating > at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588) > at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327) > at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138) > at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261) > at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534) > at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372) > at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437) > at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114) > at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > 00:55:03,608 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-coordinator > 00:55:03,612 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-client > 00:55:03,612 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0022: Unregistered web context: /ws-t11-client > 00:55:03,613 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-participant > 00:55:03,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0022: Unregistered web context: /ws-t11-participant > 00:55:03,613 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-c11 > 00:55:03,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0022: Unregistered web context: /ws-c11 > 00:55:03,617 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /ws-t11-coordinator > 00:55:03,617 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 00:55:03,618 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 00:55:03,620 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 00:55:03,621 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-client > 00:55:03,620 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 00:55:03,624 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-c11 > 00:55:03,634 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 00:55:03,634 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 00:55:03,635 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 00:55:03,637 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 00:55:03,637 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 00:55:03,641 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 00:55:03,643 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:55:03,643 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-participant > 00:55:03,644 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-coordinator > 00:55:03,655 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 74) Stopping XTSServiceTestRunner > 00:55:03,656 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 74) Stopped XTSServiceTestRunner > 00:55:03,657 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 75) AMQ151003: resource adaptor stopped > 00:55:03,678 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment restat-web-5.2.13.Final-SNAPSHOT.war (runtime-name: restat-web-5.2.13.Final-SNAPSHOT.war) in 159ms > 00:55:03,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0019: Host default-host stopping > 00:55:03,711 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 00:55:03,712 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 00:55:03,711 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 00:55:03,713 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 00:55:03,714 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0010: Stopping weld service for deployment xtstest.war > 00:55:03,772 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 00:55:03,787 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 00:55:03,805 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010 [7842cabe-b404-11e5-9b8e-a55e51d89294] stopped > 00:55:03,806 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending > 00:55:03,807 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 00:55:03,808 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.3.11.Final stopping > 00:55:03,827 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment xtstest.war (runtime-name: xtstest.war) in 308ms > 00:55:03,836 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.0.5.Final "Kenny" stopped in 284ms > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 15 06:14:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 15 Jan 2016 06:14:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2605) Narayana Spring integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2605: -------------------------------- Comment: was deleted (was: A comment with security level 'Red Hat Employee' was removed.) > Narayana Spring integration > --------------------------- > > Key: JBTM-2605 > URL: https://issues.jboss.org/browse/JBTM-2605 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, Documentation, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > This is a wrapper for all subtasks related with Spring integration. > As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 15 06:14:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 15 Jan 2016 06:14:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2605) Narayana Spring integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2605: -------------------------------- Comment: was deleted (was: A comment with security level 'Red Hat Employee' was removed.) > Narayana Spring integration > --------------------------- > > Key: JBTM-2605 > URL: https://issues.jboss.org/browse/JBTM-2605 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, Documentation, JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > This is a wrapper for all subtasks related with Spring integration. > As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 15 06:15:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 15 Jan 2016 06:15:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2606) Create Spring Boot starter for Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149266#comment-13149266 ] Tom Jenkinson commented on JBTM-2606: ------------------------------------- A few links: https://github.com/spring-projects/spring-boot/tree/master/spring-boot-starters http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#using-boot-starter-poms > Create Spring Boot starter for Narayana > --------------------------------------- > > Key: JBTM-2606 > URL: https://issues.jboss.org/browse/JBTM-2606 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Spring provides a bunch of Spring Boot starter artefacts in order to make integration of certain projects easier. We should investigate having one for Narayana. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 09:35:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 18 Jan 2016 09:35:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2608) org.wildfly.test.extension.rts.ParticipantTestCase failure In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2608: -------------------------------------- Summary: org.wildfly.test.extension.rts.ParticipantTestCase failure Key: JBTM-2608 URL: https://issues.jboss.org/browse/JBTM-2608 Project: JBoss Transaction Manager Issue Type: Bug Components: REST Affects Versions: 5.2.12.Final Reporter: Michael Musgrove Assignee: Gytis Trikleris http://172.17.130.4:8083/job/narayana-mac/PROFILE=MAIN,jdk=jdk8.latest,label=mac/165/ I have raised the issue against narayana (as opposed to wfly) since it's probably related to changes on our master narayana branch: Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 61.841 sec <<< FAILURE! - in org.wildfly.test.extension.rts.ParticipantTestCase testReadOnly(org.wildfly.test.extension.rts.ParticipantTestCase) Time elapsed: 60.432 sec <<< ERROR! java.lang.reflect.UndeclaredThrowableException: null at com.sun.proxy.$Proxy36.runTestMethod(Unknown Source) at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:80) at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runner.JUnitCore.run(JUnitCore.java:137) at org.junit.runner.JUnitCore.run(JUnitCore.java:115) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) Caused by: java.io.IOException: Unable to invoke invoke(), status=WAITING at org.jboss.remotingjmx.protocol.v2.ClientConnection$TheConnection.invoke(ClientConnection.java:1072) at org.jboss.as.arquillian.container.ManagementClient$MBeanConnectionProxy.invoke(ManagementClient.java:560) at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:292) at com.sun.proxy.$Proxy36.runTestMethod(Unknown Source) at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:80) at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runner.JUnitCore.run(JUnitCore.java:137) at org.junit.runner.JUnitCore.run(JUnitCore.java:115) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 18 10:32:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 18 Jan 2016 10:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2608) org.wildfly.test.extension.rts.ParticipantTestCase failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-2608. --------------------------------- Fix Version/s: WFLY-5950 Resolution: Duplicate Issue > org.wildfly.test.extension.rts.ParticipantTestCase failure > ---------------------------------------------------------- > > Key: JBTM-2608 > URL: https://issues.jboss.org/browse/JBTM-2608 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: WFLY-5950 > > > http://172.17.130.4:8083/job/narayana-mac/PROFILE=MAIN,jdk=jdk8.latest,label=mac/165/ > I have raised the issue against narayana (as opposed to wfly) since it's probably related to changes on our master narayana branch: > Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 61.841 sec <<< FAILURE! - in org.wildfly.test.extension.rts.ParticipantTestCase > testReadOnly(org.wildfly.test.extension.rts.ParticipantTestCase) Time elapsed: 60.432 sec <<< ERROR! > java.lang.reflect.UndeclaredThrowableException: null > at com.sun.proxy.$Proxy36.runTestMethod(Unknown Source) > at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:80) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.io.IOException: Unable to invoke invoke(), status=WAITING > at org.jboss.remotingjmx.protocol.v2.ClientConnection$TheConnection.invoke(ClientConnection.java:1072) > at org.jboss.as.arquillian.container.ManagementClient$MBeanConnectionProxy.invoke(ManagementClient.java:560) > at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:292) > at com.sun.proxy.$Proxy36.runTestMethod(Unknown Source) > at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:80) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:109) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136) > at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:363) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259) > at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:321) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:422) > at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at org.junit.runner.JUnitCore.run(JUnitCore.java:115) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:113) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:85) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:54) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 08:25:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 08:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2609) JDBC should be able to handle JEE errors during interfacing with a datasource in an app server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2609: -------------------------------- Summary: JDBC should be able to handle JEE errors during interfacing with a datasource in an app server (was: JDBC store needs to be able to handle JEE errors during interfacing with a datasource in an app server) > JDBC should be able to handle JEE errors during interfacing with a datasource in an app server > ---------------------------------------------------------------------------------------------- > > Key: JBTM-2609 > URL: https://issues.jboss.org/browse/JBTM-2609 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently the handling is all expected to be JSE typed exceptions like an SQLexception. It seems that in an app server a variety of other exception types can be thrown not just limited to JNDI exceptions. It has been reported that IllegalStateException can be thrown when an app server is rebooting and the datasource is not available for lookup. > Changing to handle all exceptions in JDBCImple_Driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 08:25:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 08:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2609) JDBC store needs to be able to handle JEE errors during interfacing with a datasource in an app server In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2609: ----------------------------------- Summary: JDBC store needs to be able to handle JEE errors during interfacing with a datasource in an app server Key: JBTM-2609 URL: https://issues.jboss.org/browse/JBTM-2609 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Transaction Core Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next Currently the handling is all expected to be JSE typed exceptions like an SQLexception. It seems that in an app server a variety of other exception types can be thrown not just limited to JNDI exceptions. It has been reported that IllegalStateException can be thrown when an app server is rebooting and the datasource is not available for lookup. Changing to handle all exceptions in JDBCImple_Driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 08:26:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 08:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2609) Make JDBCStore able to handle JEE errors interfacing with a datasource in an app server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2609: -------------------------------- Summary: Make JDBCStore able to handle JEE errors interfacing with a datasource in an app server (was: JDBC should be able to handle JEE errors during interfacing with a datasource in an app server) > Make JDBCStore able to handle JEE errors interfacing with a datasource in an app server > --------------------------------------------------------------------------------------- > > Key: JBTM-2609 > URL: https://issues.jboss.org/browse/JBTM-2609 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently the handling is all expected to be JSE typed exceptions like an SQLexception. It seems that in an app server a variety of other exception types can be thrown not just limited to JNDI exceptions. It has been reported that IllegalStateException can be thrown when an app server is rebooting and the datasource is not available for lookup. > Changing to handle all exceptions in JDBCImple_Driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 08:49:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 19 Jan 2016 08:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2610) BridgeWrapper.prepareVolatile() returned false in BridgeFromJTATest In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2610: ------------------------------------- Summary: BridgeWrapper.prepareVolatile() returned false in BridgeFromJTATest Key: JBTM-2610 URL: https://issues.jboss.org/browse/JBTM-2610 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator, TxBridge Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.next {code} ------------------------------------------------------------------------------- Test set: org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest ------------------------------------------------------------------------------- Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 451.462 sec <<< FAILURE! testCommit(org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest) Time elapsed: 192.767 sec <<< ERROR! javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction. at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1212) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89) at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:178) at org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest.testCommit(BridgeFromJTATest.java:97) 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:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at org.junit.runner.JUnitCore.run(JUnitCore.java:136) at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:160) at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:126) at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:90) at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: BridgeWrapper.prepareVolatile() returned false at org.jboss.jbossts.txbridge.outbound.BridgeSynchronization.beforeCompletion(BridgeSynchronization.java:62) at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:371) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:91) at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1200) ... 108 more testClientDrivenRollback(org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest) Time elapsed: 240.772 sec <<< ERROR! javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction. at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1212) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89) at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:178) at org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest.testClientDrivenRollback(BridgeFromJTATest.java:120) 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:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) 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:497) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at org.junit.runner.JUnitCore.run(JUnitCore.java:136) at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:160) at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:126) at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:90) at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: BridgeWrapper.prepareVolatile() returned false at org.jboss.jbossts.txbridge.outbound.BridgeSynchronization.beforeCompletion(BridgeSynchronization.java:62) at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:371) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:91) at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1200) ... 108 more {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 09:36:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 09:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2611) Make consistent usage of surefire version in quickstart poms In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2611: ----------------------------------- Summary: Make consistent usage of surefire version in quickstart poms Key: JBTM-2611 URL: https://issues.jboss.org/browse/JBTM-2611 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Demonstrator Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Minor Fix For: 5.next Some of the quickstarts use 2.4.3 of surefire plugin (amongst others used by other quickstarts). Lets standardise these on the current version. The reason this change is required is because some times the quickstart runs fail on lancel (probably something about this nodes .m2) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 09:40:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 09:40:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2611) Make consistent usage of surefire version in quickstart poms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #158 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Make consistent usage of surefire version in quickstart poms > ------------------------------------------------------------- > > Key: JBTM-2611 > URL: https://issues.jboss.org/browse/JBTM-2611 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Some of the quickstarts use 2.4.3 of surefire plugin (amongst others used by other quickstarts). Lets standardise these on the current version. The reason this change is required is because some times the quickstart runs fail on lancel (probably something about this nodes .m2) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 12:51:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 12:51:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2115) Not all classes are under code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2115: -------------------------------- Priority: Minor (was: Major) > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 12:51:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 12:51:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2571) Enable code coverage for XTS crash recovery tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2571: -------------------------------- Fix Version/s: 5.next > Enable code coverage for XTS crash recovery tests > ------------------------------------------------- > > Key: JBTM-2571 > URL: https://issues.jboss.org/browse/JBTM-2571 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Code coverage data is not collected during the XTS crash recovery tests execution. Currently this seems to be blocked by [1], [2], and [3]. > [1] https://community.jboss.org/message/817252 > [2] https://issues.jboss.org/browse/ARQ-1014 > [3] https://issues.jboss.org/browse/ARQ-918 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 12:51:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 12:51:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2571) Enable code coverage for XTS crash recovery tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2571: -------------------------------- Priority: Minor (was: Major) > Enable code coverage for XTS crash recovery tests > ------------------------------------------------- > > Key: JBTM-2571 > URL: https://issues.jboss.org/browse/JBTM-2571 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Code coverage data is not collected during the XTS crash recovery tests execution. Currently this seems to be blocked by [1], [2], and [3]. > [1] https://community.jboss.org/message/817252 > [2] https://issues.jboss.org/browse/ARQ-1014 > [3] https://issues.jboss.org/browse/ARQ-918 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 12:52:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 12:52:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-741: ------------------------------- Priority: Minor (was: Major) > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Priority: Minor > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 12:53:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 12:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-741: ------------------------------- Fix Version/s: 5.later > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 12:53:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 12:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2553: -------------------------------- Fix Version/s: 5.next (was: 5.later) > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 12:53:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 12:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2553: -------------------------------- Priority: Minor (was: Major) > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 12:53:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 12:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1804: -------------------------------- Priority: Minor (was: Major) > JTS remote tests not run and no code coverage > --------------------------------------------- > > Key: JBTM-1804 > URL: https://issues.jboss.org/browse/JBTM-1804 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build. > It would then be beneficial to have them instrumented by emma to get code coverage. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 19 12:53:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 Jan 2016 12:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2305) Incomplete tooling documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2305: -------------------------------- Priority: Minor (was: Major) > Incomplete tooling documentation > -------------------------------- > > Key: JBTM-2305 > URL: https://issues.jboss.org/browse/JBTM-2305 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > For tooling the docs defer to the wildfly/EAP cli for "5.1.1. Browse and Manage Transactions Using an Application Server". We had some text in the README explaining how to view the tooling MBeans but the equivalent needs to be added to the development_guide too for use with standalone narayana. > In addition the docs need to explain how to extend the tooling for new abstract records (basically the user needs to create a JMX MBean for the new type and register it with the ObjStoreBrowser). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 20 05:14:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 20 Jan 2016 05:14:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2611) Make consistent usage of surefire version in quickstart poms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2611: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Make consistent usage of surefire version in quickstart poms > ------------------------------------------------------------- > > Key: JBTM-2611 > URL: https://issues.jboss.org/browse/JBTM-2611 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > Some of the quickstarts use 2.4.3 of surefire plugin (amongst others used by other quickstarts). Lets standardise these on the current version. The reason this change is required is because some times the quickstart runs fail on lancel (probably something about this nodes .m2) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 20 06:30:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 20 Jan 2016 06:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2517) Update the Narayana Release Process doc to include performance figures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2517. ------------------------------------ Resolution: Done The benchmark results and bar chart are now uploaded to the artefact repo (https://github.com/jbosstm/artifacts) with a suitable git comment, for example: bq. Generated on host haverstraw (Tue 19 Jan 11:09:06 GMT 2016) using tag 5.2.12.Final > Update the Narayana Release Process doc to include performance figures > ---------------------------------------------------------------------- > > Key: JBTM-2517 > URL: https://issues.jboss.org/browse/JBTM-2517 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing, Release Process > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > Include a description in the NRP document of how to blog about performance figures when releasing a new version of Narayana -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 21 07:07:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 21 Jan 2016 07:07:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2609) Make JDBCStore able to handle JEE errors interfacing with a datasource in an app server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #969 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Make JDBCStore able to handle JEE errors interfacing with a datasource in an app server > --------------------------------------------------------------------------------------- > > Key: JBTM-2609 > URL: https://issues.jboss.org/browse/JBTM-2609 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently the handling is all expected to be JSE typed exceptions like an SQLexception. It seems that in an app server a variety of other exception types can be thrown not just limited to JNDI exceptions. It has been reported that IllegalStateException can be thrown when an app server is rebooting and the datasource is not available for lookup. > Changing to handle all exceptions in JDBCImple_Driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 22 05:24:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 22 Jan 2016 05:24:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2612) Deploy jdbc module to the Maven repository In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2612: ------------------------------------- Summary: Deploy jdbc module to the Maven repository Key: JBTM-2612 URL: https://issues.jboss.org/browse/JBTM-2612 Project: JBoss Transaction Manager Issue Type: Task Components: JTA Reporter: Gytis Trikleris Fix For: 5.next Currently jdbc module is not available in Maven repository. Therefore, jta uber jar is needed to get access to those classes. If we want to discourage uber jar usage, we should provide jdbc module through Maven. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 22 05:50:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 22 Jan 2016 05:50:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2612) Deploy jdbc module to the Maven repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2612: ----------------------------------- Assignee: Tom Jenkinson > Deploy jdbc module to the Maven repository > ------------------------------------------ > > Key: JBTM-2612 > URL: https://issues.jboss.org/browse/JBTM-2612 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently jdbc module is not available in Maven repository. Therefore, jta uber jar is needed to get access to those classes. If we want to discourage uber jar usage, we should provide jdbc module through Maven. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 22 05:51:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 22 Jan 2016 05:51:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2612) Deploy jdbc module to the Maven repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2612: -------------------------------- Workaround is to use narayana-jta jar for now > Deploy jdbc module to the Maven repository > ------------------------------------------ > > Key: JBTM-2612 > URL: https://issues.jboss.org/browse/JBTM-2612 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently jdbc module is not available in Maven repository. Therefore, jta uber jar is needed to get access to those classes. If we want to discourage uber jar usage, we should provide jdbc module through Maven. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 22 06:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 22 Jan 2016 06:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2511) Benchmark failure testing REST-AT with undertow In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152363#comment-13152363 ] Tom Jenkinson commented on JBTM-2511: ------------------------------------- Renamed the job to be consistent with other JBTM repeaters: http://albany.eng.hst.ams2.redhat.com/view/Narayana-JBTM/job/JBTM-2511/ > Benchmark failure testing REST-AT with undertow > ----------------------------------------------- > > Key: JBTM-2511 > URL: https://issues.jboss.org/browse/JBTM-2511 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing, REST > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > The REST-AT benchmark tests are failing: > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-benchmarks/37/ > and the failure is: > bq. Caused by: javax.ws.rs.ServiceUnavailableException: HTTP 503 Service Unavailable > whilst sending a request to a JAX-RS service. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 22 11:33:00 2016 From: issues at jboss.org (Mark Little (JIRA)) Date: Fri, 22 Jan 2016 11:33:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2609) Make JDBCStore able to handle Java EE errors interfacing with a datasource in an app server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little updated JBTM-2609: ------------------------------ Summary: Make JDBCStore able to handle Java EE errors interfacing with a datasource in an app server (was: Make JDBCStore able to handle JEE errors interfacing with a datasource in an app server) > Make JDBCStore able to handle Java EE errors interfacing with a datasource in an app server > ------------------------------------------------------------------------------------------- > > Key: JBTM-2609 > URL: https://issues.jboss.org/browse/JBTM-2609 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently the handling is all expected to be JSE typed exceptions like an SQLexception. It seems that in an app server a variety of other exception types can be thrown not just limited to JNDI exceptions. It has been reported that IllegalStateException can be thrown when an app server is rebooting and the datasource is not available for lookup. > Changing to handle all exceptions in JDBCImple_Driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 04:30:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 25 Jan 2016 04:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2602) QA suite failure: TestGroup_txcore_lockrecord In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2602: -------------------------------- Summary: QA suite failure: TestGroup_txcore_lockrecord (was: QA test suite failure on DB2: TestGroup_txcore_lockrecord) > QA suite failure: TestGroup_txcore_lockrecord > --------------------------------------------- > > Key: JBTM-2602 > URL: https://issues.jboss.org/browse/JBTM-2602 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 04:31:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 25 Jan 2016 04:31:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2439) XATMI CSTest failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2439. ------------------------------- Fix Version/s: 5.2.12.Final Assignee: Tom Jenkinson Resolution: Out of Date Has been out of date since at least the upgrade to Artemis in WFLY > XATMI CSTest failed > ------------------- > > Key: JBTM-2439 > URL: https://issues.jboss.org/browse/JBTM-2439 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.2.12.Final > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/863 > {code} > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest > 20:00:30,081 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:30,372 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:30,597 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:00:41,182 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:41,531 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:41,788 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:00:44,655 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:55163) Caught an exception: null: java.lang.NullPointerException > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:103) > at java.lang.Thread.run(Thread.java:744) > 20:00:54,478 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:00:54,749 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:00:55,057 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 123) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:05,617 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:01:05,865 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:01:06,103 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:16,623 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:01:16,900 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:01:17,169 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 125) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:01:38,604 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) undeploy service pending for .testsui1 as consumer count is 0, will check again in 30000ms > 20:02:08,542 WARN [org.jboss.as.ejb3] (EJB default - 3) WFLYEJB0043: A previous execution of timer [id=ec057768-85a2-4e35-ac04-cebbf53ce28e timedObjectId=blacktie-admin-services-ear-5.1.2.Final-SNAPSHOT.blacktie-admin-services-5.1.2.Final-SNAPSHOT.QueueReaperBean auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl at 3aff5ed3 initialExpiration=Wed Jun 17 18:46:38 BST 2015 intervalDuration(in milli sec)=30000 nextExpiration=Wed Jun 17 20:02:08 BST 2015 timerState=IN_TIMEOUT info=queue reaper] is still in progress, skipping this overlapping scheduled execution at: Wed Jun 17 20:02:08 BST 2015. > 20:02:08,781 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 1) undeploy service .testsui1 for consumer is 0 > 20:02:23,382 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d has 1 heuristic participant(s)! > 20:02:23,382 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a42%3a173398/terminate > 20:02:23,382 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 5ec536b5 > 20:02:23,550 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 has 1 heuristic participant(s)! > 20:02:23,551 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a35%3a424555/terminate > 20:02:23,552 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 7642baf0 > 20:02:23,625 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 has 1 heuristic participant(s)! > 20:02:23,626 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a36%3a409865/terminate > 20:02:23,627 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2ecad1c6 > 20:02:23,701 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a57%3a125401/terminate > 20:02:23,743 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 has 1 heuristic participant(s)! > 20:02:23,744 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a43%3a212555/terminate > 20:02:23,745 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2684d6dd > 20:02:57,766 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-36 (HornetQ-client-global-threads-1622216728)) call server testsui id 0 failed with 13: org.jboss.narayana.blacktie.jatmibroker.xatmi.ConnectionException: tperrno: 13 reason: Did not receive a message > at org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.SocketReceiverImpl.receive(SocketReceiverImpl.java:139) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.receive(ConnectionImpl.java:533) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:183) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.callAdminService(AdministrationProxy.java:75) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.shutdown(AdministrationProxy.java:350) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.shutdown(BlacktieAdminServiceXATMI.java:346) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.tpservice(BlacktieAdminServiceXATMI.java:132) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$view2.onMessage(Unknown Source) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) > at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$endpoint2.onMessage(Unknown Source) > at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:321) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1116) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:56) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1251) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > 20:02:57,814 ERROR [org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.stomp.StompSenderImpl] (Thread-36 (HornetQ-client-global-threads-1622216728)) queue/BTR_.testsui1 -- service jboss.naming.context.java.queue."BTR_.testsui1" > 20:02:57,815 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-36 (HornetQ-client-global-threads-1622216728)) call server testsui id 0 failed with 6: org.jboss.narayana.blacktie.jatmibroker.xatmi.ConnectionException: tperrno: 6 reason: queue/BTR_.testsui1 -- service jboss.naming.context.java.queue."BTR_.testsui1" > at org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.stomp.StompSenderImpl.send(StompSenderImpl.java:144) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpacall(ConnectionImpl.java:260) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:181) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.callAdminService(AdministrationProxy.java:75) > at org.jboss.narayana.blacktie.administration.core.AdministrationProxy.shutdown(AdministrationProxy.java:354) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.shutdown(BlacktieAdminServiceXATMI.java:346) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI.tpservice(BlacktieAdminServiceXATMI.java:132) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$view2.onMessage(Unknown Source) > at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139) > at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73) > at org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI$$$endpoint2.onMessage(Unknown Source) > at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:321) > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1116) > at org.hornetq.core.client.impl.ClientConsumerImpl.access$500(ClientConsumerImpl.java:56) > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1251) > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > 20:02:57,852 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 127) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:05,744 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:05,985 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:06,274 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:16,874 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:17,135 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:17,436 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:40,042 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:40,430 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:40,688 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:03:51,251 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:03:51,561 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:03:51,815 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:02,497 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:02,745 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:02,980 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:13,462 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:13,745 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:13,985 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 129) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:24,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:24,846 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:25,216 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:33,824 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d has 1 heuristic participant(s)! > 20:04:33,825 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a42%3a173398/terminate > 20:04:33,825 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:9d restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 32f599dc > 20:04:33,910 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 has 1 heuristic participant(s)! > 20:04:33,911 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a35%3a424555/terminate > 20:04:33,911 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:91 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 4a493aa5 > 20:04:33,989 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 has 1 heuristic participant(s)! > 20:04:33,990 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a36%3a409865/terminate > 20:04:33,990 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:94 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 4afb2f0f > 20:04:34,065 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a47%3a57%3a125401/terminate > 20:04:34,098 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 has 1 heuristic participant(s)! > 20:04:34,099 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a43%3a212555/terminate > 20:04:34,100 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffff0a27a818:-3b8ac52f:5581b0d2:a0 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord at 2d1d86a > 20:04:35,818 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:36,102 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:36,371 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:46,960 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:47,211 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:47,475 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > 20:04:58,025 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 20:04:58,376 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 20:04:58,624 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 128) HQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 279.072 sec <<< FAILURE! > test_211(org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest) Time elapsed: 101.173 sec <<< FAILURE! > junit.framework.AssertionFailedError: null > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertTrue(Assert.java:31) > at junit.framework.TestCase.assertTrue(TestCase.java:201) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.CSControl.runTest(CSControl.java:153) > at org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest.test_211(CSTest.java:27) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 04:35:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 25 Jan 2016 04:35:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2610) BridgeWrapper.prepareVolatile() returned false in BridgeFromJTATest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152850#comment-13152850 ] Tom Jenkinson commented on JBTM-2610: ------------------------------------- Do we need some more logging here and then close this as incomplete description? > BridgeWrapper.prepareVolatile() returned false in BridgeFromJTATest > ------------------------------------------------------------------- > > Key: JBTM-2610 > URL: https://issues.jboss.org/browse/JBTM-2610 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator, TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 451.462 sec <<< FAILURE! > testCommit(org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest) Time elapsed: 192.767 sec <<< ERROR! > javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction. > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1212) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89) > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:178) > at org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest.testCommit(BridgeFromJTATest.java:97) > 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:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at org.junit.runner.JUnitCore.run(JUnitCore.java:136) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:160) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:126) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:90) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.RuntimeException: BridgeWrapper.prepareVolatile() returned false > at org.jboss.jbossts.txbridge.outbound.BridgeSynchronization.beforeCompletion(BridgeSynchronization.java:62) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:371) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:91) > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1200) > ... 108 more > testClientDrivenRollback(org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest) Time elapsed: 240.772 sec <<< ERROR! > javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction. > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1212) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89) > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:178) > at org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest.testClientDrivenRollback(BridgeFromJTATest.java:120) > 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:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at org.junit.runner.JUnitCore.run(JUnitCore.java:136) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:160) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:126) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:90) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.RuntimeException: BridgeWrapper.prepareVolatile() returned false > at org.jboss.jbossts.txbridge.outbound.BridgeSynchronization.beforeCompletion(BridgeSynchronization.java:62) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:371) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:91) > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1200) > ... 108 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 04:36:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 25 Jan 2016 04:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2196) QA suite failure: CrashRecovery05_2_Test034 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152852#comment-13152852 ] Tom Jenkinson commented on JBTM-2196: ------------------------------------- This last failed in 2014 - out of date? > QA suite failure: CrashRecovery05_2_Test034 > ------------------------------------------- > > Key: JBTM-2196 > URL: https://issues.jboss.org/browse/JBTM-2196 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS, Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > Attachments: CrashRecovery05_2_Test034.tar > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/550/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 04:36:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 25 Jan 2016 04:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2252) QA suite failure: CrashRecovery05_2_Test030 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152853#comment-13152853 ] Tom Jenkinson commented on JBTM-2252: ------------------------------------- This last failed in 2014 - out of date? > QA suite failure: CrashRecovery05_2_Test030 > -------------------------------------------- > > Key: JBTM-2252 > URL: https://issues.jboss.org/browse/JBTM-2252 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS, Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > Attachments: CrashRecovery05_2_Test030.tar > > > http://albany.eng.hst.ams2.redhat.com/job/narayana/638/ -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 04:36:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 25 Jan 2016 04:36:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152855#comment-13152855 ] Tom Jenkinson commented on JBTM-2433: ------------------------------------- Shouldn't we link this to the race condition Jira? > TransactionRolledBackException in MultiCloseTest > ------------------------------------------------ > > Key: JBTM-2433 > URL: https://issues.jboss.org/browse/JBTM-2433 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt > > > It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion. > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! > testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 04:53:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 25 Jan 2016 04:53:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2610) BridgeWrapper.prepareVolatile() returned false in BridgeFromJTATest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152883#comment-13152883 ] Gytis Trikleris commented on JBTM-2610: --------------------------------------- I haven't looked at this issue yet. But that might be a good option. > BridgeWrapper.prepareVolatile() returned false in BridgeFromJTATest > ------------------------------------------------------------------- > > Key: JBTM-2610 > URL: https://issues.jboss.org/browse/JBTM-2610 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator, TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 451.462 sec <<< FAILURE! > testCommit(org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest) Time elapsed: 192.767 sec <<< ERROR! > javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction. > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1212) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89) > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:178) > at org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest.testCommit(BridgeFromJTATest.java:97) > 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:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at org.junit.runner.JUnitCore.run(JUnitCore.java:136) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:160) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:126) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:90) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.RuntimeException: BridgeWrapper.prepareVolatile() returned false > at org.jboss.jbossts.txbridge.outbound.BridgeSynchronization.beforeCompletion(BridgeSynchronization.java:62) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:371) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:91) > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1200) > ... 108 more > testClientDrivenRollback(org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest) Time elapsed: 240.772 sec <<< ERROR! > javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction. > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1212) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89) > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:178) > at org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest.testClientDrivenRollback(BridgeFromJTATest.java:120) > 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:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at org.junit.runner.JUnitCore.run(JUnitCore.java:136) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:160) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:126) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:90) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.RuntimeException: BridgeWrapper.prepareVolatile() returned false > at org.jboss.jbossts.txbridge.outbound.BridgeSynchronization.beforeCompletion(BridgeSynchronization.java:62) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:371) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:91) > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1200) > ... 108 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 06:18:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 25 Jan 2016 06:18:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2613) BABridgedTest failure (caused by WebServiceException: Could not send Message) In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2613: -------------------------------------- Summary: BABridgedTest failure (caused by WebServiceException: Could not send Message) Key: JBTM-2613 URL: https://issues.jboss.org/browse/JBTM-2613 Project: JBoss Transaction Manager Issue Type: Bug Components: TxBridge Affects Versions: 5.2.12.Final Reporter: Michael Musgrove Assignee: Gytis Trikleris job number was: http://172.17.130.4:8083/job/narayana-dualstack/80 ------------------------------------------------------------------------------- Test set: org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest ------------------------------------------------------------------------------- Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 72.917 sec <<< FAILURE! testClose(org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest) Time elapsed: 60.65 sec <<< ERROR! javax.xml.ws.WebServiceException: Could not send Message. at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:170) at java.net.SocketInputStream.read(SocketInputStream.java:141) at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) at java.io.BufferedInputStream.read(BufferedInputStream.java:345) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) at com.sun.proxy.$Proxy169.reset(Unknown Source) at org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest.teardownTest(BABridgedTest.java:97) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 06:18:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 25 Jan 2016 06:18:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2613) BABridgedTest failure (caused by WebServiceException: Could not send Message) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2613: ----------------------------------- Attachment: org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest.txt surefire output > BABridgedTest failure (caused by WebServiceException: Could not send Message) > ----------------------------------------------------------------------------- > > Key: JBTM-2613 > URL: https://issues.jboss.org/browse/JBTM-2613 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Attachments: org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest.txt > > > job number was: http://172.17.130.4:8083/job/narayana-dualstack/80 > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 72.917 sec <<< FAILURE! > testClose(org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest) Time elapsed: 60.65 sec <<< ERROR! > javax.xml.ws.WebServiceException: Could not send Message. > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > at com.sun.proxy.$Proxy169.reset(Unknown Source) > at org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest.teardownTest(BABridgedTest.java:97) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 06:34:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 25 Jan 2016 06:34:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1820) Integrate with Camel to support XA Transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1820: -------------------------------- Priority: Major (was: Optional) > Integrate with Camel to support XA Transaction > ---------------------------------------------- > > Key: JBTM-1820 > URL: https://issues.jboss.org/browse/JBTM-1820 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.later > > > From Ning Jiang (njiang at redhat.com) > {noformat} > Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1]. > As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer. > Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer. > [1]http://camel.apache.org/transactional-client.html > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 06:37:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 25 Jan 2016 06:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1820) Integrate with Camel to support XA Transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152969#comment-13152969 ] Tom Jenkinson commented on JBTM-1820: ------------------------------------- Lets not include Spring in this if possible and keep that in JBTM-855 so we show the baseline configs for both. > Integrate with Camel to support XA Transaction > ---------------------------------------------- > > Key: JBTM-1820 > URL: https://issues.jboss.org/browse/JBTM-1820 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.later > > > From Ning Jiang (njiang at redhat.com) > {noformat} > Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1]. > As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer. > Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer. > [1]http://camel.apache.org/transactional-client.html > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 06:38:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 25 Jan 2016 06:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1820) Integrate with Camel to support XA Transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152971#comment-13152971 ] Tom Jenkinson commented on JBTM-1820: ------------------------------------- Please can we create a forum topic to discuss this and to help define the scope of the work and check that it is something our community would need. > Integrate with Camel to support XA Transaction > ---------------------------------------------- > > Key: JBTM-1820 > URL: https://issues.jboss.org/browse/JBTM-1820 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.later > > > From Ning Jiang (njiang at redhat.com) > {noformat} > Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1]. > As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer. > Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer. > [1]http://camel.apache.org/transactional-client.html > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jan 25 10:47:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 25 Jan 2016 10:47:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2609) Make JDBCStore able to handle Java EE errors interfacing with a datasource in an app server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2609: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Make JDBCStore able to handle Java EE errors interfacing with a datasource in an app server > ------------------------------------------------------------------------------------------- > > Key: JBTM-2609 > URL: https://issues.jboss.org/browse/JBTM-2609 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently the handling is all expected to be JSE typed exceptions like an SQLexception. It seems that in an app server a variety of other exception types can be thrown not just limited to JNDI exceptions. It has been reported that IllegalStateException can be thrown when an app server is rebooting and the datasource is not available for lookup. > Changing to handle all exceptions in JDBCImple_Driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 26 04:09:00 2016 From: issues at jboss.org (Jive JIRA Integration (JIRA)) Date: Tue, 26 Jan 2016 04:09:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1820) Integrate with Camel to support XA Transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jive JIRA Integration updated JBTM-1820: ---------------------------------------- Forum Reference: https://developer.jboss.org/message/949549#949549 > Integrate with Camel to support XA Transaction > ---------------------------------------------- > > Key: JBTM-1820 > URL: https://issues.jboss.org/browse/JBTM-1820 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.later > > > From Ning Jiang (njiang at redhat.com) > {noformat} > Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1]. > As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer. > Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer. > [1]http://camel.apache.org/transactional-client.html > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 26 07:25:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 26 Jan 2016 07:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2614: -------------------------------------- Summary: JCA TransactionImporter should be thread safe Key: JBTM-2614 URL: https://issues.jboss.org/browse/JBTM-2614 Project: JBoss Transaction Manager Issue Type: Bug Components: JCA Affects Versions: 5.2.12.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: T1: call importTransaction for XID1 T2: call importTransaction for XID1 T1: getImportedTransaction returns null T2: getImportedTransaction returns null T1: create new transaction, add to map T2: create new transaction, add to map (overwriting T1's) There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 26 08:54:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 26 Jan 2016 08:54:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153768#comment-13153768 ] Tom Jenkinson commented on JBTM-2614: ------------------------------------- Is the unit test the one in the PR? > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 26 11:24:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 26 Jan 2016 11:24:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2615) Exclude org.omg.CORBA classes from narayana-jts-idlj uber jar In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2615: ----------------------------------- Summary: Exclude org.omg.CORBA classes from narayana-jts-idlj uber jar Key: JBTM-2615 URL: https://issues.jboss.org/browse/JBTM-2615 Project: JBoss Transaction Manager Issue Type: Task Components: Build System Affects Versions: 5.2.12.Final Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next Looks to be due to a new dependency not excluded from the uber jar -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jan 26 11:40:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 26 Jan 2016 11:40:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2615) Exclude org.omg.CORBA classes from narayana-jts-idlj uber jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #971 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Exclude org.omg.CORBA classes from narayana-jts-idlj uber jar > ------------------------------------------------------------- > > Key: JBTM-2615 > URL: https://issues.jboss.org/browse/JBTM-2615 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.2.12.Final > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Looks to be due to a new dependency not excluded from the uber jar -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 05:59:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 27 Jan 2016 05:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2615) Exclude org.omg.CORBA classes from narayana-jts-idlj uber jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2615: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Exclude org.omg.CORBA classes from narayana-jts-idlj uber jar > ------------------------------------------------------------- > > Key: JBTM-2615 > URL: https://issues.jboss.org/browse/JBTM-2615 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.2.12.Final > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Looks to be due to a new dependency not excluded from the uber jar -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 06:06:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 27 Jan 2016 06:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2612) Deploy jdbc module to the Maven repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #972 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Deploy jdbc module to the Maven repository > ------------------------------------------ > > Key: JBTM-2612 > URL: https://issues.jboss.org/browse/JBTM-2612 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently jdbc module is not available in Maven repository. Therefore, jta uber jar is needed to get access to those classes. If we want to discourage uber jar usage, we should provide jdbc module through Maven. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jan 27 15:26:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 27 Jan 2016 15:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2612) Deploy jdbc module to the Maven repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2612: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Deploy jdbc module to the Maven repository > ------------------------------------------ > > Key: JBTM-2612 > URL: https://issues.jboss.org/browse/JBTM-2612 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently jdbc module is not available in Maven repository. Therefore, jta uber jar is needed to get access to those classes. If we want to discourage uber jar usage, we should provide jdbc module through Maven. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 28 10:25:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 28 Jan 2016 10:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155932#comment-13155932 ] Michael Musgrove commented on JBTM-2614: ---------------------------------------- [~tomjenkinson] yes, I added two unit tests one for JTA the other for JTS > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 28 10:25:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 28 Jan 2016 10:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2614: ----------------------------------- Status: Pull Request Sent (was: Open) > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jan 28 10:26:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 28 Jan 2016 10:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2614: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 04:23:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 04:23:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2605) Narayana Spring integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2605 started by Tom Jenkinson. ------------------------------------------- > Narayana Spring integration > --------------------------- > > Key: JBTM-2605 > URL: https://issues.jboss.org/browse/JBTM-2605 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, Documentation, JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > This is a wrapper for all subtasks related with Spring integration. > As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 04:23:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 04:23:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2606) Create Spring Boot starter for Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2606 started by Tom Jenkinson. ------------------------------------------- > Create Spring Boot starter for Narayana > --------------------------------------- > > Key: JBTM-2606 > URL: https://issues.jboss.org/browse/JBTM-2606 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > Spring provides a bunch of Spring Boot starter artefacts in order to make integration of certain projects easier. We should investigate having one for Narayana. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 04:23:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 04:23:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2580) Create a Narayana troubleshooting guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2580 started by Tom Jenkinson. ------------------------------------------- > Create a Narayana troubleshooting guide > --------------------------------------- > > Key: JBTM-2580 > URL: https://issues.jboss.org/browse/JBTM-2580 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > This information may already exist but is possibly fragmented. This issue is to record the fact that we need to collate this. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 04:25:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 04:25:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2606) Create Spring Boot starter for Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2606: ----------------------------------- Assignee: Gytis Trikleris (was: Tom Jenkinson) > Create Spring Boot starter for Narayana > --------------------------------------- > > Key: JBTM-2606 > URL: https://issues.jboss.org/browse/JBTM-2606 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Spring provides a bunch of Spring Boot starter artefacts in order to make integration of certain projects easier. We should investigate having one for Narayana. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 04:26:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 04:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2580) Create a Narayana troubleshooting guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2580: ----------------------------------- Assignee: Amos Feng (was: Tom Jenkinson) > Create a Narayana troubleshooting guide > --------------------------------------- > > Key: JBTM-2580 > URL: https://issues.jboss.org/browse/JBTM-2580 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > This information may already exist but is possibly fragmented. This issue is to record the fact that we need to collate this. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:44:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2615) Exclude org.omg.CORBA classes from narayana-jts-idlj uber jar In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2615. ------------------------------- > Exclude org.omg.CORBA classes from narayana-jts-idlj uber jar > ------------------------------------------------------------- > > Key: JBTM-2615 > URL: https://issues.jboss.org/browse/JBTM-2615 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.2.12.Final > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.13.Final > > > Looks to be due to a new dependency not excluded from the uber jar -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:44:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2614. ------------------------------- > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.13.Final > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2612) Deploy jdbc module to the Maven repository In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2612. ------------------------------- > Deploy jdbc module to the Maven repository > ------------------------------------------ > > Key: JBTM-2612 > URL: https://issues.jboss.org/browse/JBTM-2612 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.2.13.Final > > > Currently jdbc module is not available in Maven repository. Therefore, jta uber jar is needed to get access to those classes. If we want to discourage uber jar usage, we should provide jdbc module through Maven. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2611) Make consistent usage of surefire version in quickstart poms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2611. ------------------------------- > Make consistent usage of surefire version in quickstart poms > ------------------------------------------------------------- > > Key: JBTM-2611 > URL: https://issues.jboss.org/browse/JBTM-2611 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.2.13.Final > > > Some of the quickstarts use 2.4.3 of surefire plugin (amongst others used by other quickstarts). Lets standardise these on the current version. The reason this change is required is because some times the quickstart runs fail on lancel (probably something about this nodes .m2) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2609) Make JDBCStore able to handle Java EE errors interfacing with a datasource in an app server In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2609. ------------------------------- > Make JDBCStore able to handle Java EE errors interfacing with a datasource in an app server > ------------------------------------------------------------------------------------------- > > Key: JBTM-2609 > URL: https://issues.jboss.org/browse/JBTM-2609 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.2.13.Final > > > Currently the handling is all expected to be JSE typed exceptions like an SQLexception. It seems that in an app server a variety of other exception types can be thrown not just limited to JNDI exceptions. It has been reported that IllegalStateException can be thrown when an app server is rebooting and the datasource is not available for lookup. > Changing to handle all exceptions in JDBCImple_Driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2607) Slight docs issue on wording of heuristic outcomes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2607. ------------------------------- > Slight docs issue on wording of heuristic outcomes > -------------------------------------------------- > > Key: JBTM-2607 > URL: https://issues.jboss.org/browse/JBTM-2607 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.2.13.Final > > > The text makes it sound like heuristic rollback can be achieved from only a subset of resources rolling back. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2604) Use servlet protocol in xts arquillian tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2604. ------------------------------- > Use servlet protocol in xts arquillian tests > -------------------------------------------- > > Key: JBTM-2604 > URL: https://issues.jboss.org/browse/JBTM-2604 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.2.13.Final > > > https://issues.jboss.org/browse/WFLY-5949 was caused by using jmx protocol instead of servlet in arquillian tests. Therefore, to make sure this doesn't happen in other tests, we should set servlet as a default protocol in all arquillian tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2517) Update the Narayana Release Process doc to include performance figures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2517. ------------------------------- > Update the Narayana Release Process doc to include performance figures > ---------------------------------------------------------------------- > > Key: JBTM-2517 > URL: https://issues.jboss.org/browse/JBTM-2517 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing, Release Process > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.13.Final > > > Include a description in the NRP document of how to blog about performance figures when releasing a new version of Narayana -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2610) BridgeWrapper.prepareVolatile() returned false in BridgeFromJTATest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2610: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > BridgeWrapper.prepareVolatile() returned false in BridgeFromJTATest > ------------------------------------------------------------------- > > Key: JBTM-2610 > URL: https://issues.jboss.org/browse/JBTM-2610 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator, TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 451.462 sec <<< FAILURE! > testCommit(org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest) Time elapsed: 192.767 sec <<< ERROR! > javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction. > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1212) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89) > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:178) > at org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest.testCommit(BridgeFromJTATest.java:97) > 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:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at org.junit.runner.JUnitCore.run(JUnitCore.java:136) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:160) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:126) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:90) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.RuntimeException: BridgeWrapper.prepareVolatile() returned false > at org.jboss.jbossts.txbridge.outbound.BridgeSynchronization.beforeCompletion(BridgeSynchronization.java:62) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:371) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:91) > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1200) > ... 108 more > testClientDrivenRollback(org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest) Time elapsed: 240.772 sec <<< ERROR! > javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction. > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1212) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89) > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:178) > at org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest.testClientDrivenRollback(BridgeFromJTATest.java:120) > 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:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > 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:497) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runner.JUnitCore.run(JUnitCore.java:157) > at org.junit.runner.JUnitCore.run(JUnitCore.java:136) > at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:65) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.executeTest(ServletTestRunner.java:160) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.execute(ServletTestRunner.java:126) > at org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner.doGet(ServletTestRunner.java:90) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.RuntimeException: BridgeWrapper.prepareVolatile() returned false > at org.jboss.jbossts.txbridge.outbound.BridgeSynchronization.beforeCompletion(BridgeSynchronization.java:62) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:371) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:91) > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1200) > ... 108 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2606) Create Spring Boot starter for Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2606: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Create Spring Boot starter for Narayana > --------------------------------------- > > Key: JBTM-2606 > URL: https://issues.jboss.org/browse/JBTM-2606 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Spring provides a bunch of Spring Boot starter artefacts in order to make integration of certain projects easier. We should investigate having one for Narayana. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2605) Narayana Spring integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2605: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Narayana Spring integration > --------------------------- > > Key: JBTM-2605 > URL: https://issues.jboss.org/browse/JBTM-2605 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, Documentation, JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Fix For: 5.next > > > This is a wrapper for all subtasks related with Spring integration. > As per Tom's request we should improve Narayana integration with Spring and Spring Boot. Also, provide documentation and quickstarts for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2603) Socket read timed out in EnabledContextPropagationTests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2603: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Socket read timed out in EnabledContextPropagationTests > ------------------------------------------------------- > > Key: JBTM-2603 > URL: https://issues.jboss.org/browse/JBTM-2603 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Test output: > {code} > testNoTransactionWithDisabledJTAOverWSATFeature(org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests) Time elapsed: 76.255 sec <<< ERROR! > org.apache.http.client.HttpResponseException: Internal Server Error > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:68) > at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:54) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1070) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1044) > at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1035) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.makeRequest(EnabledContextPropagationTests.java:377) > at org.jboss.jbossts.txbridge.tests.outbound.junit.EnabledContextPropagationTests.testNoTransactionWithDisabledJTAOverWSATFeature(EnabledContextPropagationTests.java:256) > {code} > Server log: > {code} > [0mJan 06, 2016 12:53:47 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Manual starting of a server instance > Jan 06, 2016 12:53:47 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > Jan 06, 2016 12:53:47 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.8.0_60/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -Djava.net.preferIPv4Stack=true, -Djava.awt.headless=true, -Djboss.modules.system.pkgs=org.jboss.byteman, -server, -Xmx1024m, -XX:MaxPermSize=512m, -Dorg.jboss.byteman.debug=true, -Dorg.jboss.byteman.verbose=true, -Dorg.jboss.byteman.contrib.dtest.rmiregistry.port=1199, -javaagent:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/txbridge/target/byteman/byteman.jar=port:9091,listener:true,sys:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/txbridge/target/byteman/byteman-dtest.jar, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/configuration, -c=standalone-xts.xml] > Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > TransformListener() : accepting requests on localhost:9091 > 00:53:48,689 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.0.Final > 00:53:49,098 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 00:53:49,246 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Core 2.0.5.Final "Kenny" starting > 00:53:51,591 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 00:53:51,629 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.4.Final > 00:53:51,659 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.4.Final > 00:53:51,751 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 40) WFLYCLINF0001: Activating Infinispan subsystem. > 00:53:51,743 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 00:53:51,771 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 39) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 00:53:51,815 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 41) WFLYIIOP0001: Activating IIOP Subsystem > 00:53:51,837 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 47) WFLYJSF0007: Activated the following JSF Implementations: [main] > 00:53:51,847 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.1.Final) > 00:53:51,913 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2 > 00:53:51,958 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.17.Final-wildfly-1 > 00:53:51,994 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. > 00:53:52,039 INFO [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem > 00:53:52,039 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 61) WFLYWS0002: Activating WebServices Extension > 00:53:52,076 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem > 00:53:52,066 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.4.Final > 00:53:52,227 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.11.Final starting > 00:53:52,237 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0003: Undertow 1.3.11.Final starting > 00:53:52,593 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 32 (per class), which is derived from thread worker pool sizing. > 00:53:52,594 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 8 (per class), which is derived from the number of CPUs on this host. > 00:53:52,713 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service > 00:53:52,723 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 00:53:52,887 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0014: Creating file handler for path '/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] > 00:53:52,934 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. > 00:53:52,938 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 00:53:53,155 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 > 00:53:53,521 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 00:53:53,575 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-4) WFLYIIOP0009: CORBA ORB Service started > 00:53:53,916 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final > 00:53:54,002 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "restat-web-5.2.13.Final-SNAPSHOT.war" (runtime-name: "restat-web-5.2.13.Final-SNAPSHOT.war") > 00:53:54,004 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/deployments > 00:53:54,004 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "xtstest.war" (runtime-name: "xtstest.war") > 00:53:54,192 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/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/journal,bindingsDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/activemq/paging) > 00:53:54,248 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.2.Final (Apache CXF 3.1.4) > 00:53:54,351 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221013: Using NIO Journal > 00:53:54,505 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-c11 > 00:53:54,506 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-client > 00:53:54,511 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-coordinator > 00:53:54,659 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) 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 > 00:53:54,661 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-1) 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 > 00:53:54,667 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:54,667 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:54,668 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,668 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,669 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,670 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,723 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,724 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,724 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) 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 > 00:53:54,966 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE > 00:53:54,988 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP > 00:53:55,029 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ > 00:53:55,034 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP > 00:53:55,155 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-deploy.ws-t11-participant > 00:53:55,156 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:55,168 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:55,169 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-4) 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 > 00:53:56,128 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}CompletionCoordinatorService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorPortTypeImpl > 00:53:56,138 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from class com.arjuna.webservices11.wscoor.sei.ActivationPortTypeImpl > 00:53:56,137 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) 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 > 00:53:56,131 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationParticipantPortType > 00:53:57,259 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live > 00:53:57,276 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010 [nodeID=7842cabe-b404-11e5-9b8e-a55e51d89294] > 00:53:57,412 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/ws-t11-client/TerminationParticipantService > 00:53:57,419 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinatorCompletionParticipantService > 00:53:57,412 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorService > 00:53:57,532 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-c11/ActivationService > 00:53:57,685 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorService.wsdl > 00:53:57,704 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from class com.arjuna.schemas.ws._2005._10.wsarjtx.TerminationCoordinatorPortType > 00:53:57,705 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/ActivationService.wsdl > 00:53:57,713 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from class com.arjuna.webservices11.wscoor.sei.RegistrationPortTypeImpl > 00:53:57,701 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/TerminationParticipantService.wsdl > 00:53:57,715 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://docs.oasis-open.org/ws-tx/wsat/2006/06}CompletionInitiatorService from class com.arjuna.webservices11.wsat.sei.CompletionInitiatorPortTypeImpl > 00:53:57,721 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithCoordinatorCompletionParticipantService.wsdl > 00:53:57,731 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}ParticipantService from class com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl > 00:53:57,749 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService > 00:53:57,773 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/ws-t11-client/CompletionInitiatorService > 00:53:57,779 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/ws-c11/RegistrationService > 00:53:57,785 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorService.wsdl > 00:53:57,795 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorRPCPortTypeImplService from class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorRPCPortTypeImpl > 00:53:57,804 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/ParticipantService > 00:53:57,808 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorRPCService > 00:53:57,822 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-client.deployment/CompletionInitiatorService.wsdl > 00:53:57,831 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/TerminationCoordinatorRPCPortTypeImplService.wsdl > 00:53:57,827 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-1) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-c11.deployment/RegistrationService.wsdl > 00:53:57,836 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}BusinessAgreementWithCoordinatorCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithCoordinatorCompletionCoordinatorPortTypeImpl > 00:53:57,842 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/ParticipantService.wsdl > 00:53:57,851 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionParticipantService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionParticipantPortTypeImpl > 00:53:57,903 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithParticipantCompletionParticipantService > 00:53:57,953 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-4) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-participant.deployment/BusinessAgreementWithParticipantCompletionParticipantService.wsdl > 00:53:57,960 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:53:57,988 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 00:53:58,005 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 00:53:58,014 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 00:53:58,015 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 00:53:58,025 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithCoordinatorCompletionCoordinatorService.wsdl > 00:53:58,027 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}BusinessAgreementWithParticipantCompletionCoordinatorService from class com.arjuna.webservices11.wsba.sei.BusinessAgreementWithParticipantCompletionCoordinatorPortTypeImpl > 00:53:58,044 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 00:53:58,045 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 00:53:58,052 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 00:53:58,053 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 00:53:58,061 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/BusinessAgreementWithParticipantCompletionCoordinatorService > 00:53:58,063 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 00:53:58,070 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 00:53:58,111 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor > 00:53:58,119 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor > 00:53:58,123 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/BusinessAgreementWithParticipantCompletionCoordinatorService.wsdl > 00:53:58,124 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}CoordinatorService from class com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl > 00:53:58,145 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CoordinatorService > 00:53:58,182 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 64) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 00:53:58,193 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CoordinatorService.wsdl > 00:53:58,203 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}CompletionCoordinatorRPCService from class com.arjuna.webservices11.wsat.sei.CompletionCoordinatorRPCPortTypeImpl > 00:53:58,210 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 00:53:58,212 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221003: trying to deploy queue jms.queue.DLQ > 00:53:58,217 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-c11 > 00:53:58,228 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 65) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue > 00:53:58,235 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/ws-t11-coordinator/CompletionCoordinatorRPCService > 00:53:58,261 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/ws-t11-coordinator.deployment/CompletionCoordinatorRPCService.wsdl > 00:53:58,287 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-client > 00:53:58,297 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-participant > 00:53:58,352 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0021: Registered web context: /ws-t11-client > 00:53:58,359 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0021: Registered web context: /ws-c11 > 00:53:58,360 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:53:58,359 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0021: Registered web context: /ws-t11-participant > 00:53:58,361 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 00:53:58,361 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 00:53:58,362 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 00:53:58,362 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 00:53:58,364 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 00:53:58,366 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0003: Starting service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 00:53:58,390 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint-publish.ws-t11-coordinator > 00:53:58,402 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0021: Registered web context: /ws-t11-coordinator > 00:53:58,413 WARN [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0005: Secure listener for protocol: 'HTTP/1.1' not found! Using non secure port! > 00:53:58,517 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.restat-web-5.2.13.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:53:58,523 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) WFLYSRV0018: Deployment "deployment.restat-web-5.2.13.Final-SNAPSHOT.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:53:58,591 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 00:53:58,776 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033006: InboundBridgeRecoveryManager starting > 00:53:58,777 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-2) ARJUNA033013: OutboundBridgeRecoveryManager starting > 00:53:58,821 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) Resource adaptor started > 00:53:58,821 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatoractivemq-ra > 00:53:58,823 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 00:53:58,823 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 00:53:58,950 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) 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. > 00:53:58,995 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment xtstest.war > 00:53:59,138 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.2.2.Final > 00:53:59,403 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0021: Registered web context: /rest-tx > 00:53:59,533 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: xtstest.war > 00:53:59,587 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.3.2 (Final) > 00:53:59,600 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,601 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,601 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,602 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) 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 > 00:53:59,616 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,679 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest1 > 00:53:59,689 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,690 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,693 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest2 > 00:53:59,719 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,722 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,726 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtsservicetest3 > 00:53:59,737 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,740 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://jbossts.jboss.org/xts/servicetests/generated}XTSServiceTestService from WSDL: WEB-INF/wsdl/xtsservicetests.wsdl > 00:53:59,743 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/xtstest/xtssubordinateservicetest1 > 00:53:59,750 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/xtstest.war/xtsservicetests.wsdl > 00:53:59,780 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 00:53:59,781 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 00:53:59,784 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 00:53:59,785 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 00:53:59,792 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0009: Starting weld service for deployment xtstest.war > 00:54:00,907 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 65) Starting XTSServiceTestRunner > 00:54:00,908 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 65) Started XTSServiceTestRunner > 00:54:00,925 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 65) Initializing Mojarra 2.2.12-jbossorg-2 20150729-1131 for context '/xtstest' > 00:54:01,758 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0021: Registered web context: /xtstest > 00:54:01,792 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "xtstest.war" (runtime-name : "xtstest.war") > 00:54:01,794 INFO [org.jboss.as.server] (ServerService Thread Pool -- 36) WFLYSRV0010: Deployed "restat-web-5.2.13.Final-SNAPSHOT.war" (runtime-name : "restat-web-5.2.13.Final-SNAPSHOT.war") > 00:54:02,073 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 00:54:02,074 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 00:54:02,074 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 2.0.5.Final "Kenny" started in 13928ms - Started 567 of 876 services (423 services are lazy, passive or on-demand) > Jan 06, 2016 12:54:02 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Automatic deploying of the managed deployment with name txbridge-outbound-tests-service for the container with name jboss > 00:54:02,228 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/9b/70e2a1644d4faf24e750f2cf3b295db924703a/content > 00:54:02,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "txbridge-outbound-tests-service.war" (runtime-name: "txbridge-outbound-tests-service.war") > 00:54:02,258 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-service.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:54:02,329 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=OutboundTestServiceATServlet > address=http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl > implementor=org.jboss.jbossts.txbridge.tests.outbound.service.TestATServiceImpl > serviceName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService > portName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplPort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 00:54:02,329 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-2) JBWS024061: Adding service endpoint metadata: id=OutboundTestServiceNonATServlet > address=http://localhost:8080/txbridge-outbound-tests-service/TestNonATServiceImpl > implementor=org.jboss.jbossts.txbridge.tests.outbound.service.TestNonATServiceImpl > serviceName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplService > portName={http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplPort > annotationWsdlLocation=null > wsdlLocationOverride=null > mtomEnabled=false > 00:54:02,350 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from class org.jboss.jbossts.txbridge.tests.outbound.service.TestATServiceImpl > 00:54:02,377 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl > 00:54:02,392 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/txbridge-outbound-tests-service.war/TestATServiceImplService.wsdl > 00:54:02,396 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-2) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestNonATServiceImplService from class org.jboss.jbossts.txbridge.tests.outbound.service.TestNonATServiceImpl > 00:54:02,399 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting the server's publish address to be http://localhost:8080/txbridge-outbound-tests-service/TestNonATServiceImpl > 00:54:02,404 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-2) JBWS024074: WSDL published to: file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/wsdl/txbridge-outbound-tests-service.war/TestNonATServiceImplService.wsdl > 00:54:02,422 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0003: Starting service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceATServlet > 00:54:02,422 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0003: Starting service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceNonATServlet > 00:54:02,434 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /txbridge-outbound-tests-service > 00:54:02,492 INFO [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "txbridge-outbound-tests-service.war" (runtime-name : "txbridge-outbound-tests-service.war") > Jan 06, 2016 12:54:02 AM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > Jan 06, 2016 12:54:02 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController start > INFO: Automatic deploying of the managed deployment with name txbridge-outbound-tests-client for the container with name jboss > 00:54:02,720 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/b3/6bdfaa5feca5ff426c038cb7f2f2fed119847f/content > 00:54:02,723 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "txbridge-outbound-tests-client.war" (runtime-name: "txbridge-outbound-tests-client.war") > 00:54:02,746 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-client.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 00:54:02,746 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.txbridge-outbound-tests-client.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. > 00:54:02,810 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 4) WFLYUT0021: Registered web context: /txbridge-outbound-tests-client > 00:54:02,823 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "txbridge-outbound-tests-client.war" (runtime-name : "txbridge-outbound-tests-client.war") > 00:54:03,077 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from WSDL: http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl?wsdl > 00:54:03,099 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (default task-1) Creating Service {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService from WSDL: http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl?wsdl > 00:55:03,344 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default task-1) Interceptor for {http://client.outbound.tests.txbridge.jbossts.jboss.org/}TestATServiceImplService#{http://client.outbound.tests.txbridge.jbossts.jboss.org/}doNothing has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not send Message. > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > at com.sun.proxy.$Proxy137.doNothing(Unknown Source) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:140) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.doPost(TestATClient.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl: Read timed out > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > ... 39 more > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > ... 42 more > 00:55:03,349 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /txbridge-outbound-tests-client//testATClient: java.lang.RuntimeException: javax.xml.ws.WebServiceException: Could not send Message. > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:148) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.doPost(TestATClient.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: javax.xml.ws.WebServiceException: Could not send Message. > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:150) > at com.sun.proxy.$Proxy137.doNothing(Unknown Source) > at org.jboss.jbossts.txbridge.tests.outbound.client.TestATClient.executeTest(TestATClient.java:140) > ... 30 more > Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking http://localhost:8080/txbridge-outbound-tests-service/TestATServiceImpl: Read timed out > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1376) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1360) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > ... 32 more > Caused by: java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > ... 42 more > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Automatic undeploying of the managed deployment with name txbridge-outbound-tests-service from the container with name jboss > 00:55:03,375 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 70) WFLYUT0022: Unregistered web context: /txbridge-outbound-tests-service > 00:55:03,387 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceNonATServlet > 00:55:03,389 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."txbridge-outbound-tests-service.war".OutboundTestServiceATServlet > 00:55:03,452 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment txbridge-outbound-tests-service.war (runtime-name: txbridge-outbound-tests-service.war) in 85ms > 00:55:03,469 INFO [org.jboss.as.repository] (management-handler-thread - 5) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/9b/70e2a1644d4faf24e750f2cf3b295db924703a/content > 00:55:03,469 INFO [org.jboss.as.server] (management-handler-thread - 5) WFLYSRV0009: Undeployed "txbridge-outbound-tests-service.war" (runtime-name: "txbridge-outbound-tests-service.war") > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Automatic undeploying of the managed deployment with name txbridge-outbound-tests-client from the container with name jboss > 00:55:03,481 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Unregistered web context: /txbridge-outbound-tests-client > 00:55:03,491 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment txbridge-outbound-tests-client.war (runtime-name: txbridge-outbound-tests-client.war) in 12ms > 00:55:03,502 INFO [org.jboss.as.repository] (management-handler-thread - 6) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/jboss-as/build/target/wildfly-10.0.0.Final-SNAPSHOT/standalone/data/content/b3/6bdfaa5feca5ff426c038cb7f2f2fed119847f/content > 00:55:03,502 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0009: Undeployed "txbridge-outbound-tests-client.war" (runtime-name: "txbridge-outbound-tests-client.war") > Jan 06, 2016 12:55:03 AM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController stop > INFO: Manual stopping of a server instance > 00:55:03,508 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0211: Suspending server with 0ms timeout. > 00:55:03,512 INFO [org.jboss.as.server] (Thread-3) WFLYSRV0220: Server shutdown has been requested. > 00:55:03,544 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-3) ARJUNA033014: OutboundBridgeRecoveryManager stopping > 00:55:03,545 INFO [org.jboss.jbossts.txbridge] (MSC service thread 1-1) ARJUNA033007: InboundBridgeRecoveryManager stopping > 00:55:03,557 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Unregistered web context: /rest-tx > 00:55:03,567 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 00:55:03,577 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0022: Unregistered web context: /xtstest > 00:55:03,582 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA] > 00:55:03,587 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 71) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory > 00:55:03,604 ERROR [org.jboss.remoting.resource] (Remoting "brandon:MANAGEMENT" task-8) Close action for Channel ID 25c56b1d (inbound) of Remoting connection 01cf11a2 to /127.0.0.1:47100 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating > at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588) > at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327) > at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138) > at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261) > at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534) > at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372) > at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437) > at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114) > at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > 00:55:03,608 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-coordinator > 00:55:03,612 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-client > 00:55:03,612 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0022: Unregistered web context: /ws-t11-client > 00:55:03,613 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-t11-participant > 00:55:03,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0022: Unregistered web context: /ws-t11-participant > 00:55:03,613 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-publish.ws-c11 > 00:55:03,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0022: Unregistered web context: /ws-c11 > 00:55:03,617 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /ws-t11-coordinator > 00:55:03,617 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".TerminationParticipantService > 00:55:03,618 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-client.deployment".CompletionInitiatorService > 00:55:03,620 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".RegistrationService > 00:55:03,621 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-client > 00:55:03,620 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-c11.deployment".ActivationService > 00:55:03,624 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-c11 > 00:55:03,634 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".ParticipantService > 00:55:03,634 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithParticipantCompletionParticipantService > 00:55:03,635 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-participant.deployment".BusinessAgreementWithCoordinatorCompletionParticipantService > 00:55:03,637 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService > 00:55:03,637 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService > 00:55:03,641 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService > 00:55:03,642 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService > 00:55:03,643 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService > 00:55:03,643 INFO [org.jboss.as.webservices] (MSC service thread 1-1) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-participant > 00:55:03,644 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint-deploy.ws-t11-coordinator > 00:55:03,655 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 74) Stopping XTSServiceTestRunner > 00:55:03,656 INFO [org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean] (ServerService Thread Pool -- 74) Stopped XTSServiceTestRunner > 00:55:03,657 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 75) AMQ151003: resource adaptor stopped > 00:55:03,678 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment restat-web-5.2.13.Final-SNAPSHOT.war (runtime-name: restat-web-5.2.13.Final-SNAPSHOT.war) in 159ms > 00:55:03,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0019: Host default-host stopping > 00:55:03,711 INFO [org.jboss.as.webservices] (MSC service thread 1-2) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_One > 00:55:03,712 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Subordinate_Service_One > 00:55:03,711 INFO [org.jboss.as.webservices] (MSC service thread 1-3) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Two > 00:55:03,713 INFO [org.jboss.as.webservices] (MSC service thread 1-4) WFLYWS0004: Stopping service jboss.ws.endpoint."xtstest.war".XTS_Service_Test_Service_Three > 00:55:03,714 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0010: Stopping weld service for deployment xtstest.war > 00:55:03,772 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 00:55:03,787 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 00:55:03,805 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-010 [7842cabe-b404-11e5-9b8e-a55e51d89294] stopped > 00:55:03,806 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending > 00:55:03,807 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080 > 00:55:03,808 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.3.11.Final stopping > 00:55:03,827 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment xtstest.war (runtime-name: xtstest.war) in 308ms > 00:55:03,836 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Core 2.0.5.Final "Kenny" stopped in 284ms > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2602) QA suite failure: TestGroup_txcore_lockrecord In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2602: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > QA suite failure: TestGroup_txcore_lockrecord > --------------------------------------------- > > Key: JBTM-2602 > URL: https://issues.jboss.org/browse/JBTM-2602 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2598) Merge in BlackTie Javadocs to main Narayana javadocs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2598: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Merge in BlackTie Javadocs to main Narayana javadocs > ---------------------------------------------------- > > Key: JBTM-2598 > URL: https://issues.jboss.org/browse/JBTM-2598 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Documentation > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > The BlackTie javadocs are still separate http://narayana.io/documentation/index.html - it would be useful to ensure that they are in the same place as the rest of the Narayana javadocs. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2580) Create a Narayana troubleshooting guide In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2580: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Create a Narayana troubleshooting guide > --------------------------------------- > > Key: JBTM-2580 > URL: https://issues.jboss.org/browse/JBTM-2580 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > This information may already exist but is possibly fragmented. This issue is to record the fact that we need to collate this. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2571) Enable code coverage for XTS crash recovery tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2571: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Enable code coverage for XTS crash recovery tests > ------------------------------------------------- > > Key: JBTM-2571 > URL: https://issues.jboss.org/browse/JBTM-2571 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Code coverage data is not collected during the XTS crash recovery tests execution. Currently this seems to be blocked by [1], [2], and [3]. > [1] https://community.jboss.org/message/817252 > [2] https://issues.jboss.org/browse/ARQ-1014 > [3] https://issues.jboss.org/browse/ARQ-918 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2553: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Investigate the test with byteman do not work with the jacoco > ------------------------------------------------------------- > > Key: JBTM-2553 > URL: https://issues.jboss.org/browse/JBTM-2553 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:03 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2522) Update performance comparison tests to use JMH In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2522: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Update performance comparison tests to use JMH > ---------------------------------------------- > > Key: JBTM-2522 > URL: https://issues.jboss.org/browse/JBTM-2522 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:04 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2498: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:04 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2497) Update or remove references of HornetQ to Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2497: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Update or remove references of HornetQ to Artemis > ------------------------------------------------- > > Key: JBTM-2497 > URL: https://issues.jboss.org/browse/JBTM-2497 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator, Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > There were reports of HornetQ still in at least the fooapp QS. We should try to remove references to the specific implementation unless necessary and in those cases use the correct name which is now Artemis. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:04 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2495: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' 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. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' 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. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:04 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2481) Automate NRP In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2481: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:04 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2458) Think of the possibility to improve Compensations API with lambdas In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2458: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Think of the possibility to improve Compensations API with lambdas > ------------------------------------------------------------------ > > Key: JBTM-2458 > URL: https://issues.jboss.org/browse/JBTM-2458 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Emmanuel suggested to reduce verbosity in Compensations API by making it possible to use lambdas for handler implementation. > We should try to think of the best API changes to introduce that. > We could rewrite MongoDB quickstart to make it easier to visualise the difference. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:04 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2480: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Provide documentation of how to integrate with Karaf > ---------------------------------------------------- > > Key: JBTM-2480 > URL: https://issues.jboss.org/browse/JBTM-2480 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > This should include recovery information -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:04 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2305) Incomplete tooling documentation In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2305: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Incomplete tooling documentation > -------------------------------- > > Key: JBTM-2305 > URL: https://issues.jboss.org/browse/JBTM-2305 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > For tooling the docs defer to the wildfly/EAP cli for "5.1.1. Browse and Manage Transactions Using an Application Server". We had some text in the README explaining how to view the tooling MBeans but the equivalent needs to be added to the development_guide too for use with standalone narayana. > In addition the docs need to explain how to extend the tooling for new abstract records (basically the user needs to create a JMX MBean for the new type and register it with the ObjStoreBrowser). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:04 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2298) Use Project Atomic for docker image(s) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2298: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Use Project Atomic for docker image(s) > -------------------------------------- > > Key: JBTM-2298 > URL: https://issues.jboss.org/browse/JBTM-2298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > > When I created the initial docker (POC) image I did so using a standard Fedora base image. We should also look at supporting the Project Atomic docker image, since it's important for Red Hat. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:05 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:05 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2234) out of memory when logging more messages than heap size (surefire issue) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2234: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > out of memory when logging more messages than heap size (surefire issue) > ------------------------------------------------------------------------ > > Key: JBTM-2234 > URL: https://issues.jboss.org/browse/JBTM-2234 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.0.2 > Environment: JTS testing > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > Running com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 on JacORB with about 500000 transactions results in an OOM error because surefire keeps in logs in memory until the test has finished. > In this particular test jacorb logs messages at INFO level for each transaction resulting in excessive memory requirements. We can't make the heap too large because the default JVM is 32 bit. However, we could fix it by reducing the jacorb log level to WARN. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:05 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:05 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1804: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > JTS remote tests not run and no code coverage > --------------------------------------------- > > Key: JBTM-1804 > URL: https://issues.jboss.org/browse/JBTM-1804 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build. > It would then be beneficial to have them instrumented by emma to get code coverage. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:05 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:05 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-855) Create an example showing integration with Spring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-855: ------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:04 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:04 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2433) TransactionRolledBackException in MultiCloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2433: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > TransactionRolledBackException in MultiCloseTest > ------------------------------------------------ > > Key: JBTM-2433 > URL: https://issues.jboss.org/browse/JBTM-2433 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Attachments: com.arjuna.wstx.tests.arq.ba.MultiCloseTest-output.txt > > > It looks like this failure has been caused by the race condition in WS-BA. In our tests it should be handled by the Byteman rule, but seems that for an unknown reason it has still failed in this occasion. > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.MultiCloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.117 sec <<< FAILURE! > testMultiClose(com.arjuna.wstx.tests.arq.ba.MultiCloseTest) Time elapsed: 2.5 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.MultiCloseTest.testMultiClose(MultiCloseTest.java:71) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 05:45:05 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 05:45:05 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2115) Not all classes are under code coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2115: -------------------------------- Fix Version/s: 5.next (was: 5.2.13.Final) > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 06:30:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 29 Jan 2016 06:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2616) Implement JMS integration classes In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2616: ------------------------------------- Summary: Implement JMS integration classes Key: JBTM-2616 URL: https://issues.jboss.org/browse/JBTM-2616 Project: JBoss Transaction Manager Issue Type: Sub-task Components: JTA Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next Both Spring and Spring Boot requires ConnectionFactory, Connection, Session implementation which should handle the transaction related tasks when using JMS e.g. enlisting xa resources, registering synchronizations etc. This should be somethings similar to the ConnectionManager and ConnectionImple used by the transactional driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 06:30:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 29 Jan 2016 06:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2606) Create Spring Boot starter for Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2606 stopped by Gytis Trikleris. --------------------------------------------- > Create Spring Boot starter for Narayana > --------------------------------------- > > Key: JBTM-2606 > URL: https://issues.jboss.org/browse/JBTM-2606 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Spring provides a bunch of Spring Boot starter artefacts in order to make integration of certain projects easier. We should investigate having one for Narayana. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 06:31:00 2016 From: issues at jboss.org (Jive JIRA Integration (JIRA)) Date: Fri, 29 Jan 2016 06:31:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2616) Implement JMS integration classes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jive JIRA Integration updated JBTM-2616: ---------------------------------------- Forum Reference: https://developer.jboss.org/message/949577#949577 > Implement JMS integration classes > --------------------------------- > > Key: JBTM-2616 > URL: https://issues.jboss.org/browse/JBTM-2616 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Both Spring and Spring Boot requires ConnectionFactory, Connection, Session implementation which should handle the transaction related tasks when using JMS e.g. enlisting xa resources, registering synchronizations etc. > This should be somethings similar to the ConnectionManager and ConnectionImple used by the transactional driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 06:32:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 29 Jan 2016 06:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2616) Implement JMS integration classes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2616 started by Gytis Trikleris. --------------------------------------------- > Implement JMS integration classes > --------------------------------- > > Key: JBTM-2616 > URL: https://issues.jboss.org/browse/JBTM-2616 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > Both Spring and Spring Boot requires ConnectionFactory, Connection, Session implementation which should handle the transaction related tasks when using JMS e.g. enlisting xa resources, registering synchronizations etc. > This should be somethings similar to the ConnectionManager and ConnectionImple used by the transactional driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:43:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2613) BABridgedTest failure (caused by WebServiceException: Could not send Message) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2613: -------------------------------- Fix Version/s: 5.next > BABridgedTest failure (caused by WebServiceException: Could not send Message) > ----------------------------------------------------------------------------- > > Key: JBTM-2613 > URL: https://issues.jboss.org/browse/JBTM-2613 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest.txt > > > job number was: http://172.17.130.4:8083/job/narayana-dualstack/80 > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest > ------------------------------------------------------------------------------- > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 72.917 sec <<< FAILURE! > testClose(org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest) Time elapsed: 60.65 sec <<< ERROR! > javax.xml.ws.WebServiceException: Could not send Message. > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1535) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) > at org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.getResponseCode(URLConnectionHTTPConduit.java:332) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.doProcessResponseCode(HTTPConduit.java:1577) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1606) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1550) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1347) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:651) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:514) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:423) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:324) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:277) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > at com.sun.proxy.$Proxy169.reset(Unknown Source) > at org.jboss.narayana.txframework.functional.ws.ba.bridged.BABridgedTest.teardownTest(BABridgedTest.java:97) -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:44:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2541) Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2541: -------------------------------- Fix Version/s: 6.later > Even ActiveMQ Artemis object store is used the Narayana log contains notion of HornetQ store > -------------------------------------------------------------------------------------------- > > Key: JBTM-2541 > URL: https://issues.jboss.org/browse/JBTM-2541 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.2.5.Final > Reporter: Ond?ej Chaloupka > Assignee: Amos Feng > Priority: Minor > Fix For: 6.later > > > Currently the Narayna could use journal store which is implemented by ActiveMQ journaling. But after activation the narayana trace log contains messages like > {{2015-10-23 12:24:40,735 TRACE [com.arjuna.ats.arjuna] HornetqObjectStore.start()}}. > If HornetQ object store is not really used the log messages should be changed to correspond to the state. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:44:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2505) Java heap space issue on Brandon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2505. --------------------------------- Resolution: Won't Fix > Java heap space issue on Brandon > -------------------------------- > > Key: JBTM-2505 > URL: https://issues.jboss.org/browse/JBTM-2505 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.2.5.Final > Reporter: Gytis Trikleris > Attachments: consoleText.txt > > > narayana-AS800 build fails whenever it runs on Brandon due to not enough java heap space. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:44:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2505) Java heap space issue on Brandon In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2505. ------------------------------- > Java heap space issue on Brandon > -------------------------------- > > Key: JBTM-2505 > URL: https://issues.jboss.org/browse/JBTM-2505 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.2.5.Final > Reporter: Gytis Trikleris > Attachments: consoleText.txt > > > narayana-AS800 build fails whenever it runs on Brandon due to not enough java heap space. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:44:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2469) BlackTie tests failing due to missing queue/BTR_TestTPConnect In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2469. ------------------------------- Resolution: Out of Date > BlackTie tests failing due to missing queue/BTR_TestTPConnect > ------------------------------------------------------------- > > Key: JBTM-2469 > URL: https://issues.jboss.org/browse/JBTM-2469 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.2.0 > Reporter: Michael Musgrove > > job http://albany.eng.hst.ams2.redhat.com/job/narayana-catelyn/967 has been running for a couple of days with the repeated failure: > bq. javax.naming.NameNotFoundException: queue/BTR_TestTPConnect -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:45:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:45:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2419) Consider reducing the number of JMH perf test forks on PRs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2419: -------------------------------- Fix Version/s: 5.next > Consider reducing the number of JMH perf test forks on PRs > ---------------------------------------------------------- > > Key: JBTM-2419 > URL: https://issues.jboss.org/browse/JBTM-2419 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Fix For: 5.next > > > We run our JMH tests multiple times in order to estimate run-to-run variance. The [JMH docs|http://hg.openjdk.java.net/code-tools/jmh/file/tip/jmh-samples/src/main/java/org/openjdk/jmh/samples/JMHSample_13_RunToRun.java] state: > bq. JVMs are complex systems, and the non-determinism is inherent for them. This requires us to always account the run-to-run variance as the one of the effects in our experiments. Forking aggregates the results across several JVM launches. > Currently we set the number of forks to 10. We run each test 6 times with each run lasting 1 min. Since we have 10 tests this means it takes 10 * 10 * 6 minutes for the benchmarks to complete. In the future we want to keep adding new performance tests and the time taken to run a PR will become prohibitive. I would like to propose one of the following solutions: > - reduce the number of forks; > - run a subset of performance tests on each PR and then run them all once a week or so on the main build > My preference is to reduce the number of forks to 3. Note that the PR requester has the option to disable performance tests for his PR (by including !PERF in the comment section). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:45:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:45:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2419) Consider reducing the number of JMH perf test forks on PRs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2419: -------------------------------- Priority: Minor (was: Major) > Consider reducing the number of JMH perf test forks on PRs > ---------------------------------------------------------- > > Key: JBTM-2419 > URL: https://issues.jboss.org/browse/JBTM-2419 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > We run our JMH tests multiple times in order to estimate run-to-run variance. The [JMH docs|http://hg.openjdk.java.net/code-tools/jmh/file/tip/jmh-samples/src/main/java/org/openjdk/jmh/samples/JMHSample_13_RunToRun.java] state: > bq. JVMs are complex systems, and the non-determinism is inherent for them. This requires us to always account the run-to-run variance as the one of the effects in our experiments. Forking aggregates the results across several JVM launches. > Currently we set the number of forks to 10. We run each test 6 times with each run lasting 1 min. Since we have 10 tests this means it takes 10 * 10 * 6 minutes for the benchmarks to complete. In the future we want to keep adding new performance tests and the time taken to run a PR will become prohibitive. I would like to propose one of the following solutions: > - reduce the number of forks; > - run a subset of performance tests on each PR and then run them all once a week or so on the main build > My preference is to reduce the number of forks to 3. Note that the PR requester has the option to disable performance tests for his PR (by including !PERF in the comment section). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:46:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2409) XARecoveryModuleHelpersUnitTest hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2409: -------------------------------- Fix Version/s: 5.next > XARecoveryModuleHelpersUnitTest hang > ------------------------------------ > > Key: JBTM-2409 > URL: https://issues.jboss.org/browse/JBTM-2409 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Fix For: 5.next > > Attachments: 32287.jstack, hang.jstack > > > The test checks that recovery helpers can be removed at the correct stages during recovery scans. The CI job http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/196 shows the hang. > The junit test thread: > - starts 2 threads that will remove a recovery helper > - triggers xaRecoveryModule.periodicWorkFirstPass() > - triggers xaRecoveryModule.periodicWorkSecondPass() > - joins with remover threads > The jstack output shows: > - the two threads in the process of removing a recovery helper and are waiting for the first pass to finish; > - the junit test thread is waiting to join with these two threads; > Since both recovery passes must have completed it looks like the remover threads weren't notified when the first pass completed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:46:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2409) XARecoveryModuleHelpersUnitTest hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2409: -------------------------------- Priority: Minor (was: Major) > XARecoveryModuleHelpersUnitTest hang > ------------------------------------ > > Key: JBTM-2409 > URL: https://issues.jboss.org/browse/JBTM-2409 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > Attachments: 32287.jstack, hang.jstack > > > The test checks that recovery helpers can be removed at the correct stages during recovery scans. The CI job http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/196 shows the hang. > The junit test thread: > - starts 2 threads that will remove a recovery helper > - triggers xaRecoveryModule.periodicWorkFirstPass() > - triggers xaRecoveryModule.periodicWorkSecondPass() > - joins with remover threads > The jstack output shows: > - the two threads in the process of removing a recovery helper and are waiting for the first pass to finish; > - the junit test thread is waiting to join with these two threads; > Since both recovery passes must have completed it looks like the remover threads weren't notified when the first pass completed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:47:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:47:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2275) Create the zip airtifact of apr and log4cxx In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2275. ------------------------------- Resolution: Won't Fix Hopefully not required > Create the zip airtifact of apr and log4cxx > ------------------------------------------- > > Key: JBTM-2275 > URL: https://issues.jboss.org/browse/JBTM-2275 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Reporter: Amos Feng > Priority: Trivial > > Nexus imposes some conflicting requirements on needing a none-classifier version of the jar uploading at the same time to do the release -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:48:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2496) Investigate using of camel for content based routing in the Blacktie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2496: -------------------------------- Fix Version/s: (was: 5.later) > Investigate using of camel for content based routing in the Blacktie > -------------------------------------------------------------------- > > Key: JBTM-2496 > URL: https://issues.jboss.org/browse/JBTM-2496 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > The current cbr quickstart is out-of-date by using the jboss-esb and it needs to investigate the camel -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:48:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2497) Update or remove references of HornetQ to Artemis In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2497. ------------------------------- Fix Version/s: (was: 5.next) Resolution: Rejected > Update or remove references of HornetQ to Artemis > ------------------------------------------------- > > Key: JBTM-2497 > URL: https://issues.jboss.org/browse/JBTM-2497 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Demonstrator, Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > > There were reports of HornetQ still in at least the fooapp QS. We should try to remove references to the specific implementation unless necessary and in those cases use the correct name which is now Artemis. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:49:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2495: -------------------------------- Parent: JBTM-2498 Issue Type: Sub-task (was: Task) > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' 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. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' 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. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:49:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2495) Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2495: -------------------------------- Fix Version/s: (was: 5.next) > Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriate) > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2495 > URL: https://issues.jboss.org/browse/JBTM-2495 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M2 > Environment: RHEL 6.3 > Reporter: Joice Joy > Assignee: Amos Feng > Priority: Minor > > I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1 but the Wildfly server fails to start the Blacktie service > But the server does not start the blacktie service: > This is from quickstart quickstart/blacktie > > > > ========================================================================= > > > JBoss Bootstrap Environment > > > JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final > > > JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java > > > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE > > > ========================================================================= > > > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > 07:35:52,490 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 07:35:52,892 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final > 07:35:53,007 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting > 07:35:55,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' 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. > 07:35:55,055 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' 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. > 07:35:55,121 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear > 07:35:55,361 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:55,390 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 07:35:55,422 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final > 07:35:55,438 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final > 07:35:55,482 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final > 07:35:55,548 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem. > 07:35:55,554 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors > 07:35:55,557 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem > 07:35:55,602 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 07:35:55,615 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main] > 07:35:55,652 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 07:35:55,661 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 07:35:55,670 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2 > 07:35:55,827 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem > 07:35:55,829 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final > 07:35:55,849 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 07:35:55,849 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension > 07:35:55,998 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,034 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting > 07:35:56,095 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 07:35:56,119 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 07:35:56,352 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content > 07:35:56,417 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. > 07:35:56,437 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting > 07:35:56,589 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 07:35:56,945 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started > 07:35:56,969 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 07:35:57,030 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments > 07:35:57,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:57,187 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging) > 07:35:57,193 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock > 07:35:57,287 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal > 07:35:57,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE > 07:35:57,414 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final > 07:35:57,439 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP > 07:35:57,443 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP > 07:35:57,502 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock > 07:35:57,504 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock > 07:35:58,108 INFO [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor > 07:35:58,112 INFO [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor > 07:35:58,206 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live > 07:35:58,207 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561] > 07:35:58,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue > 07:35:58,514 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory > 07:35:58,519 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 07:35:58,519 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ > 07:35:58,623 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA > 07:35:58,721 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started > 07:35:58,721 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra > 07:35:58,733 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 07:35:58,733 INFO [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,763 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar does not point to a valid jar for a Class-Path reference. > 07:35:58,780 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar") > 07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) > ... 6 more > > > 07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1] > Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}} > 07:35:58,980 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:58,982 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear" > > > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 07:35:59,202 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand) > 07:35:59,243 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms > 07:35:59,332 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms > 07:35:59,413 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content > 07:35:59,414 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear") > 07:35:59,414 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:50:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:50:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2096) ListServiceStatusTest.testListServiceStatusWithRunningServer: Command failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2096. ------------------------------- Resolution: Out of Date > ListServiceStatusTest.testListServiceStatusWithRunningServer: Command failed > ---------------------------------------------------------------------------- > > Key: JBTM-2096 > URL: https://issues.jboss.org/browse/JBTM-2096 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Priority: Minor > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/423/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el6/consoleText > {code} > Running org.jboss.narayana.blacktie.btadmin.ListServersStatusTest > 21:56:16,141 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 89) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 21:56:16,141 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 89) JBAS011601: Bound messaging object to jndi name /queue/BTR_.testsui1 > 21:56:19,541 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 89) HQ221003: trying to deploy queue jms.queue.BTR_.testsui2 > 21:56:19,541 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 89) JBAS011601: Bound messaging object to jndi name /queue/BTR_.testsui2 > 21:56:22,904 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 89) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 21:56:22,904 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 89) JBAS011601: Bound messaging object to jndi name /queue/BTR_BAR > 21:56:24,579 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a37%3a59%3a454518/terminate > 21:56:24,683 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a0%3a471367/terminate > 21:56:24,761 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a44%3a7%3a336519/terminate > 21:56:24,847 INFO [org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI] (Thread-38 (HornetQ-client-global-threads-26693153)) init PostConstruct > 21:56:24,849 INFO [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-38 (HornetQ-client-global-threads-26693153)) onConstruct load btconfig.xml > 21:56:24,854 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a6%3a292860/terminate > 21:56:31,591 INFO [org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService] (Thread-39 (HornetQ-client-global-threads-26693153)) init PostConstruct > 21:56:37,062 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 89) JBAS011605: Unbound messaging object to jndi name java:/queue/BTR_BAR > 21:56:37,243 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 89) JBAS011605: Unbound messaging object to jndi name java:/queue/BTR_.testsui2 > 21:56:38,066 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 8) undeploy service pending for .testsui1 as consumer count is 0, will check again in 30000ms > 21:56:39,278 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 89) JBAS011605: Unbound messaging object to jndi name java:/queue/BTR_.testsui1 > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 30.62 sec > Running org.jboss.narayana.blacktie.btadmin.ListServiceStatusTest > 21:56:47,603 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 89) HQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > 21:56:47,603 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 89) JBAS011601: Bound messaging object to jndi name /queue/BTR_.testsui1 > 21:56:51,939 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 89) HQ221003: trying to deploy queue jms.queue.BTR_.testsui2 > 21:56:51,939 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 89) JBAS011601: Bound messaging object to jndi name /queue/BTR_.testsui2 > 21:56:56,314 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 89) HQ221003: trying to deploy queue jms.queue.BTR_BAR > 21:56:56,314 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 89) JBAS011601: Bound messaging object to jndi name /queue/BTR_BAR > 21:56:58,193 ERROR [stderr] (Thread-1015) Exception in thread "Thread-1015" java.lang.ArrayIndexOutOfBoundsException: 1 > 21:56:58,193 ERROR [stderr] (Thread-1015) at org.jboss.narayana.blacktie.jatmibroker.core.server.Client.run(SocketServer.java:268) > 21:56:58,193 ERROR [stderr] (Thread-1015) at java.lang.Thread.run(Thread.java:744) > 21:56:58,210 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:36306) Caught an exception: Connection reset: java.net.SocketException: Connection reset > at java.net.SocketInputStream.read(SocketInputStream.java:196) [rt.jar:1.7.0_45] > at java.net.SocketInputStream.read(SocketInputStream.java:122) [rt.jar:1.7.0_45] > at java.net.SocketInputStream.read(SocketInputStream.java:210) [rt.jar:1.7.0_45] > at java.io.DataInputStream.readByte(DataInputStream.java:265) [rt.jar:1.7.0_45] > at org.codehaus.stomp.StompMarshaller.readLine(StompMarshaller.java:183) [wildfly-blacktie-5.1.0.Alpha1-SNAPSHOT.jar:5.1.0.Alpha1-SNAPSHOT] > at org.codehaus.stomp.StompMarshaller.unmarshal(StompMarshaller.java:94) [wildfly-blacktie-5.1.0.Alpha1-SNAPSHOT.jar:5.1.0.Alpha1-SNAPSHOT] > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:98) [wildfly-blacktie-5.1.0.Alpha1-SNAPSHOT.jar:5.1.0.Alpha1-SNAPSHOT] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > 21:57:39,481 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 9) undeploy service pending for .testsui1 as consumer count is 0, will check again in 30000ms > 21:57:46,601 ERROR [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-39 (HornetQ-client-global-threads-26693153)) call server testsui id 1 command advertise,BAR, failed with 13 > 21:57:46,603 WARN [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-39 (HornetQ-client-global-threads-26693153)) Failed to advertise service: BAR at: testsui1 > 21:57:47,610 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 90) JBAS011605: Unbound messaging object to jndi name java:/queue/BTR_BAR > 21:57:49,481 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 90) JBAS011605: Unbound messaging object to jndi name java:/queue/BTR_.testsui2 > 21:58:10,859 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 91) JBAS011605: Unbound messaging object to jndi name java:/queue/BTR_.testsui1 > 21:58:10,989 WARN [org.jboss.narayana.blacktie.administration.QueueReaperBean] (EJB default - 9) undeploy service .testsui1 for consumer is 0 > Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 110.906 sec <<< FAILURE! > testListServiceStatusWithRunningServer(org.jboss.narayana.blacktie.btadmin.ListServiceStatusTest) Time elapsed: 108.914 sec <<< FAILURE! > junit.framework.AssertionFailedError: Command failed > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.TestCase.fail(TestCase.java:227) > at org.jboss.narayana.blacktie.btadmin.ListServiceStatusTest.testListServiceStatusWithRunningServer(ListServiceStatusTest.java:93) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:51:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:51:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1573) Transaction timeout incompatible with block forever In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-1573: -------------------------------- Issue Type: Enhancement (was: Bug) > Transaction timeout incompatible with block forever > --------------------------------------------------- > > Key: JBTM-1573 > URL: https://issues.jboss.org/browse/JBTM-1573 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: BlackTie > Reporter: Tom Jenkinson > Attachments: blocking call.log > > > Currently we set a transaction timeout (e.g. in TestRollbackOnly.cxx we call tx_set_transaction_timeout) > This ends up putting a timetolive on the message of the same duration. > Now, if this message is not received within the period of time it will expire. > However we also use a block forever waiting for the response. > This can lead to a call never returning. > i.e. > server advertises queue > client sends message with small timeout (e.g. 4) and then blocks forever waiting response > server gets round to advertising queue 5 seconds later but never sees the clients initial request > client is blocked forever > I realise that we are meant to block forever when a client issues a tpcall under transactional conditions but something needs to be done as this can easily happen on slow machines? > Perhaps we need to make use of the DLQ to wake up the blocked client with an error message?? > Perhaps the client doesn't block forever and just calls txrollback if nothing is heard back?? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:51:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:51:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2527) Update to check the buffer size in btgetattribute In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2527: -------------------------------- Fix Version/s: (was: 5.later) > Update to check the buffer size in btgetattribute > ------------------------------------------------- > > Key: JBTM-2527 > URL: https://issues.jboss.org/browse/JBTM-2527 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > currently the nbf btgetattribute does not check the buffer size is big enough for copying the value. > So it should return error if the pass buffer size is not enough. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:54:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:54:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2478) Use Flame Graph tool In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2478: -------------------------------- Priority: Minor (was: Major) > Use Flame Graph tool > -------------------- > > Key: JBTM-2478 > URL: https://issues.jboss.org/browse/JBTM-2478 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Performance Testing > Reporter: Tom Jenkinson > Priority: Minor > > Tools and instructions are at: > https://github.com/jesperpedersen/perfjava/ <-- CPU sampling > https://github.com/jesperpedersen/javamemflame <-- Memory allocation tracking > Both use Agent_OnLoad/Agent_OnUnload, so better for smaller tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 08:54:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 08:54:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2478) Use Flame Graph tool In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2478: -------------------------------- Priority: Optional (was: Minor) > Use Flame Graph tool > -------------------- > > Key: JBTM-2478 > URL: https://issues.jboss.org/browse/JBTM-2478 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Performance Testing > Reporter: Tom Jenkinson > Priority: Optional > > Tools and instructions are at: > https://github.com/jesperpedersen/perfjava/ <-- CPU sampling > https://github.com/jesperpedersen/javamemflame <-- Memory allocation tracking > Both use Agent_OnLoad/Agent_OnUnload, so better for smaller tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 11:41:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 11:41:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2122) Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156578#comment-13156578 ] Tom Jenkinson commented on JBTM-2122: ------------------------------------- Observation: With JBR transport the enlist is done at the parent rather than the subordinate calling back (like it would in JTS). It seems at the moment this will result in propagated EAP transactions that use the JBR transport being 2PC. Was discussed as part of case 01560781. > Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2122 > URL: https://issues.jboss.org/browse/JBTM-2122 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 11:41:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 11:41:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2122) Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156579#comment-13156579 ] Tom Jenkinson commented on JBTM-2122: ------------------------------------- Observation: Bottom-up recovery not possible with JBR transport > Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2122 > URL: https://issues.jboss.org/browse/JBTM-2122 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 11:41:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 11:41:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2122) Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156579#comment-13156579 ] Tom Jenkinson edited comment on JBTM-2122 at 1/29/16 11:40 AM: --------------------------------------------------------------- Observation: Bottom-up recovery not implemented for JBR transport was (Author: tomjenkinson): Observation: Bottom-up recovery not possible with JBR transport > Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2122 > URL: https://issues.jboss.org/browse/JBTM-2122 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jan 29 11:44:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 29 Jan 2016 11:44:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2122) Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156583#comment-13156583 ] Tom Jenkinson commented on JBTM-2122: ------------------------------------- Discussion about enlistment is over here: http://lists.jboss.org/pipermail/wildfly-dev/2016-January/004725.html > Go through JTS code and compare/contrast with capabilities missing in other dist tx code we've got > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2122 > URL: https://issues.jboss.org/browse/JBTM-2122 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Mark Little > -- This message was sent by Atlassian JIRA (v6.4.11#64026)