-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
On Wildfly master as of today, booting with standalone-xts.xml produces these errors:
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
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.
