From issues at jboss.org Mon Feb 1 06:24:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 1 Feb 2016 06:24:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2617: ------------------------------------- Summary: Add recovery support to JMS integration Key: JBTM-2617 URL: https://issues.jboss.org/browse/JBTM-2617 Project: JBoss Transaction Manager Issue Type: Sub-task Components: JTA Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 1 06:24:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 1 Feb 2016 06:24: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 stopped 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 Mon Feb 1 07:05:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 1 Feb 2016 07:05: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:comment-tabpanel&focusedCommentId=13156991#comment-13156991 ] Gytis Trikleris commented on JBTM-2613: --------------------------------------- [~mmusgrov], is the test output available? > 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 Mon Feb 1 07:56:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 1 Feb 2016 07:56: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:comment-tabpanel&focusedCommentId=13157032#comment-13157032 ] Michael Musgrove commented on JBTM-2613: ---------------------------------------- Sorry just the surefire output is available. The next job passed so I would be tempted to close with justification "Incomplete Description" > 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 Mon Feb 1 08:34:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 1 Feb 2016 08:34: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 ] Gytis Trikleris closed JBTM-2613. --------------------------------- Fix Version/s: (was: 5.next) Resolution: Incomplete Description > 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 Feb 1 09:54:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 1 Feb 2016 09:54: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:all-tabpanel ] Work on JBTM-2610 started by Gytis Trikleris. --------------------------------------------- > 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 Feb 1 09:58:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 1 Feb 2016 09:58: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:all-tabpanel ] Work on JBTM-2610 stopped by Gytis Trikleris. --------------------------------------------- > 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 Feb 1 09:58:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 1 Feb 2016 09:58: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=13157136#comment-13157136 ] Gytis Trikleris commented on JBTM-2610: --------------------------------------- Have to wait until the CI cluster gets back up, so that I could access test output. > 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 Feb 2 07:38:00 2016 From: issues at jboss.org (Luis Barreiro (JIRA)) Date: Tue, 2 Feb 2016 07:38:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2618) Improve concurrent behavior of HornetqJournalStore In-Reply-To: References: Message-ID: Luis Barreiro created JBTM-2618: ----------------------------------- Summary: Improve concurrent behavior of HornetqJournalStore Key: JBTM-2618 URL: https://issues.jboss.org/browse/JBTM-2618 Project: JBoss Transaction Manager Issue Type: Enhancement Reporter: Luis Barreiro Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 2 07:48:00 2016 From: issues at jboss.org (Anonymous (JIRA)) Date: Tue, 2 Feb 2016 07:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2618) Improve concurrent behavior of HornetqJournalStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Luis Barreiro created pull request #973 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Improve concurrent behavior of HornetqJournalStore > -------------------------------------------------- > > Key: JBTM-2618 > URL: https://issues.jboss.org/browse/JBTM-2618 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Luis Barreiro > > Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 2 08:05:00 2016 From: issues at jboss.org (Luis Barreiro (JIRA)) Date: Tue, 2 Feb 2016 08:05:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2618) Improve concurrent behavior of HornetqJournalStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luis Barreiro updated JBTM-2618: -------------------------------- Description: Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. When there is a was:Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. > Improve concurrent behavior of HornetqJournalStore > -------------------------------------------------- > > Key: JBTM-2618 > URL: https://issues.jboss.org/browse/JBTM-2618 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Luis Barreiro > > Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. > When there is a -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 2 08:06:00 2016 From: issues at jboss.org (Luis Barreiro (JIRA)) Date: Tue, 2 Feb 2016 08:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2618) Improve concurrent behavior of HornetqJournalStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luis Barreiro updated JBTM-2618: -------------------------------- Description: Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. When there is a high number of threads, some will be block reducing the overall throughput and increasing response times on the whole system. was: Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. When there is a > Improve concurrent behavior of HornetqJournalStore > -------------------------------------------------- > > Key: JBTM-2618 > URL: https://issues.jboss.org/browse/JBTM-2618 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Luis Barreiro > > Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. > When there is a high number of threads, some will be block reducing the overall throughput and increasing response times on the whole system. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 2 10:09:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 2 Feb 2016 10:09:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2617 started by Gytis Trikleris. --------------------------------------------- > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 2 17:07:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 2 Feb 2016 17:07: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 Tue Feb 2 17:10:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 2 Feb 2016 17:10: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:comment-tabpanel&focusedCommentId=13157972#comment-13157972 ] Gytis Trikleris commented on JBTM-2616: --------------------------------------- Proxy classes with unit tests: https://github.com/gytis/narayana/commit/ef28ed806b15a0b915b4db87b3f8d94246358b62 Commit and rollback integration tests with ActiveMQ Artemis: https://github.com/gytis/narayana/commit/5c9adae735c8d5717dc96152c84624f2aaf570ed > 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 Wed Feb 3 03:19:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 3 Feb 2016 03:19:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstar to show using of the narayana-osgi-jta bundle In-Reply-To: References: Message-ID: Amos Feng created JBTM-2619: ------------------------------- Summary: Create a quickstar to show using of the narayana-osgi-jta bundle Key: JBTM-2619 URL: https://issues.jboss.org/browse/JBTM-2619 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator Reporter: Amos Feng Assignee: Amos Feng -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 3 03:31:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 3 Feb 2016 03:31:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstar to show using of the narayana-osgi-jta bundle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2619: ---------------------------- Description: It should be with the recovery example > Create a quickstar to show using of the narayana-osgi-jta bundle > ----------------------------------------------------------------- > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 3 03:45:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 3 Feb 2016 03:45:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstar to show using of the narayana-osgi-jta bundle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2619: -------------------------------- Fix Version/s: 5.next > Create a quickstar to show using of the narayana-osgi-jta bundle > ----------------------------------------------------------------- > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 3 03:45:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 3 Feb 2016 03:45:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstar to show using of the narayana-osgi-jta bundle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2619: -------------------------------- Priority: Minor (was: Major) > Create a quickstar to show using of the narayana-osgi-jta bundle > ----------------------------------------------------------------- > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 3 03:45:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 3 Feb 2016 03:45:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstart to show using of the narayana-osgi-jta bundle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2619: -------------------------------- Summary: Create a quickstart to show using of the narayana-osgi-jta bundle (was: Create a quickstar to show using of the narayana-osgi-jta bundle) > Create a quickstart to show using of the narayana-osgi-jta bundle > ------------------------------------------------------------------ > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 3 03:45:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 3 Feb 2016 03:45:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstart to show using of the narayana-osgi-jta bundle In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158058#comment-13158058 ] Tom Jenkinson commented on JBTM-2619: ------------------------------------- I think a simple example with two dummy XAResources and a System.exit in the commit of the first one followed by seeing recovery happen will be sufficient > Create a quickstart to show using of the narayana-osgi-jta bundle > ------------------------------------------------------------------ > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 4 03:12:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 4 Feb 2016 03:12: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=13158593#comment-13158593 ] Tom Jenkinson commented on JBTM-2606: ------------------------------------- Can we get a link to your branch here please? > 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 Thu Feb 4 06:31:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 4 Feb 2016 06:31: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: -------------------------------- Forum Reference: https://developer.jboss.org/message/948921#948921, https://developer.jboss.org/message/950188 (was: 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: 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 Thu Feb 4 06:33:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 4 Feb 2016 06:33: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:comment-tabpanel&focusedCommentId=13158692#comment-13158692 ] Tom Jenkinson commented on JBTM-855: ------------------------------------ I believe there is a forum topic about recovery and Spring that needs linking to this jira. > 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 Thu Feb 4 08:22:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 4 Feb 2016 08:22: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 updated JBTM-2580: -------------------------------- Priority: Minor (was: Major) > 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 > Priority: Minor > 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 Thu Feb 4 08:26:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 4 Feb 2016 08:26: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: -------------------------------- Fix Version/s: 5.later (was: 5.next) > 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.later > > > 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 Thu Feb 4 08:26:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 4 Feb 2016 08:26: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.later (was: 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 > Priority: Minor > Fix For: 5.later > > > 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 Thu Feb 4 08:27:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 4 Feb 2016 08:27:00 -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 resolved JBTM-2481. --------------------------------- Resolution: Done > 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 Thu Feb 4 08:42:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 4 Feb 2016 08:42:00 -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:comment-tabpanel&focusedCommentId=13158779#comment-13158779 ] Gytis Trikleris commented on JBTM-2481: --------------------------------------- Are we not planning to make the release completely automatic and incorporating it into our CI? > 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 Thu Feb 4 11:40:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 4 Feb 2016 11:40:00 -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:comment-tabpanel&focusedCommentId=13158905#comment-13158905 ] Tom Jenkinson commented on JBTM-2481: ------------------------------------- I think the process is sufficiently automated. We may create a new task to trigger this automatic process in the future but for now I am happy with now NRP works. > 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.2.13.Final > > > 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 Thu Feb 4 11:40:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 4 Feb 2016 11:40:00 -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.2.13.Final (was: 5.next) > 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.2.13.Final > > > 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 Thu Feb 4 11:40:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 4 Feb 2016 11:40:01 -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 closed JBTM-2481. ------------------------------- > 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.2.13.Final > > > 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 Feb 5 03:31:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 5 Feb 2016 03:31:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2620) Introduce narayana-properties.xml as default property file name In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2620: ----------------------------------- Summary: Introduce narayana-properties.xml as default property file name Key: JBTM-2620 URL: https://issues.jboss.org/browse/JBTM-2620 Project: JBoss Transaction Manager Issue Type: Feature Request Reporter: Tom Jenkinson Fix For: 6.later With the next Major release of Narayana: 1. We introduce a new narayana-properties.xml 2. The narayana-jt* jars not override the properties name in their manifest but we still support that facility in case someone else is using it 3. We change the search path to look for .xml, narayana-properties.xml, then jbossts-properties.xml and finally arjuna-properties.xml. When people use the raw jars (org.jboss.narayana.jta.jta for example) then they can then provide the same narayana-properties.xml as they would if they were using the uber jar (example org.jboss.narayana.jta.narayana-jta) without a system property. It should help in a Maven enabled debugger when executing applications running in integration environments like WildFly or Spring where debugging via an uber jar adds an extra layer that makes getting to the real source code harder and code fix cycle slower. This should not pose too much of a backwards compatibility issue unless the user has multiple config files with different names (arjuna and jbossts) in their path, were only using arjuna.jar and now jbossts-properties.xml was picked up. But for this reason I propose waiting until Narayana 6. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Feb 5 03:31:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 5 Feb 2016 03:31:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2620) Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2620: -------------------------------- Summary: Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name (was: Introduce narayana-properties.xml as default property file name) > Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2620 > URL: https://issues.jboss.org/browse/JBTM-2620 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Tom Jenkinson > Fix For: 6.later > > > With the next Major release of Narayana: > 1. We introduce a new narayana-properties.xml > 2. The narayana-jt* jars not override the properties name in their manifest but we still support that facility in case someone else is using it > 3. We change the search path to look for .xml, narayana-properties.xml, then jbossts-properties.xml and finally arjuna-properties.xml. > > When people use the raw jars (org.jboss.narayana.jta.jta for example) then they can then provide the same narayana-properties.xml as they would if they were using the uber jar (example org.jboss.narayana.jta.narayana-jta) without a system property. It should help in a Maven enabled debugger when executing applications running in integration environments like WildFly or Spring where debugging via an uber jar adds an extra layer that makes getting to the real source code harder and code fix cycle slower. > > This should not pose too much of a backwards compatibility issue unless the user has multiple config files with different names (arjuna and jbossts) in their path, were only using arjuna.jar and now jbossts-properties.xml was picked up. But for this reason I propose waiting until Narayana 6. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Feb 5 03:35:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 5 Feb 2016 03:35:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2620) Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2620: -------------------------------- Component/s: Configuration > Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2620 > URL: https://issues.jboss.org/browse/JBTM-2620 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Configuration > Reporter: Tom Jenkinson > Fix For: 6.later > > > With the next Major release of Narayana: > 1. We introduce a new narayana-properties.xml > 2. The narayana-jt* jars not override the properties name in their manifest but we still support that facility in case someone else is using it > 3. We change the search path to look for .xml, narayana-properties.xml, then jbossts-properties.xml and finally arjuna-properties.xml. > > When people use the raw jars (org.jboss.narayana.jta.jta for example) then they can then provide the same narayana-properties.xml as they would if they were using the uber jar (example org.jboss.narayana.jta.narayana-jta) without a system property. It should help in a Maven enabled debugger when executing applications running in integration environments like WildFly or Spring where debugging via an uber jar adds an extra layer that makes getting to the real source code harder and code fix cycle slower. > > This should not pose too much of a backwards compatibility issue unless the user has multiple config files with different names (arjuna and jbossts) in their path, were only using arjuna.jar and now jbossts-properties.xml was picked up. But for this reason I propose waiting until Narayana 6. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Feb 5 03:49:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 5 Feb 2016 03:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2619: -------------------------------- Summary: Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) (was: Create a quickstart to show using of the narayana-osgi-jta bundle) > Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) > -------------------------------------------------------------------------- > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Feb 5 03:54:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 5 Feb 2016 03:54:00 -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: -------------------------------- Forum Reference: https://developer.jboss.org/message/950167?et=watches.email.thread#950167 > 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 Feb 5 03:54:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 5 Feb 2016 03:54:00 -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: -------------------------------- Forum Reference: (was: https://developer.jboss.org/message/950167?et=watches.email.thread#950167) > 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 Feb 5 03:55:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 5 Feb 2016 03:55: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: -------------------------------- Description: >From Ning Jiang (njiang at redhat.com) {quote} 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 {quote} was: >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} > 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) > {quote} > 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 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Feb 5 07:20:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 5 Feb 2016 07:20: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 ] Michael Musgrove updated JBTM-2602: ----------------------------------- Attachment: jstack.tar Java stack traces > 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 > > Attachments: jstack.tar > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Feb 5 07:22:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 5 Feb 2016 07:22: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 ] Michael Musgrove closed JBTM-2602. ---------------------------------- Resolution: Won't Fix The only activity in the stack traces (attached) shows Client003 waiting for a commit to finish. It has passed prepare added its log to an an ibm JDBCStore and is now trying to remove the record but it looks like it is waiting to obtain a connection. Two observations: # why aren't we using connection pools (this looks like a very inefficient way of updating the database) # the stack trace shows the connection attempt is waiting inside the ibm JDBC driver Since it looks like a db comms problem and since we have not seen a subsequent failure (a month ago) I am closing the issue as a spurious failure. > 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 > > Attachments: jstack.tar > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Feb 5 09:46:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 5 Feb 2016 09:46:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2620) Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159287#comment-13159287 ] Tom Jenkinson commented on JBTM-2620: ------------------------------------- Add a WARNING or NOTE in the docs to bring this to the attention of people as much as possible. > Introduce narayana-properties.xml and use as as default property file name, change search order of properties file name > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2620 > URL: https://issues.jboss.org/browse/JBTM-2620 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Configuration > Reporter: Tom Jenkinson > Fix For: 6.later > > > With the next Major release of Narayana: > 1. We introduce a new narayana-properties.xml > 2. The narayana-jt* jars not override the properties name in their manifest but we still support that facility in case someone else is using it > 3. We change the search path to look for .xml, narayana-properties.xml, then jbossts-properties.xml and finally arjuna-properties.xml. > > When people use the raw jars (org.jboss.narayana.jta.jta for example) then they can then provide the same narayana-properties.xml as they would if they were using the uber jar (example org.jboss.narayana.jta.narayana-jta) without a system property. It should help in a Maven enabled debugger when executing applications running in integration environments like WildFly or Spring where debugging via an uber jar adds an extra layer that makes getting to the real source code harder and code fix cycle slower. > > This should not pose too much of a backwards compatibility issue unless the user has multiple config files with different names (arjuna and jbossts) in their path, were only using arjuna.jar and now jbossts-properties.xml was picked up. But for this reason I propose waiting until Narayana 6. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 8 03:59:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 8 Feb 2016 03:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2528) QA testsuite needs documenting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #36 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > QA testsuite needs documenting > ------------------------------ > > Key: JBTM-2528 > URL: https://issues.jboss.org/browse/JBTM-2528 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > We need a document detailing what the tests in the QA testsuite test. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 8 05:31:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 8 Feb 2016 05:31:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2528) QA testsuite needs documenting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2528: ----------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/documentation/pull/36 > QA testsuite needs documenting > ------------------------------ > > Key: JBTM-2528 > URL: https://issues.jboss.org/browse/JBTM-2528 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > We need a document detailing what the tests in the QA testsuite test. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 8 06:17:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 8 Feb 2016 06:17:00 -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 reassigned JBTM-2234: ----------------------------------- Assignee: Tom Jenkinson (was: Amos Feng) > 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: Tom Jenkinson > 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 Mon Feb 8 07:12:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 8 Feb 2016 07:12:00 -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 ] Issue was automatically transitioned when Tom Jenkinson created pull request #34 in GitHub ------------------------------------------------------------------------------------------ Status: Pull Request Sent (was: Open) > 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: Tom Jenkinson > 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 Mon Feb 8 07:15:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 8 Feb 2016 07:15:01 -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 reassigned JBTM-2605: ----------------------------------- Assignee: (was: 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 > 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 Mon Feb 8 07:43:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 8 Feb 2016 07:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2621) Tests that rely on the old perf benchmark harness need porting to use JMH In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2621: -------------------------------------- Summary: Tests that rely on the old perf benchmark harness need porting to use JMH Key: JBTM-2621 URL: https://issues.jboss.org/browse/JBTM-2621 Project: JBoss Transaction Manager Issue Type: Task Components: Performance Testing Affects Versions: 5.2.13.Final Reporter: Michael Musgrove Assignee: Michael Musgrove The relevant tests are: com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance1 com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance3 if there are no others then once ported the old performance benchmark harness can be removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 8 09:30:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 8 Feb 2016 09:30: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 ] Issue was automatically transitioned when Tom Jenkinson created pull request #976 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Reopened) > 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 Mon Feb 8 13:25:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 8 Feb 2016 13:25:00 -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 ] Issue was automatically transitioned when Tom Jenkinson created pull request #977 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > 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 Feb 8 14:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 8 Feb 2016 14:32:00 -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: 6.later (was: 5.next) > 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: 6.later > > > 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 Feb 8 14:33:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 8 Feb 2016 14:33: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 ] Tom Jenkinson updated JBTM-2583: -------------------------------- Fix Version/s: 6.later (was: 5.later) > 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: 6.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 Feb 8 14:33:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 8 Feb 2016 14:33:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2180: -------------------------------- Fix Version/s: 6.later (was: 5.later) > Determine whether or not we should use a specific collections framework > ----------------------------------------------------------------------- > > Key: JBTM-2180 > URL: https://issues.jboss.org/browse/JBTM-2180 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTA, JTS, Performance Testing, REST, Transaction Core > Affects Versions: 5.0.1 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Optional > Fix For: 6.later > > > We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections > There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 9 06:13:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 9 Feb 2016 06:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2622) Implement possible new compensations api from the meeting In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2622: ------------------------------------- Summary: Implement possible new compensations api from the meeting Key: JBTM-2622 URL: https://issues.jboss.org/browse/JBTM-2622 Project: JBoss Transaction Manager Issue Type: Sub-task Components: Compensations Reporter: Gytis Trikleris Fix For: 5.next Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 9 06:15:01 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 9 Feb 2016 06:15:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2622) Implement possible new compensations api from the meeting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2622: ---------------------------------- Attachment: 20160209_105648.jpg > Implement possible new compensations api from the meeting > --------------------------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 9 06:16:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 9 Feb 2016 06:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2622) Implement possible new compensations api from the meeting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris reassigned JBTM-2622: ------------------------------------- Assignee: Gytis Trikleris > Implement possible new compensations api from the meeting > --------------------------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 9 07:11:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 9 Feb 2016 07:11:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2528) QA testsuite needs documenting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2528: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done I have added the documentation to the appendix of our Narayana Guide (Community-only features). > QA testsuite needs documenting > ------------------------------ > > Key: JBTM-2528 > URL: https://issues.jboss.org/browse/JBTM-2528 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > We need a document detailing what the tests in the QA testsuite test. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 9 09:21:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 9 Feb 2016 09:21: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 ] Tom Jenkinson updated JBTM-2580: -------------------------------- Fix Version/s: 5.later (was: 5.next) > 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 > Priority: Minor > Fix For: 5.later > > > 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 Feb 9 09:22:01 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 9 Feb 2016 09:22:01 -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 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 Tue Feb 9 09:23:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 9 Feb 2016 09:23: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 reassigned JBTM-2571: ----------------------------------- Assignee: Amos Feng (was: Gytis Trikleris) > 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: Amos Feng > 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 Feb 9 12:10:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 9 Feb 2016 12:10:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2623) Check Glassfish-to-Narayana interoperability (via JTS). In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2623: -------------------------------------- Summary: Check Glassfish-to-Narayana interoperability (via JTS). Key: JBTM-2623 URL: https://issues.jboss.org/browse/JBTM-2623 Project: JBoss Transaction Manager Issue Type: Task Components: JTS Affects Versions: 5.2.13.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 5.next This task facilitates the resolution of JBTM-223 Check WL-to-JBossTS interoperability (via JTS). Whilst developing a test for recovery with WebLogic I was unable to make progress due to issue \[1\] (basically registering resources for recovery fails). Checking recovery using glassfish may be easier since the source code is readily available and may help with figuring out the correct solution with WL. \[1\] According to [https://docs.oracle.com/cd/E12839_01/web.1111/e13731/jtatxexp.htm#WLJTA279] XA resources can be registered for recovery via a singleton bean that runs at start up and registers them with the WL transaction manager. When I do this I get the exception as shown: {quote} javax.transaction.SystemException: Resource 'Dummy'can be registered only in a server process at org.glassfish.transaction.TransactionManagerImplCommon.registerStaticResource(TransactionManagerImplCommon.java:695) at org.jboss.narayana.RecoveryBean.register(RecoveryBean.java:61) at org.jboss.narayana.RecoveryBean.init(RecoveryBean.java:30) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethod(Jsr250Metadata.java:377) at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethods(Jsr250Metadata.java:352) at com.oracle.pitchfork.intercept.InterceptionMetadata.invokeLifecycleMethods(InterceptionMetadata.java:399) at weblogic.ejb.container.injection.EjbComponentCreatorImpl.invokePostConstruct(EjbComponentCreatorImpl.java:55) at weblogic.ejb.container.manager.SingletonSessionManager.constructAndInitBean(SingletonSessionManager.java:330) at weblogic.ejb.container.manager.SingletonSessionManager.access$300(SingletonSessionManager.java:62) at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.doActualInit(SingletonSessionManager.java:753) at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.initInternal(SingletonSessionManager.java:701) at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.init(SingletonSessionManager.java:588) at weblogic.ejb.container.manager.SingletonSessionManager.init(SingletonSessionManager.java:255) at weblogic.ejb.container.manager.SingletonSessionManager.perhapsInit(SingletonSessionManager.java:251) at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:968) at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:597) at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360) at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:216) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:211) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:73) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258) at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:226) at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:418) at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51) at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200) at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240) at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:210) at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:118) at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:78) at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.glassfish.hk2.utilities.reflection.ReflectionHelper.invoke(ReflectionHelper.java:1017) at org.jvnet.hk2.internal.ClazzCreator.postConstructMe(ClazzCreator.java:388) at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:430) at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456) at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225) at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82) at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488) at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98) at org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:606) at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:77) at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:231) at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:254) at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:413) at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456) at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225) at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82) at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488) at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98) at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:87) at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1162) at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1147) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311) at weblogic.work.ExecuteThread.run(ExecuteThread.java:263) {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 11 09:07:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 11 Feb 2016 09:07: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 ] Work on JBTM-2580 stopped 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: Amos Feng > Priority: Minor > Fix For: 5.later > > > 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 Thu Feb 11 09:09:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 11 Feb 2016 09:09:00 -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=13161751#comment-13161751 ] Tom Jenkinson commented on JBTM-2433: ------------------------------------- I will close this because we have documented the race condition. > 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 Thu Feb 11 09:10:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 11 Feb 2016 09:10:00 -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 closed JBTM-2433. ------------------------------- Fix Version/s: (was: 5.next) Resolution: Won't Fix > 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 > 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 Thu Feb 11 09:30:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 11 Feb 2016 09:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2623) Check Glassfish-to-Narayana interoperability (via JTS). In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2623 started by Tom Jenkinson. ------------------------------------------- > Check Glassfish-to-Narayana interoperability (via JTS). > ------------------------------------------------------- > > Key: JBTM-2623 > URL: https://issues.jboss.org/browse/JBTM-2623 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > This task facilitates the resolution of JBTM-223 Check WL-to-JBossTS interoperability (via JTS). > Whilst developing a test for recovery with WebLogic I was unable to make progress due to issue \[1\] (basically registering resources for recovery fails). Checking recovery using glassfish may be easier since the source code is readily available and may help with figuring out the correct solution with WL. > \[1\] According to [https://docs.oracle.com/cd/E12839_01/web.1111/e13731/jtatxexp.htm#WLJTA279] > XA resources can be registered for recovery via a singleton bean that runs at start up and registers them with the WL transaction manager. When I do this I get the exception as shown: > {quote} > javax.transaction.SystemException: Resource 'Dummy'can be registered only in a server process > at org.glassfish.transaction.TransactionManagerImplCommon.registerStaticResource(TransactionManagerImplCommon.java:695) > at org.jboss.narayana.RecoveryBean.register(RecoveryBean.java:61) > at org.jboss.narayana.RecoveryBean.init(RecoveryBean.java:30) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethod(Jsr250Metadata.java:377) > at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethods(Jsr250Metadata.java:352) > at com.oracle.pitchfork.intercept.InterceptionMetadata.invokeLifecycleMethods(InterceptionMetadata.java:399) > at weblogic.ejb.container.injection.EjbComponentCreatorImpl.invokePostConstruct(EjbComponentCreatorImpl.java:55) > at weblogic.ejb.container.manager.SingletonSessionManager.constructAndInitBean(SingletonSessionManager.java:330) > at weblogic.ejb.container.manager.SingletonSessionManager.access$300(SingletonSessionManager.java:62) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.doActualInit(SingletonSessionManager.java:753) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.initInternal(SingletonSessionManager.java:701) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.init(SingletonSessionManager.java:588) > at weblogic.ejb.container.manager.SingletonSessionManager.init(SingletonSessionManager.java:255) > at weblogic.ejb.container.manager.SingletonSessionManager.perhapsInit(SingletonSessionManager.java:251) > at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:968) > at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:597) > at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360) > at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138) > at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124) > at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:216) > at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:211) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:73) > at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24) > at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258) > at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48) > at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) > at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:226) > at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:418) > at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51) > at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200) > at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) > at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240) > at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) > at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) > at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:210) > at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:118) > at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:78) > at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.glassfish.hk2.utilities.reflection.ReflectionHelper.invoke(ReflectionHelper.java:1017) > at org.jvnet.hk2.internal.ClazzCreator.postConstructMe(ClazzCreator.java:388) > at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:430) > at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456) > at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225) > at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82) > at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98) > at org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:606) > at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:77) > at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:231) > at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:254) > at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:413) > at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456) > at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225) > at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82) > at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:87) > at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1162) > at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1147) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:263) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 11 17:28:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 11 Feb 2016 17:28: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: ------------------------------- Status: Open (was: Pull Request Sent) > 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 Thu Feb 11 17:28:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 11 Feb 2016 17:28: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 ] Work on JBTM-855 started by Tom Jenkinson. ------------------------------------------ > 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: Tom Jenkinson > 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 Thu Feb 11 17:28:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 11 Feb 2016 17:28: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 reassigned JBTM-855: ---------------------------------- Assignee: Amos Feng (was: Tom Jenkinson) > 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 Mon Feb 15 08:48:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 15 Feb 2016 08:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162977#comment-13162977 ] Gytis Trikleris commented on JBTM-2617: --------------------------------------- I've pushed the commit with JMS recovery helper, unit, and integration tests to the development branch. Currently helper is holding the connection with JMS forever, which is not ideal. As a next step I'm going to try to get rid of this issue. > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 15 09:19:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 15 Feb 2016 09:19:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163001#comment-13163001 ] Tom Jenkinson commented on JBTM-2617: ------------------------------------- Feel free to discuss in the forum if you would like some more feedback - not sure which class you are referring to. > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 15 10:28:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 15 Feb 2016 10:28:01 -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 ] Tom Jenkinson updated JBTM-223: ------------------------------- Fix Version/s: 5.next (was: 6.later) > 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: 5.next > > > 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 Mon Feb 15 10:28:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 15 Feb 2016 10:28:02 -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 ] Tom Jenkinson updated JBTM-223: ------------------------------- Priority: Minor (was: Major) > 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 > Priority: Minor > Fix For: 5.next > > > 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 Mon Feb 15 10:28:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 15 Feb 2016 10:28:02 -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 ] Work on JBTM-223 started by Tom Jenkinson. ------------------------------------------ > 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: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > 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 Mon Feb 15 10:29:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 15 Feb 2016 10:29: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 ] Tom Jenkinson reassigned JBTM-223: ---------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > 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 > Priority: Minor > Fix For: 5.next > > > 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 Mon Feb 15 10:29:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 15 Feb 2016 10:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2623) Check Glassfish-to-Narayana interoperability (via JTS). In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2623: ----------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > Check Glassfish-to-Narayana interoperability (via JTS). > ------------------------------------------------------- > > Key: JBTM-2623 > URL: https://issues.jboss.org/browse/JBTM-2623 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > This task facilitates the resolution of JBTM-223 Check WL-to-JBossTS interoperability (via JTS). > Whilst developing a test for recovery with WebLogic I was unable to make progress due to issue \[1\] (basically registering resources for recovery fails). Checking recovery using glassfish may be easier since the source code is readily available and may help with figuring out the correct solution with WL. > \[1\] According to [https://docs.oracle.com/cd/E12839_01/web.1111/e13731/jtatxexp.htm#WLJTA279] > XA resources can be registered for recovery via a singleton bean that runs at start up and registers them with the WL transaction manager. When I do this I get the exception as shown: > {quote} > javax.transaction.SystemException: Resource 'Dummy'can be registered only in a server process > at org.glassfish.transaction.TransactionManagerImplCommon.registerStaticResource(TransactionManagerImplCommon.java:695) > at org.jboss.narayana.RecoveryBean.register(RecoveryBean.java:61) > at org.jboss.narayana.RecoveryBean.init(RecoveryBean.java:30) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethod(Jsr250Metadata.java:377) > at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethods(Jsr250Metadata.java:352) > at com.oracle.pitchfork.intercept.InterceptionMetadata.invokeLifecycleMethods(InterceptionMetadata.java:399) > at weblogic.ejb.container.injection.EjbComponentCreatorImpl.invokePostConstruct(EjbComponentCreatorImpl.java:55) > at weblogic.ejb.container.manager.SingletonSessionManager.constructAndInitBean(SingletonSessionManager.java:330) > at weblogic.ejb.container.manager.SingletonSessionManager.access$300(SingletonSessionManager.java:62) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.doActualInit(SingletonSessionManager.java:753) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.initInternal(SingletonSessionManager.java:701) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.init(SingletonSessionManager.java:588) > at weblogic.ejb.container.manager.SingletonSessionManager.init(SingletonSessionManager.java:255) > at weblogic.ejb.container.manager.SingletonSessionManager.perhapsInit(SingletonSessionManager.java:251) > at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:968) > at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:597) > at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360) > at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138) > at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124) > at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:216) > at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:211) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:73) > at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24) > at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258) > at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48) > at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) > at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:226) > at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:418) > at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51) > at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200) > at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) > at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240) > at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) > at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) > at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:210) > at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:118) > at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:78) > at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.glassfish.hk2.utilities.reflection.ReflectionHelper.invoke(ReflectionHelper.java:1017) > at org.jvnet.hk2.internal.ClazzCreator.postConstructMe(ClazzCreator.java:388) > at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:430) > at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456) > at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225) > at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82) > at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98) > at org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:606) > at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:77) > at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:231) > at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:254) > at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:413) > at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456) > at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225) > at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82) > at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:87) > at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1162) > at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1147) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:263) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 15 10:30:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 15 Feb 2016 10:30: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 stopped 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 > 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 Mon Feb 15 11:01:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 15 Feb 2016 11:01:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163086#comment-13163086 ] Gytis Trikleris commented on JBTM-2617: --------------------------------------- I've just pushed the fix for this. Instead of holding connection in the recovery helper forever, I've implemented XAResource interface for it. Recovery helper acts as a proxy for JMS XAResource during recovery. It then creates and closes connections when needed. https://github.com/gytis/narayana/commit/781869d9c46ca994efe31f8acc773c4658e326e0 > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 15 11:06:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 15 Feb 2016 11:06:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163091#comment-13163091 ] Tom Jenkinson commented on JBTM-2617: ------------------------------------- It looks like it would perform (really) badly. May I suggest you get hold of the connection in recover(TMSTARTRSCAN) and release it in recover(TMENDRSCAN) - happy to discuss on forum if its easier. > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 15 11:10:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 15 Feb 2016 11:10:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163094#comment-13163094 ] Gytis Trikleris commented on JBTM-2617: --------------------------------------- My initial plan was to do this in between recover(TMSTARTRSCAN) and recover(TMENDRSCAN). However, I wasn't sure that all other calls e.g. commit are only executed in that time frame. If they're not, connection wouldn't be active and the call would fail. I agree with the performance, however my thought was that since it's during the recovery time it's not an issue. > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 15 11:33:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 15 Feb 2016 11:33:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163118#comment-13163118 ] Tom Jenkinson commented on JBTM-2617: ------------------------------------- I suppose it depends how the driver is implemented but if its not pooling and established a connection and shut it down everytime it would have an effect on the overall life span of the server. As XARecoveryModule is last in the list https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/narayana-jts-idlj/src/main/resources/jbossts-properties.xml#L96 TMENDRSCAN will be called after transaction recovery IMO it should therefore be safe. > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 15 22:58:00 2016 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 15 Feb 2016 22:58:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf In-Reply-To: References: Message-ID: Amos Feng created JBTM-2624: ------------------------------- Summary: Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf Key: JBTM-2624 URL: https://issues.jboss.org/browse/JBTM-2624 Project: JBoss Transaction Manager Issue Type: Feature Request Reporter: Amos Feng Assignee: Amos Feng Priority: Minor {quote} We have several management ways in Karaf : * mbeans (no need to rewrap them) * shell commands * a servlet for the felix web console (used by the community) * a hawtio plugin (used by fuse) The first two are the most important imho. {quote} the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 16 04:19:01 2016 From: issues at jboss.org (Hayk Hovsepyan (JIRA)) Date: Tue, 16 Feb 2016 04:19:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2578) Make "junit-jdbc-ncl-testsuite" testsuite of Narayana/qa compatible with IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hayk Hovsepyan reassigned JBTM-2578: ------------------------------------ Assignee: Daniel Simko (was: Hayk Hovsepyan) > Make "junit-jdbc-ncl-testsuite" testsuite of Narayana/qa compatible with IPv6 > ----------------------------------------------------------------------------- > > Key: JBTM-2578 > URL: https://issues.jboss.org/browse/JBTM-2578 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Hayk Hovsepyan > Assignee: Daniel Simko > > Currently JDBC tests from "junit-jdbc-ncl-testsuite" testsuite of narayana/qa tsts fail while running on pure IPv6 machine. > The reason is that it is designed to connect to databases via IPv4 protocol, and there are hostnames of DB's specified in project. > It needs to be modified to connect to databases via IPv6 addresses protocol and run tests on pure Ipv6 machine. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 16 05:29:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 16 Feb 2016 05:29:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163401#comment-13163401 ] Tom Jenkinson commented on JBTM-2624: ------------------------------------- I think we should look to expose the same functionality as we have in the WildFly CLI. /cc [~mmusgrov] for an idea on where to get the list of functionality. We need at least probe: https://github.com/wildfly/wildfly/blob/0c68aa0ebef3682e9ded4b473e24463b3e31af07/transactions/src/main/java/org/jboss/as/txn/subsystem/LogStoreDefinition.java#L59 But we likely need others too: https://github.com/wildfly/wildfly/blob/0c68aa0ebef3682e9ded4b473e24463b3e31af07/transactions/src/main/java/org/jboss/as/txn/subsystem/LogStoreConstants.java#L43 > Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf > ----------------------------------------------------------------------------------- > > Key: JBTM-2624 > URL: https://issues.jboss.org/browse/JBTM-2624 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > {quote} > We have several management ways in Karaf : > * mbeans (no need to rewrap them) > * shell commands > * a servlet for the felix web console (used by the community) > * a hawtio plugin (used by fuse) > The first two are the most important imho. > {quote} > the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 16 05:30:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 16 Feb 2016 05:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163402#comment-13163402 ] Tom Jenkinson commented on JBTM-2624: ------------------------------------- Lets create a forum topic to define the scope. But first try to get an inventory of the available operations and include that in your posting. > Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf > ----------------------------------------------------------------------------------- > > Key: JBTM-2624 > URL: https://issues.jboss.org/browse/JBTM-2624 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > {quote} > We have several management ways in Karaf : > * mbeans (no need to rewrap them) > * shell commands > * a servlet for the felix web console (used by the community) > * a hawtio plugin (used by fuse) > The first two are the most important imho. > {quote} > the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 16 05:43:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 16 Feb 2016 05:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163413#comment-13163413 ] Gytis Trikleris commented on JBTM-2617: --------------------------------------- You're correct. Workflow seems to be safe to create/remove connection only on XAResource.recovery calls with TMSTARTRSCAN/TMENDRSCAN attributes. > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 16 06:14:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 16 Feb 2016 06:14:00 -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: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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: Tom Jenkinson > 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 Feb 16 06:24:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 16 Feb 2016 06:24:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163434#comment-13163434 ] Gytis Trikleris commented on JBTM-2617: --------------------------------------- I've changed the recovery helper: https://github.com/gytis/narayana/commit/3508ba6da29a1febea98035d017dca2d4db58996 > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 16 09:07:01 2016 From: issues at jboss.org (Jive JIRA Integration (JIRA)) Date: Tue, 16 Feb 2016 09:07:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2622) Implement possible new compensations api from the meeting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jive JIRA Integration updated JBTM-2622: ---------------------------------------- Forum Reference: https://developer.jboss.org/message/948585#948585 > Implement possible new compensations api from the meeting > --------------------------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 16 09:19:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 16 Feb 2016 09:19:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2619 started by Tom Jenkinson. ------------------------------------------- > Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) > -------------------------------------------------------------------------- > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 16 09:20:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 16 Feb 2016 09:20:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2619: ----------------------------------- Assignee: Amos Feng (was: Tom Jenkinson) > Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) > -------------------------------------------------------------------------- > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 16 18:26:00 2016 From: issues at jboss.org (RH Bugzilla Integration (JIRA)) Date: Tue, 16 Feb 2016 18:26:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2575) When checking for orphaned subordinate transactions in the middle of a tree branches that are eligible for orphan detection will be rolled back In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163977#comment-13163977 ] RH Bugzilla Integration commented on JBTM-2575: ----------------------------------------------- Brad Maxwell changed the Status of [bug 1289386|https://bugzilla.redhat.com/show_bug.cgi?id=1289386] from ASSIGNED to MODIFIED > When checking for orphaned subordinate transactions in the middle of a tree branches that are eligible for orphan detection will be rolled back > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2575 > URL: https://issues.jboss.org/browse/JBTM-2575 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 4.17.31, 5.2.9.Final > > > There is a check in the subordinate orphan detection that not only checks for matching gtrid but also for matching subordinate name. This will not match correctly for an intermediary node. E.g. > a->b b->c > When b scans c the xid it gets back will have subordinate name of c, b will look in its object store and match the subordinate on gtrid but the subordinate node ID in b subordinateatomicaction will be "b". > This check is actually superfluous anyway. We already know that the Xid returned from c was for b because of transport level checks. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 17 04:15:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 17 Feb 2016 04:15:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2402) Karaf Integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2402: -------------------------------- Summary: Karaf Integration (was: Create a quickstart and some docs that show how to use our OSGi bundle) > Karaf Integration > ----------------- > > Key: JBTM-2402 > URL: https://issues.jboss.org/browse/JBTM-2402 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Application Server Integration, Demonstrator, Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.later > > > We should create a quickstart to demonstrate how to install and use our bundle. It should also be described in our project (community) manual. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 17 04:16:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 17 Feb 2016 04:16:00 -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: -------------------------------- Parent: JBTM-2402 Issue Type: Sub-task (was: Task) > 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: Sub-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 Wed Feb 17 04:16:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 17 Feb 2016 04:16:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2619: -------------------------------- Parent: JBTM-2402 Issue Type: Sub-task (was: Task) > Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) > -------------------------------------------------------------------------- > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 18 05:01:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 18 Feb 2016 05:01:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #978 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 18 05:01:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 18 Feb 2016 05:01: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 ] Issue was automatically transitioned when Gytis Trikleris created pull request #978 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > 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 Thu Feb 18 05:27:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 18 Feb 2016 05:27:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2622) Implement possible new compensations api from the meeting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2622 started by Gytis Trikleris. --------------------------------------------- > Implement possible new compensations api from the meeting > --------------------------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 18 05:48:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 18 Feb 2016 05:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164844#comment-13164844 ] Michael Musgrove commented on JBTM-2624: ---------------------------------------- [~tomjenkinson] [~zhfeng] The CLI is documented in the [tools|http://narayana.io/docs/product/index.html#d0e2725] of our product manual. > Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf > ----------------------------------------------------------------------------------- > > Key: JBTM-2624 > URL: https://issues.jboss.org/browse/JBTM-2624 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > {quote} > We have several management ways in Karaf : > * mbeans (no need to rewrap them) > * shell commands > * a servlet for the felix web console (used by the community) > * a hawtio plugin (used by fuse) > The first two are the most important imho. > {quote} > the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 18 05:48:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 18 Feb 2016 05:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164844#comment-13164844 ] Michael Musgrove edited comment on JBTM-2624 at 2/18/16 5:47 AM: ----------------------------------------------------------------- [~tomjenkinson] [~zhfeng] The CLI is documented in the [tools section|http://narayana.io/docs/product/index.html#d0e2725] of our product manual. was (Author: mmusgrov): [~tomjenkinson] [~zhfeng] The CLI is documented in the [tools|http://narayana.io/docs/product/index.html#d0e2725] of our product manual. > Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf > ----------------------------------------------------------------------------------- > > Key: JBTM-2624 > URL: https://issues.jboss.org/browse/JBTM-2624 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > > {quote} > We have several management ways in Karaf : > * mbeans (no need to rewrap them) > * shell commands > * a servlet for the felix web console (used by the community) > * a hawtio plugin (used by fuse) > The first two are the most important imho. > {quote} > the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 18 11:59:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 18 Feb 2016 11:59: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 ] Issue was automatically transitioned when Gytis Trikleris created pull request #979 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > 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 Thu Feb 18 11:59:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 18 Feb 2016 11:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2622) Implement possible new compensations api from the meeting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Gytis Trikleris created pull request #979 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Implement possible new compensations api from the meeting > --------------------------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Feb 19 09:38:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 19 Feb 2016 09:38: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: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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 Mon Feb 22 04:19:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 22 Feb 2016 04:19: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 ] Tom Jenkinson updated JBTM-2583: -------------------------------- Description: 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. * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed was: 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) > 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: 6.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. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 22 08:59:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 22 Feb 2016 08:59:00 -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 ] Gytis Trikleris closed JBTM-2522. --------------------------------- Fix Version/s: (was: 5.next) Resolution: Rejected > 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 > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 22 09:30:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 22 Feb 2016 09:30: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 ] Tom Jenkinson updated JBTM-2583: -------------------------------- Issue Type: Enhancement (was: Feature Request) > 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: Enhancement > 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. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 22 09:30:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 22 Feb 2016 09:30:01 -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 ] Tom Jenkinson updated JBTM-2583: -------------------------------- Fix Version/s: 5.later (was: 6.later) > 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: Enhancement > 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. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 22 09:31:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 22 Feb 2016 09:31: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=13166376#comment-13166376 ] Tom Jenkinson commented on JBTM-2583: ------------------------------------- Lowering impact to enhancement/5 series as it can be added as a new filter that can be enabled as per user demand. > 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: Enhancement > 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. > > * In the case where the recovery manager and transaction manager are co-located this negates the need for a timeout based process entirely > * In the case where the recovery manager and transaction manager are not in the same JVM process, the current behaviour of timeout based orphan detection MUST still be employed -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 22 10:08:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 22 Feb 2016 10:08: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:all-tabpanel ] Work on JBTM-2610 started by Gytis Trikleris. --------------------------------------------- > 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 Feb 22 10:13:01 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 22 Feb 2016 10:13:01 -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 ] Issue was automatically transitioned when Gytis Trikleris created pull request #980 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > 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 Feb 23 05:58:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 23 Feb 2016 05:58: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 ] Work on JBTM-2603 started by Gytis Trikleris. --------------------------------------------- > 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 Tue Feb 23 06:51:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 06:51:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2625) Errors during reading the object store state may result in incorrect presumed abort semantics being activated In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2625: ----------------------------------- Summary: Errors during reading the object store state may result in incorrect presumed abort semantics being activated Key: JBTM-2625 URL: https://issues.jboss.org/browse/JBTM-2625 Project: JBoss Transaction Manager Issue Type: Bug Components: Transaction Core Reporter: Tom Jenkinson Assignee: Tom Jenkinson In the method getOsStatus the error handling ignores various errors that may occur and proceeds to return ActionStatus.ABORTED Method is defined here: https://github.com/jbosstm/narayana/blob/5.2.13.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/recovery/ActionStatusService.java#L245 The method is intended such that if we get a successful access to the ObjectStore but can?t find any states corresponding to the Uid (vector size is 0) then we can return aborted due to presumed abort. Currently if we have a failure during lookup we may also have vector size of 0 but that doesn?t mean the transaction has aborted; it just means we had a failure and should retry later. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 06:52:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 06:52:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2625) Errors during reading the object store state may result in incorrect presumed abort semantics being activated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Tom Jenkinson created pull request #981 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Errors during reading the object store state may result in incorrect presumed abort semantics being activated > ------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2625 > URL: https://issues.jboss.org/browse/JBTM-2625 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > In the method getOsStatus the error handling ignores various errors that may occur and proceeds to return ActionStatus.ABORTED > Method is defined here: > https://github.com/jbosstm/narayana/blob/5.2.13.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/recovery/ActionStatusService.java#L245 > The method is intended such that if we get a successful access to the ObjectStore but can?t find any states corresponding to the Uid (vector size is 0) then we can return aborted due to presumed abort. > Currently if we have a failure during lookup we may also have vector size of 0 but that doesn?t mean the transaction has aborted; it just means we had a failure and should retry later. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 07:03:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 23 Feb 2016 07:03: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:all-tabpanel ] Gytis Trikleris updated JBTM-2610: ---------------------------------- Status: Resolved (was: Pull Request Sent) Release Notes Text: I've added logging once the exception is caught. Resolution: 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 Tue Feb 23 07:05:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 23 Feb 2016 07:05: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 ] Issue was automatically transitioned when Gytis Trikleris created pull request #982 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Coding In Progress) > 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 Tue Feb 23 07:27:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 07:27:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2625) Errors during reading the object store state may result in incorrect presumed abort semantics being activated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13166934#comment-13166934 ] Tom Jenkinson commented on JBTM-2625: ------------------------------------- If we return ActionStatus.INVALID it has the effect of triggering a retry so proposing that as the fix. > Errors during reading the object store state may result in incorrect presumed abort semantics being activated > ------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2625 > URL: https://issues.jboss.org/browse/JBTM-2625 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > In the method getOsStatus the error handling ignores various errors that may occur and proceeds to return ActionStatus.ABORTED > Method is defined here: > https://github.com/jbosstm/narayana/blob/5.2.13.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/recovery/ActionStatusService.java#L245 > The method is intended such that if we get a successful access to the ObjectStore but can?t find any states corresponding to the Uid (vector size is 0) then we can return aborted due to presumed abort. > Currently if we have a failure during lookup we may also have vector size of 0 but that doesn?t mean the transaction has aborted; it just means we had a failure and should retry later. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 09:15:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 09:15:01 -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: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) > 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 Tue Feb 23 09:28:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 23 Feb 2016 09:28:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2626) Journal Store QA test failures In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2626: -------------------------------------- Summary: Journal Store QA test failures Key: JBTM-2626 URL: https://issues.jboss.org/browse/JBTM-2626 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Affects Versions: 5.2.13.Final Reporter: Michael Musgrove Assignee: Michael Musgrove There was a single test failure on each of the following CI runs: http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 09:41:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 09:41:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2626) Journal Store QA test failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2626: -------------------------------- Fix Version/s: 5.next > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > There was a single test failure on each of the following CI runs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 09:41:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 09:41:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2626) Journal Store QA test failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2626: -------------------------------- Priority: Critical (was: Major) > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > There was a single test failure on each of the following CI runs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 09:42:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 09:42:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2626) Journal Store QA test failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167059#comment-13167059 ] Tom Jenkinson commented on JBTM-2626: ------------------------------------- Hi Mike, Please can you take a look as it seems quite frequent to leave without a root cause? Thanks, Tom > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > There was a single test failure on each of the following CI runs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 09:42:01 2016 From: issues at jboss.org (=?UTF-8?Q?Ond=C5=99ej_Chaloupka_=28JIRA=29?=) Date: Tue, 23 Feb 2016 09:42:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2578) Make "junit-jdbc-ncl-testsuite" testsuite of Narayana/qa compatible with IPv6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ond?ej Chaloupka updated JBTM-2578: ----------------------------------- Priority: Critical (was: Major) > Make "junit-jdbc-ncl-testsuite" testsuite of Narayana/qa compatible with IPv6 > ----------------------------------------------------------------------------- > > Key: JBTM-2578 > URL: https://issues.jboss.org/browse/JBTM-2578 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Hayk Hovsepyan > Assignee: Daniel Simko > Priority: Critical > > Currently JDBC tests from "junit-jdbc-ncl-testsuite" testsuite of narayana/qa tsts fail while running on pure IPv6 machine. > The reason is that it is designed to connect to databases via IPv4 protocol, and there are hostnames of DB's specified in project. > It needs to be modified to connect to databases via IPv6 addresses protocol and run tests on pure Ipv6 machine. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 09:49:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 23 Feb 2016 09:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2626) Journal Store QA test failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167073#comment-13167073 ] Michael Musgrove commented on JBTM-2626: ---------------------------------------- A different test failed on each CI run. I will be adding the output from the failures and if they are sufficiently different I will create sub-tasks for them > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > There was a single test failure on each of the following CI runs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 10:30:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2625) Errors during reading the object store state may result in incorrect presumed abort semantics being activated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2625: -------------------------------- Priority: Blocker (was: Major) > Errors during reading the object store state may result in incorrect presumed abort semantics being activated > ------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2625 > URL: https://issues.jboss.org/browse/JBTM-2625 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > > In the method getOsStatus the error handling ignores various errors that may occur and proceeds to return ActionStatus.ABORTED > Method is defined here: > https://github.com/jbosstm/narayana/blob/5.2.13.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/recovery/ActionStatusService.java#L245 > The method is intended such that if we get a successful access to the ObjectStore but can?t find any states corresponding to the Uid (vector size is 0) then we can return aborted due to presumed abort. > Currently if we have a failure during lookup we may also have vector size of 0 but that doesn?t mean the transaction has aborted; it just means we had a failure and should retry later. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 10:30:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 23 Feb 2016 10:30:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2626) Journal Store QA test failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2626: ----------------------------------- Description: There was a single test failure on each of the following CI runs: crashrecovery05_2 CrashRecovery05_2_Test080 failed on job http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console crashrecovery05_2 CrashRecovery05_2_Test080 failed on job http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console jtatests01 JTATests01_Test006 failed on job http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console was: There was a single test failure on each of the following CI runs: http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > There was a single test failure on each of the following CI runs: > crashrecovery05_2 CrashRecovery05_2_Test080 failed on job http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console > crashrecovery05_2 CrashRecovery05_2_Test080 failed on job http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console > jtatests01 JTATests01_Test006 failed on job http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 10:31:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:31:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2625) Errors during reading the object store state may result in incorrect presumed abort semantics being activated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2625: -------------------------------- Fix Version/s: 5.next > Errors during reading the object store state may result in incorrect presumed abort semantics being activated > ------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2625 > URL: https://issues.jboss.org/browse/JBTM-2625 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > In the method getOsStatus the error handling ignores various errors that may occur and proceeds to return ActionStatus.ABORTED > Method is defined here: > https://github.com/jbosstm/narayana/blob/5.2.13.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/recovery/ActionStatusService.java#L245 > The method is intended such that if we get a successful access to the ObjectStore but can?t find any states corresponding to the Uid (vector size is 0) then we can return aborted due to presumed abort. > Currently if we have a failure during lookup we may also have vector size of 0 but that doesn?t mean the transaction has aborted; it just means we had a failure and should retry later. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 10:33:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 23 Feb 2016 10:33:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2626) Journal Store QA test failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2626: ----------------------------------- Description: There was a single test failure on each of the following CI runs: crashrecovery05_2 CrashRecovery05_2_Test080 failed on the idlj run on the jobs: http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console and jtatests01 JTATests01_Test006 failed on the jacorb run of job: http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console was: There was a single test failure on each of the following CI runs: crashrecovery05_2 CrashRecovery05_2_Test080 failed on job http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console crashrecovery05_2 CrashRecovery05_2_Test080 failed on job http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console jtatests01 JTATests01_Test006 failed on job http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > There was a single test failure on each of the following CI runs: > crashrecovery05_2 CrashRecovery05_2_Test080 failed on the idlj run on the jobs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console > and jtatests01 JTATests01_Test006 failed on the jacorb run of job: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 10:38:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:38: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 ] Tom Jenkinson reopened JBTM-2608: --------------------------------- > 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: 5.next > > > 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 Feb 23 10:38:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:38: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 ] Tom Jenkinson updated JBTM-2608: -------------------------------- Fix Version/s: (was: 5.next) > 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 Tue Feb 23 10:38:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:38: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 ] Tom Jenkinson closed JBTM-2608. ------------------------------- 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 > > 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 Feb 23 10:39:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:39: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 reopened JBTM-2602: --------------------------------- > 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 > > Attachments: jstack.tar > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 10:39:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:39: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: -------------------------------- Fix Version/s: (was: 5.next) > 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 > Attachments: jstack.tar > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 10:39:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:39: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 closed JBTM-2602. ------------------------------- Resolution: Won't Fix > 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 > Attachments: jstack.tar > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 10:43:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:43: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 ] Tom Jenkinson updated JBTM-2616: -------------------------------- Fix Version/s: 5.later (was: 5.next) > 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.later > > > 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 Tue Feb 23 10:43:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2617: -------------------------------- Fix Version/s: 5.later (was: 5.next) > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 10:43:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:43: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:comment-tabpanel&focusedCommentId=13167127#comment-13167127 ] Tom Jenkinson commented on JBTM-2616: ------------------------------------- Needs to be classed as feature request during merge so that we don't release in 5.2.x (fine to leave as subtask) > 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.later > > > 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 Tue Feb 23 10:43:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:43:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167128#comment-13167128 ] Tom Jenkinson commented on JBTM-2617: ------------------------------------- Needs to be classed as feature request during merge so that we don't release in 5.2.x (fine to leave as subtask) > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 10:48:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:48:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2618) Improve concurrent behavior of HornetqJournalStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2618: -------------------------------- Fix Version/s: 5.next > Improve concurrent behavior of HornetqJournalStore > -------------------------------------------------- > > Key: JBTM-2618 > URL: https://issues.jboss.org/browse/JBTM-2618 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Luis Barreiro > Fix For: 5.next > > > Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. > When there is a high number of threads, some will be block reducing the overall throughput and increasing response times on the whole system. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 10:49:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2625) Errors during reading the object store state may result in incorrect presumed abort semantics being activated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2625: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Errors during reading the object store state may result in incorrect presumed abort semantics being activated > ------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2625 > URL: https://issues.jboss.org/browse/JBTM-2625 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > In the method getOsStatus the error handling ignores various errors that may occur and proceeds to return ActionStatus.ABORTED > Method is defined here: > https://github.com/jbosstm/narayana/blob/5.2.13.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/recovery/ActionStatusService.java#L245 > The method is intended such that if we get a successful access to the ObjectStore but can?t find any states corresponding to the Uid (vector size is 0) then we can return aborted due to presumed abort. > Currently if we have a failure during lookup we may also have vector size of 0 but that doesn?t mean the transaction has aborted; it just means we had a failure and should retry later. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 10:50:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 10:50:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2618) Improve concurrent behavior of HornetqJournalStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2618: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Improve concurrent behavior of HornetqJournalStore > -------------------------------------------------- > > Key: JBTM-2618 > URL: https://issues.jboss.org/browse/JBTM-2618 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Luis Barreiro > Fix For: 5.next > > > Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. > When there is a high number of threads, some will be block reducing the overall throughput and increasing response times on the whole system. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 12:50:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 23 Feb 2016 12:50:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2626) Journal Store QA test failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2626: ----------------------------------- Attachment: jstack.25002.jacorb The java stack trace for test JTATests01_Test006 failed on the jacorb run. The test launches 32 worker threads each running 1000 transactions. Trace level logging has been enabled and there is gigabyte worth of logging output. My analysis shows that the test is ticking along happily at its own (glacial) pace but is being slowed by the amount of trace logging it needs to do. The trace shows: 17 threads waiting on org.omg.CosTransactions.Status 6 threads waiting for the logger 1 thread holding the lock on both of the above but is not blocked The fixes are: - increase the task runtime - decrease the work performed the test - disable logging for load tests > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > Attachments: jstack.25002.jacorb > > > There was a single test failure on each of the following CI runs: > crashrecovery05_2 CrashRecovery05_2_Test080 failed on the idlj run on the jobs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console > and jtatests01 JTATests01_Test006 failed on the jacorb run of job: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Feb 23 12:54:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 23 Feb 2016 12:54:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2626) Journal Store QA test failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13167222#comment-13167222 ] Tom Jenkinson commented on JBTM-2626: ------------------------------------- Ouch - recommend logging at WARN for this test if possible to isolate it. > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > Attachments: jstack.25002.jacorb > > > There was a single test failure on each of the following CI runs: > crashrecovery05_2 CrashRecovery05_2_Test080 failed on the idlj run on the jobs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console > and jtatests01 JTATests01_Test006 failed on the jacorb run of job: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 24 06:16:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 24 Feb 2016 06:16:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2627) Document JMS integration functionality In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2627: ------------------------------------- Summary: Document JMS integration functionality Key: JBTM-2627 URL: https://issues.jboss.org/browse/JBTM-2627 Project: JBoss Transaction Manager Issue Type: Task Components: Documentation Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.later New JMS integration feature needs documentation. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 24 06:19:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 24 Feb 2016 06:19: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: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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 Wed Feb 24 09:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2618) Improve concurrent behavior of HornetqJournalStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2618. ------------------------------- > Improve concurrent behavior of HornetqJournalStore > -------------------------------------------------- > > Key: JBTM-2618 > URL: https://issues.jboss.org/browse/JBTM-2618 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Luis Barreiro > Fix For: 5.2.14.Final > > > Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. > When there is a high number of threads, some will be block reducing the overall throughput and increasing response times on the whole system. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 24 09:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2625) Errors during reading the object store state may result in incorrect presumed abort semantics being activated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2625. ------------------------------- > Errors during reading the object store state may result in incorrect presumed abort semantics being activated > ------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2625 > URL: https://issues.jboss.org/browse/JBTM-2625 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.2.14.Final > > > In the method getOsStatus the error handling ignores various errors that may occur and proceeds to return ActionStatus.ABORTED > Method is defined here: > https://github.com/jbosstm/narayana/blob/5.2.13.Final/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/recovery/ActionStatusService.java#L245 > The method is intended such that if we get a successful access to the ObjectStore but can?t find any states corresponding to the Uid (vector size is 0) then we can return aborted due to presumed abort. > Currently if we have a failure during lookup we may also have vector size of 0 but that doesn?t mean the transaction has aborted; it just means we had a failure and should retry later. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 24 09:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:32: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:all-tabpanel ] Tom Jenkinson closed JBTM-2610. ------------------------------- > 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.2.14.Final > > > {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 Wed Feb 24 09:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:32: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 ] Tom Jenkinson closed JBTM-2603. ------------------------------- > 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.2.14.Final > > > 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 Wed Feb 24 09:33:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:01 -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 closed JBTM-2409. ------------------------------- > 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.2.14.Final > > 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 Wed Feb 24 09:33:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:01 -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 closed JBTM-2234. ------------------------------- > 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: Tom Jenkinson > Priority: Minor > Fix For: 5.2.14.Final > > > 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 Wed Feb 24 09:33:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2626) Journal Store QA test failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2626: -------------------------------- Fix Version/s: 5.next (was: 5.2.14.Final) > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > Attachments: jstack.25002.jacorb > > > There was a single test failure on each of the following CI runs: > crashrecovery05_2 CrashRecovery05_2_Test080 failed on the idlj run on the jobs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console > and jtatests01 JTATests01_Test006 failed on the jacorb run of job: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 24 09:33:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2623) Check Glassfish-to-Narayana interoperability (via JTS). In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2623: -------------------------------- Fix Version/s: 5.next (was: 5.2.14.Final) > Check Glassfish-to-Narayana interoperability (via JTS). > ------------------------------------------------------- > > Key: JBTM-2623 > URL: https://issues.jboss.org/browse/JBTM-2623 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > This task facilitates the resolution of JBTM-223 Check WL-to-JBossTS interoperability (via JTS). > Whilst developing a test for recovery with WebLogic I was unable to make progress due to issue \[1\] (basically registering resources for recovery fails). Checking recovery using glassfish may be easier since the source code is readily available and may help with figuring out the correct solution with WL. > \[1\] According to [https://docs.oracle.com/cd/E12839_01/web.1111/e13731/jtatxexp.htm#WLJTA279] > XA resources can be registered for recovery via a singleton bean that runs at start up and registers them with the WL transaction manager. When I do this I get the exception as shown: > {quote} > javax.transaction.SystemException: Resource 'Dummy'can be registered only in a server process > at org.glassfish.transaction.TransactionManagerImplCommon.registerStaticResource(TransactionManagerImplCommon.java:695) > at org.jboss.narayana.RecoveryBean.register(RecoveryBean.java:61) > at org.jboss.narayana.RecoveryBean.init(RecoveryBean.java:30) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethod(Jsr250Metadata.java:377) > at com.oracle.pitchfork.inject.Jsr250Metadata.invokeLifecycleMethods(Jsr250Metadata.java:352) > at com.oracle.pitchfork.intercept.InterceptionMetadata.invokeLifecycleMethods(InterceptionMetadata.java:399) > at weblogic.ejb.container.injection.EjbComponentCreatorImpl.invokePostConstruct(EjbComponentCreatorImpl.java:55) > at weblogic.ejb.container.manager.SingletonSessionManager.constructAndInitBean(SingletonSessionManager.java:330) > at weblogic.ejb.container.manager.SingletonSessionManager.access$300(SingletonSessionManager.java:62) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.doActualInit(SingletonSessionManager.java:753) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.initInternal(SingletonSessionManager.java:701) > at weblogic.ejb.container.manager.SingletonSessionManager$SingletonLifecycleManager.init(SingletonSessionManager.java:588) > at weblogic.ejb.container.manager.SingletonSessionManager.init(SingletonSessionManager.java:255) > at weblogic.ejb.container.manager.SingletonSessionManager.perhapsInit(SingletonSessionManager.java:251) > at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:968) > at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:597) > at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360) > at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138) > at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124) > at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:216) > at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:211) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:73) > at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24) > at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) > at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258) > at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48) > at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) > at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:226) > at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:418) > at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51) > at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200) > at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30) > at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240) > at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169) > at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123) > at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:210) > at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:118) > at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:78) > at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.glassfish.hk2.utilities.reflection.ReflectionHelper.invoke(ReflectionHelper.java:1017) > at org.jvnet.hk2.internal.ClazzCreator.postConstructMe(ClazzCreator.java:388) > at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:430) > at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456) > at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225) > at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82) > at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98) > at org.jvnet.hk2.internal.ServiceLocatorImpl.getService(ServiceLocatorImpl.java:606) > at org.jvnet.hk2.internal.ThreeThirtyResolver.resolve(ThreeThirtyResolver.java:77) > at org.jvnet.hk2.internal.ClazzCreator.resolve(ClazzCreator.java:231) > at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:254) > at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:413) > at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456) > at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225) > at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:82) > at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2488) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:98) > at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:87) > at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1162) > at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1147) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:263) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 24 09:33:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2622) Implement possible new compensations api from the meeting In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2622: -------------------------------- Fix Version/s: 5.next (was: 5.2.14.Final) > Implement possible new compensations api from the meeting > --------------------------------------------------------- > > Key: JBTM-2622 > URL: https://issues.jboss.org/browse/JBTM-2622 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Compensations > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: 20160209_105648.jpg > > > Implement mock api from the meeting in order to be able to have a discussion about it on the forum. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 24 09:33:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:02 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2619) Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2619: -------------------------------- Fix Version/s: 5.next (was: 5.2.14.Final) > Create a quickstart to show using of the narayana-osgi-jta bundle (karaf) > -------------------------------------------------------------------------- > > Key: JBTM-2619 > URL: https://issues.jboss.org/browse/JBTM-2619 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > It should be with the recovery example -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 24 09:33:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:02 -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.14.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 Wed Feb 24 09:33:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:02 -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.14.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 > 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 Wed Feb 24 09:33:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:02 -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.14.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 Wed Feb 24 09:33:02 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:02 -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.14.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: Amos Feng > 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 Wed Feb 24 09:33:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:03 -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.14.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: Sub-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 Wed Feb 24 09:33:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:03 -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.14.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 Wed Feb 24 09:33:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:03 -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.14.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 Wed Feb 24 09:33:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:03 -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.14.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 Wed Feb 24 09:33:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33: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.14.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 Wed Feb 24 09:33:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33: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.14.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 Wed Feb 24 09:33:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33: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.14.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 Wed Feb 24 09:33:04 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 24 Feb 2016 09:33:04 -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 ] Tom Jenkinson updated JBTM-223: ------------------------------- Fix Version/s: 5.next (was: 5.2.14.Final) > 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 > Priority: Minor > Fix For: 5.next > > > 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 Feb 24 09:49:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 24 Feb 2016 09:49:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2298) Write an atomic app that uses JTS and JacORB containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2298: ---------------------------------- Summary: Write an atomic app that uses JTS and JacORB containers (was: Use Project Atomic for docker image(s)) > Write an atomic app that uses JTS and JacORB containers > ------------------------------------------------------- > > 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 Wed Feb 24 09:49:01 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 24 Feb 2016 09:49:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2298) Write an atomic app that uses JTS and JacORB containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2298: ---------------------------------- Component/s: (was: XTS) (was: REST) > Write an atomic app that uses JTS and JacORB containers > ------------------------------------------------------- > > Key: JBTM-2298 > URL: https://issues.jboss.org/browse/JBTM-2298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, JTS > 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 Wed Feb 24 09:50:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 24 Feb 2016 09:50:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2298) Write an atomic app that uses JTS and JacORB containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBTM-2298 started by Gytis Trikleris. --------------------------------------------- > Write an atomic app that uses JTS and JacORB containers > ------------------------------------------------------- > > Key: JBTM-2298 > URL: https://issues.jboss.org/browse/JBTM-2298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, JTS > 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 Wed Feb 24 11:03:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 24 Feb 2016 11:03:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2628) QA testsuite logging does not use log4j In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2628: -------------------------------------- Summary: QA testsuite logging does not use log4j Key: JBTM-2628 URL: https://issues.jboss.org/browse/JBTM-2628 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Affects Versions: 5.2.14.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The qa testsuite does not add log4j.jar to the classpath so we default to the jdk logger with the result that we do not get the desired log line formatting (such as including the thread name). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 24 11:41:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 24 Feb 2016 11:41:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2628) QA testsuite logging does not use log4j In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #984 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > QA testsuite logging does not use log4j > --------------------------------------- > > Key: JBTM-2628 > URL: https://issues.jboss.org/browse/JBTM-2628 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.14.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The qa testsuite does not add log4j.jar to the classpath so we default to the jdk logger with the result that we do not get the desired log line formatting (such as including the thread name). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Feb 24 11:43:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 24 Feb 2016 11:43:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2628) QA testsuite logging does not use log4j In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2628: ----------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/984 > QA testsuite logging does not use log4j > --------------------------------------- > > Key: JBTM-2628 > URL: https://issues.jboss.org/browse/JBTM-2628 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.14.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The qa testsuite does not add log4j.jar to the classpath so we default to the jdk logger with the result that we do not get the desired log line formatting (such as including the thread name). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 25 04:17:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 04:17:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2618) Improve concurrent behavior of HornetqJournalStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reopened JBTM-2618: --------------------------------- Assignee: Luis Barreiro > Improve concurrent behavior of HornetqJournalStore > -------------------------------------------------- > > Key: JBTM-2618 > URL: https://issues.jboss.org/browse/JBTM-2618 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 5.2.14.Final > > > Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. > When there is a high number of threads, some will be block reducing the overall throughput and increasing response times on the whole system. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 25 04:17:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 04:17:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2618) Improve concurrent behavior of HornetqJournalStore In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2618. ------------------------------- Resolution: Done > Improve concurrent behavior of HornetqJournalStore > -------------------------------------------------- > > Key: JBTM-2618 > URL: https://issues.jboss.org/browse/JBTM-2618 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 5.2.14.Final > > > Remove existing synchronized block and also make better usage of concurrent data structures already present in the code. > When there is a high number of threads, some will be block reducing the overall throughput and increasing response times on the whole system. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 25 04:52:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 04:52:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2626) Journal Store QA test failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2626: -------------------------------- Priority: Major (was: Critical) > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: jstack.25002.jacorb > > > There was a single test failure on each of the following CI runs: > crashrecovery05_2 CrashRecovery05_2_Test080 failed on the idlj run on the jobs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console > and jtatests01 JTATests01_Test006 failed on the jacorb run of job: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 25 04:52:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 04:52:01 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2626) Journal Store QA test failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168059#comment-13168059 ] Tom Jenkinson commented on JBTM-2626: ------------------------------------- Downgrading based on Mikes analysis > Journal Store QA test failures > ------------------------------ > > Key: JBTM-2626 > URL: https://issues.jboss.org/browse/JBTM-2626 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.13.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: jstack.25002.jacorb > > > There was a single test failure on each of the following CI runs: > crashrecovery05_2 CrashRecovery05_2_Test080 failed on the idlj run on the jobs: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/147/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/console > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/PROFILE=QA_JTS_JDKORB,jdk=jdk8.latest,label=linux/148/console > and jtatests01 JTATests01_Test006 failed on the jacorb run of job: > http://albany.eng.hst.ams2.redhat.com/job/narayana-hqstore/149/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/console -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 25 05:08:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 05:08:01 -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 reopened JBTM-2603: --------------------------------- > 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.2.14.Final > > > 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 Thu Feb 25 05:09:01 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 05:09:01 -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 closed JBTM-2603. ------------------------------- Resolution: Incomplete Description Closing with incomplete description as the change does not alter behaviour just adds more logging > 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.2.14.Final > > > 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 Thu Feb 25 05:15:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 05:15:03 -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 reopened JBTM-2481: --------------------------------- > 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.2.13.Final > > > 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 Thu Feb 25 05:15:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 05:15:03 -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.2.14.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.2.13.Final, 5.2.14.Final > > > 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 Thu Feb 25 05:15:03 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 05:15:03 -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 closed JBTM-2481. ------------------------------- Resolution: Done > 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.2.14.Final, 5.2.13.Final > > > 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 Thu Feb 25 05:37:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 25 Feb 2016 05:37: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 ] Gytis Trikleris updated JBTM-2616: ---------------------------------- Fix Version/s: 5.next (was: 5.later) > 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 Thu Feb 25 05:37:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 25 Feb 2016 05:37:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2617: ---------------------------------- Fix Version/s: 5.next (was: 5.later) > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 25 05:39:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 25 Feb 2016 05:39: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 ] Gytis Trikleris updated JBTM-2616: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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 Thu Feb 25 05:39:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 25 Feb 2016 05:39:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2617) Add recovery support to JMS integration In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2617: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add recovery support to JMS integration > --------------------------------------- > > Key: JBTM-2617 > URL: https://issues.jboss.org/browse/JBTM-2617 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTA > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 25 05:59:00 2016 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 25 Feb 2016 05:59:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2629) Implement TransactionalDriver alternative for JMS In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2629: ------------------------------------- Summary: Implement TransactionalDriver alternative for JMS Key: JBTM-2629 URL: https://issues.jboss.org/browse/JBTM-2629 Project: JBoss Transaction Manager Issue Type: Feature Request Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next JMS integration is done. In order to make it easier to use it in standalone Narayana, we should implement a similar utility as TransactionalDriver in JDBC. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 25 08:33:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 08:33:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2630) Downgrade maven assembly plugin to 2.4 in BlackTie In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2630: ----------------------------------- Summary: Downgrade maven assembly plugin to 2.4 in BlackTie Key: JBTM-2630 URL: https://issues.jboss.org/browse/JBTM-2630 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie, Build System Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next Currently the 2.5.5 maven assembly plugin does not work on EL5. The workaround is to downgrade to 2.4 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 25 08:34:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 08:34:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2630) Downgrade maven assembly plugin to 2.4 in BlackTie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2630: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/983 > Downgrade maven assembly plugin to 2.4 in BlackTie > -------------------------------------------------- > > Key: JBTM-2630 > URL: https://issues.jboss.org/browse/JBTM-2630 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently the 2.5.5 maven assembly plugin does not work on EL5. > The workaround is to downgrade to 2.4 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 25 08:36:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 08:36:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2629) Implement TransactionalDriver alternative for JMS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2629: -------------------------------- Forum Reference: https://developer.jboss.org/message/951562?et=watches.email.thread#951562 > Implement TransactionalDriver alternative for JMS > ------------------------------------------------- > > Key: JBTM-2629 > URL: https://issues.jboss.org/browse/JBTM-2629 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > JMS integration is done. In order to make it easier to use it in standalone Narayana, we should implement a similar utility as TransactionalDriver in JDBC. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 25 10:32:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 25 Feb 2016 10:32:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2630) Downgrade maven assembly plugin to 2.4 in BlackTie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2630: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Downgrade maven assembly plugin to 2.4 in BlackTie > -------------------------------------------------- > > Key: JBTM-2630 > URL: https://issues.jboss.org/browse/JBTM-2630 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Currently the 2.5.5 maven assembly plugin does not work on EL5. > The workaround is to downgrade to 2.4 -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Feb 25 11:18:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 25 Feb 2016 11:18:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2628) QA testsuite logging does not use log4j In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2628: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > QA testsuite logging does not use log4j > --------------------------------------- > > Key: JBTM-2628 > URL: https://issues.jboss.org/browse/JBTM-2628 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.14.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The qa testsuite does not add log4j.jar to the classpath so we default to the jdk logger with the result that we do not get the desired log line formatting (such as including the thread name). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Feb 26 07:17:00 2016 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 26 Feb 2016 07:17:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2624) Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2624: -------------------------------- Fix Version/s: 5.next > Introduce the administrator tool in the Narayana JTA OSGi integrated with the Karaf > ----------------------------------------------------------------------------------- > > Key: JBTM-2624 > URL: https://issues.jboss.org/browse/JBTM-2624 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > {quote} > We have several management ways in Karaf : > * mbeans (no need to rewrap them) > * shell commands > * a servlet for the felix web console (used by the community) > * a hawtio plugin (used by fuse) > The first two are the most important imho. > {quote} > the manual interventions that may be needed if the heuristic fails to rollback / commit the transactions. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 29 07:10:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 29 Feb 2016 07:10:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2631) UidTest qa test suite (with the journal store) failures In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2631: -------------------------------------- Summary: UidTest qa test suite (with the journal store) failures Key: JBTM-2631 URL: https://issues.jboss.org/browse/JBTM-2631 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Affects Versions: 5.2.14.Final Reporter: Michael Musgrove Assignee: Michael Musgrove CI job http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/151/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/ failed with various uid test failures: {quote} txcore Uid_Test011 Fail (0m18.180s) txcore Uid_Test011 Fail (0m19.431s) txcore Uid_Test012 Fail (0m20.850s) txcore Uid_Test004 Fail (0m11.566s) txcore Uid_Test005 Fail (0m12.343s) txcore Uid_Test006 Fail (0m12.062s) txcore Uid_Test007 Fail (0m15.742s) txcore Uid_Test008 Fail (0m16.908s) txcore Uid_Test009 Fail (0m17.282s) txcore_lockrecord LockRecord_Thread_Test036a Fail (8m12.773s) txcore_lockrecord LockRecord_Thread_Test036b Fail (8m10.265s) txcore_lockrecord LockRecord_Thread_Test048a Fail (8m11.115s) txcore_lockrecord LockRecord_Thread_Test048b Fail (8m7.376s) {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 29 07:17:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 29 Feb 2016 07:17:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2631) UidTest qa test suite (with the journal store) failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2631: ----------------------------------- Attachment: testoutput.jacorb.hqstore.tar The attachment includes the uid test failures. The LockRecord failures are excluded due to their size (1GB) > UidTest qa test suite (with the journal store) failures > ------------------------------------------------------- > > Key: JBTM-2631 > URL: https://issues.jboss.org/browse/JBTM-2631 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.14.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Attachments: testoutput.jacorb.hqstore.tar > > > CI job http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/151/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/ failed with various uid test failures: > {quote} > txcore Uid_Test011 Fail (0m18.180s) > txcore Uid_Test011 Fail (0m19.431s) > txcore Uid_Test012 Fail (0m20.850s) > txcore Uid_Test004 Fail (0m11.566s) > txcore Uid_Test005 Fail (0m12.343s) > txcore Uid_Test006 Fail (0m12.062s) > txcore Uid_Test007 Fail (0m15.742s) > txcore Uid_Test008 Fail (0m16.908s) > txcore Uid_Test009 Fail (0m17.282s) > txcore_lockrecord LockRecord_Thread_Test036a Fail (8m12.773s) > txcore_lockrecord LockRecord_Thread_Test036b Fail (8m10.265s) > txcore_lockrecord LockRecord_Thread_Test048a Fail (8m11.115s) > txcore_lockrecord LockRecord_Thread_Test048b Fail (8m7.376s) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 29 12:07:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 29 Feb 2016 12:07:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2631) UidTest qa test suite (with the journal store) failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169704#comment-13169704 ] Michael Musgrove commented on JBTM-2631: ---------------------------------------- This JIRA moved logging from JDK logging to log4j which enabled an appender that directs console output to System.out. The failing tests parse System.out to determine the outcome of spawned processes so they end up parsing trace output instead of program output. The fix is to redirect console logging output to System.err > UidTest qa test suite (with the journal store) failures > ------------------------------------------------------- > > Key: JBTM-2631 > URL: https://issues.jboss.org/browse/JBTM-2631 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.14.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Attachments: testoutput.jacorb.hqstore.tar > > > CI job http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/151/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/ failed with various uid test failures: > {quote} > txcore Uid_Test011 Fail (0m18.180s) > txcore Uid_Test011 Fail (0m19.431s) > txcore Uid_Test012 Fail (0m20.850s) > txcore Uid_Test004 Fail (0m11.566s) > txcore Uid_Test005 Fail (0m12.343s) > txcore Uid_Test006 Fail (0m12.062s) > txcore Uid_Test007 Fail (0m15.742s) > txcore Uid_Test008 Fail (0m16.908s) > txcore Uid_Test009 Fail (0m17.282s) > txcore_lockrecord LockRecord_Thread_Test036a Fail (8m12.773s) > txcore_lockrecord LockRecord_Thread_Test036b Fail (8m10.265s) > txcore_lockrecord LockRecord_Thread_Test048a Fail (8m11.115s) > txcore_lockrecord LockRecord_Thread_Test048b Fail (8m7.376s) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 29 12:11:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 29 Feb 2016 12:11:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2631) UidTest qa test suite (with the journal store) failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #985 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > UidTest qa test suite (with the journal store) failures > ------------------------------------------------------- > > Key: JBTM-2631 > URL: https://issues.jboss.org/browse/JBTM-2631 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.14.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Attachments: testoutput.jacorb.hqstore.tar > > > CI job http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/151/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/ failed with various uid test failures: > {quote} > txcore Uid_Test011 Fail (0m18.180s) > txcore Uid_Test011 Fail (0m19.431s) > txcore Uid_Test012 Fail (0m20.850s) > txcore Uid_Test004 Fail (0m11.566s) > txcore Uid_Test005 Fail (0m12.343s) > txcore Uid_Test006 Fail (0m12.062s) > txcore Uid_Test007 Fail (0m15.742s) > txcore Uid_Test008 Fail (0m16.908s) > txcore Uid_Test009 Fail (0m17.282s) > txcore_lockrecord LockRecord_Thread_Test036a Fail (8m12.773s) > txcore_lockrecord LockRecord_Thread_Test036b Fail (8m10.265s) > txcore_lockrecord LockRecord_Thread_Test048a Fail (8m11.115s) > txcore_lockrecord LockRecord_Thread_Test048b Fail (8m7.376s) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Feb 29 12:13:00 2016 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 29 Feb 2016 12:13:00 -0500 (EST) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2631) UidTest qa test suite (with the journal store) failures In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2631: ----------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/985 > UidTest qa test suite (with the journal store) failures > ------------------------------------------------------- > > Key: JBTM-2631 > URL: https://issues.jboss.org/browse/JBTM-2631 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.2.14.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Attachments: testoutput.jacorb.hqstore.tar > > > CI job http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-hqstore/151/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/ failed with various uid test failures: > {quote} > txcore Uid_Test011 Fail (0m18.180s) > txcore Uid_Test011 Fail (0m19.431s) > txcore Uid_Test012 Fail (0m20.850s) > txcore Uid_Test004 Fail (0m11.566s) > txcore Uid_Test005 Fail (0m12.343s) > txcore Uid_Test006 Fail (0m12.062s) > txcore Uid_Test007 Fail (0m15.742s) > txcore Uid_Test008 Fail (0m16.908s) > txcore Uid_Test009 Fail (0m17.282s) > txcore_lockrecord LockRecord_Thread_Test036a Fail (8m12.773s) > txcore_lockrecord LockRecord_Thread_Test036b Fail (8m10.265s) > txcore_lockrecord LockRecord_Thread_Test048a Fail (8m11.115s) > txcore_lockrecord LockRecord_Thread_Test048b Fail (8m7.376s) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)