]
Paul Robinson commented on JBTM-1825:
-------------------------------------
This method seems to do the actual starting of the service. Therefore it fails if the
service is already started. Given that XTS seems to be functioning correctly, I'd
guess that the bug is this method being called twice. The first time it succeeds, the
second it fails, producing the error.
Error starting XTS Services
---------------------------
Key: JBTM-1825
URL:
https://issues.jboss.org/browse/JBTM-1825
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Application Server Integration, XTS
Reporter: Paul Robinson
Assignee: Amos Feng
Priority: Critical
Fix For: 5.0.0.M4
On Wildfly master as of today, booting with standalone-xts.xml produces these errors:
{code}
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015539:
Starting service
jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithCoordinatorCompletionCoordinatorService
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-8) JBAS015539:
Starting service
jboss.ws.endpoint."ws-t11-coordinator.deployment".CoordinatorService
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-11) JBAS015539:
Starting service
jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorService
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015539:
Starting service
jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorRPCService
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015539:
Starting service
jboss.ws.endpoint."ws-t11-coordinator.deployment".TerminationCoordinatorService
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539:
Starting service
jboss.ws.endpoint."ws-t11-coordinator.deployment".BusinessAgreementWithParticipantCompletionCoordinatorService
14:13:02,059 INFO [org.jboss.as.webservices] (MSC service thread 1-5) JBAS015539:
Starting service
jboss.ws.endpoint."ws-t11-coordinator.deployment".CompletionCoordinatorRPCService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-1) JBWS022103:
Cannot start endpoint in state STARTED:
jboss.ws:context=ws-t11-coordinator,endpoint=BusinessAgreementWithCoordinatorCompletionCoordinatorService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-8) JBWS022103:
Cannot start endpoint in state STARTED:
jboss.ws:context=ws-t11-coordinator,endpoint=CoordinatorService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-11) JBWS022103:
Cannot start endpoint in state STARTED:
jboss.ws:context=ws-t11-coordinator,endpoint=CompletionCoordinatorService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-4) JBWS022103:
Cannot start endpoint in state STARTED:
jboss.ws:context=ws-t11-coordinator,endpoint=TerminationCoordinatorRPCService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-3) JBWS022103:
Cannot start endpoint in state STARTED:
jboss.ws:context=ws-t11-coordinator,endpoint=TerminationCoordinatorService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-2) JBWS022103:
Cannot start endpoint in state STARTED:
jboss.ws:context=ws-t11-coordinator,endpoint=BusinessAgreementWithParticipantCompletionCoordinatorService
14:13:02,060 ERROR [org.jboss.ws.common.deployment] (MSC service thread 1-5) JBWS022103:
Cannot start endpoint in state STARTED:
jboss.ws:context=ws-t11-coordinator,endpoint=CompletionCoordinatorRPCService
{code}
The XTS integration tests in the WildFly codebase under
'testsuite/integration/xts' pass on my box, but are failing in CI (sometimes). I
don't know how any of the XTS tests could be passing if those services really
haven't started up.
Note that the wsdl is available at
http://localhost:8080/ws-t11-coordinator/TerminationCoordinatorService?wsdl, despite
TerminationCoordinatorService claiming not to have started.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: