[JBoss JIRA] (JBTM-1825) Error starting XTS Services
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1825?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1825:
---------------------------------
Thanks for looking at this issue
> 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: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (JBTM-1825) Error starting XTS Services
by Jim Ma (JIRA)
[ https://issues.jboss.org/browse/JBTM-1825?page=com.atlassian.jira.plugin.... ]
Jim Ma commented on JBTM-1825:
------------------------------
There is checker to make sure the endpoint state is stopped when invoke ep.setInvocationhandler(), so change to original state doesn't work to set the invocationHandler. I'll have a look at this issue now, and get back to you soon.
> 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: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (JBTM-1825) Error starting XTS Services
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1825?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1825:
---------------------------------
the better fix looks like
{code}
for (Endpoint ep : dep.getService().getEndpoints()) {
synchronized(ep) {
+ EndpointState orig_state = ep.getState();
ep.setState(EndpointState.STOPPED);
ep.setInvocationHandler(new InvocationHandlerJAXWS());
- ep.setState(EndpointState.STARTED);
+ ep.setState(orig_state);
{code}
> 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: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (JBTM-1825) Error starting XTS Services
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1825?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1825:
---------------------------------
{code}
diff --git a/webservices/server-integration/src/main/java/org/jboss/as/webservices/publish/EndpointPubl
index 11fb5f6..8caa143 100644
--- a/webservices/server-integration/src/main/java/org/jboss/as/webservices/publish/EndpointPublisherIm
+++ b/webservices/server-integration/src/main/java/org/jboss/as/webservices/publish/EndpointPublisherIm
@@ -127,7 +127,7 @@ public final class EndpointPublisherImpl implements EndpointPublisher {
synchronized(ep) {
ep.setState(EndpointState.STOPPED);
ep.setInvocationHandler(new InvocationHandlerJAXWS());
- ep.setState(EndpointState.STARTED);
+ ep.setState(EndpointState.UNDEFINED);
}
}
} finally {
{code}
This can fix the issue and [~jim.ma], does it make sense ?
> 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: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (JBTM-1825) Error starting XTS Services
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1825?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1825:
---------------------------------
[~paul.robinson] the DefaultLifecycleHandler.start() only called once and the endpoint state is STARTED when calling EndpointService.start()
{code}
@Override
public void start(final StartContext context) throws StartException {
ROOT_LOGGER.starting(name);
endpoint.setSecurityDomainContext(new SecurityDomainContextAdaptor(securityDomainContextValue.getValue()));
final List<RecordProcessor> processors = endpoint.getRecordProcessors();
for (final RecordProcessor processor : processors) {
registerRecordProcessor(processor, endpoint);
}
registerEndpoint(endpoint);
endpoint.getLifecycleHandler().start(endpoint);
}
{code}
> 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: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (JBTM-1825) Error starting XTS Services
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1825?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1825:
---------------------------------
It looks like the commit [JBWS-3649]:Invoke LifecycleHandler in EndpointService https://github.com/wildfly/wildfly/commit/1ed7cb8c042cfdb9311c6558d931e78...
I just revert it and the xts services work fine.
[~jim.ma] can you take a look at this ?
> 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: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (JBTM-1829) Recovery creator service fails to start in JacORBGenericRecoveryCreatorUnitTest
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1829?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-1829:
-----------------------------------
Yes, I'd forgotten to check in a couple of changes to give public access to the async shutdown option.
> Recovery creator service fails to start in JacORBGenericRecoveryCreatorUnitTest
> -------------------------------------------------------------------------------
>
> Key: JBTM-1829
> URL: https://issues.jboss.org/browse/JBTM-1829
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTS
> Reporter: Gytis Trikleris
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/177/TESTS=MAIN,jd...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/50
> {code}
> Emptying /home/hudson/workspace/narayana/TESTS/MAIN/jdk/jdk7.latest/label/linux/ArjunaJTS/jts/target/test-classes/ObjectStore
> 1 [main] WARN jacorb.config - jacorb.home unset! Will use '.'
> 1 [main] WARN jacorb.config - File ./jacorb.properties for configuration jacorb not found
> 2 [main] WARN jacorb.config - no properties found for configuration jacorb
> 5 [main] INFO jacorb.orb.print_version -
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> JacORB V 2.3.1 (JBoss patch01), www.jacorb.org
> (C) The JacORB project 29-Jul-2009
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 40 [main] INFO jacorb.orb - Property "jacorb.hashtable_class" is set to: java.util.HashMap
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit initORBandOA
> INFO: ARJUNA022087: RecoveryServer using existing ORB
> 201 [main] WARN jacorb.config - jacorb.home unset! Will use '.'
> 201 [main] WARN jacorb.config - File ./jacorb.properties for configuration jacorb not found
> 202 [main] WARN jacorb.config - no properties found for configuration jacorb
> 202 [main] INFO jacorb.orb.singleton - created ORBSingleton
> 313 [main] INFO jacorb.poa - oid:
> 00 17 4C 48 03 47 41 4C 02 05 32 ..LH.GAL..2
> object is activated
> 314 [main] INFO jacorb.poa - Using server ID (4426315968) for transient POA
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.recovery.recoverycoordinators.GenericRecoveryCreator create
> WARN: ARJUNA022156: GenericRecoveryCreator: Missing params to create
> 318 [Thread-3] INFO jacorb.orb - ORB run
> 321 [POADestructor] INFO jacorb.poa - POA RcvCo-RecCoService_jaimerecovery_coordinator destroyed
> 322 [POADestructor] INFO jacorb.poa - POA RootPOA destroyed
> 322 [main] INFO jacorb.orb - prepare ORB for shutdown...
> 322 [main] INFO jacorb.orb - ORB going down...
> 323 [ServerSocketListener] INFO jacorb.orb.iiop - Listener exited
> 323 [main] INFO jacorb.orb - ORB shutdown complete
> Emptying /home/hudson/workspace/narayana/TESTS/MAIN/jdk/jdk7.latest/label/linux/ArjunaJTS/jts/target/test-classes/ObjectStore
> Emptying /home/hudson/workspace/narayana/TESTS/MAIN/jdk/jdk7.latest/label/linux/ArjunaJTS/jts/target/test-classes/ObjectStore
> 328 [main] WARN jacorb.config - jacorb.home unset! Will use '.'
> 328 [main] WARN jacorb.config - File ./jacorb.properties for configuration jacorb not found
> 329 [main] WARN jacorb.config - no properties found for configuration jacorb
> 329 [main] INFO jacorb.orb.print_version -
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> JacORB V 2.3.1 (JBoss patch01), www.jacorb.org
> (C) The JacORB project 29-Jul-2009
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 329 [main] INFO jacorb.orb - Property "jacorb.hashtable_class" is set to: java.util.HashMap
> 330 [Thread-3] INFO jacorb.orb - ORB run, exit
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit initORBandOA
> INFO: ARJUNA022087: RecoveryServer using existing ORB
> 333 [POADestructor] INFO jacorb.poa - POA RcvCo-RecCoService_jaimerecovery_coordinator destroyed
> 333 [POADestructor] INFO jacorb.poa - POA RootPOA destroyed
> 333 [Thread-3] INFO jacorb.orb - prepare ORB for shutdown...
> 333 [Thread-3] INFO jacorb.orb - ORB going down...
> 333 [Thread-3] INFO jacorb.orb - ORB shutdown complete
> 334 [ServerSocketListener] INFO jacorb.orb.iiop - Listener exited
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit startRCservice
> WARN: ARJUNA022083: JacOrbRCServiceInit - Failed to start RC service
> org.omg.CORBA.OBJECT_NOT_EXIST: POA destroyed vmcid: 0x0 minor code: 0 completed: No
> at org.jacorb.poa.POA.checkDestructionApparent(Unknown Source)
> at org.jacorb.poa.POA.the_POAManager(Unknown Source)
> at com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit.startRCservice(JacOrbRCServiceInit.java:225)
> at com.hp.mwtests.ts.jts.recovery.JacORBGenericRecoveryCreatorUnitTest.testSuccess(JacORBGenericRecoveryCreatorUnitTest.java:95)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> 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.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> 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.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Jul 07, 2013 5:55:53 PM com.arjuna.orbportability.RootOA objectIsReady
> WARN: ARJUNA021004: objectIsReady - invalid POA: rootPOA
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService
> INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 48098
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init>
> INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 48098
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start
> INFO: ARJUNA012170: TransactionStatusManager started on port 48098 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCManager makeRC
> WARN: ARJUNA022077: RCManager.makeRC did not make rcvco reference
> org.omg.CORBA.BAD_INV_ORDER: vmcid: 0x0 minor code: 4 completed: No
> at org.jacorb.orb.ORB.work_pending(Unknown Source)
> at org.jacorb.orb.ORB.perform_work(Unknown Source)
> at org.jacorb.orb.ORB.string_to_object(Unknown Source)
> at com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCManager.makeRC(JacOrbRCManager.java:102)
> at com.arjuna.ats.internal.jts.recovery.recoverycoordinators.GenericRecoveryCreator.create(GenericRecoveryCreator.java:121)
> at com.hp.mwtests.ts.jts.recovery.JacORBGenericRecoveryCreatorUnitTest.testSuccess(JacORBGenericRecoveryCreatorUnitTest.java:111)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> 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.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
> 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.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Emptying /home/hudson/workspace/narayana/TESTS/MAIN/jdk/jdk7.latest/label/linux/ArjunaJTS/jts/target/test-classes/ObjectStore
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore remove_state
> WARN: ARJUNA012284: ShadowingStore::remove_state() - access problems on 0:ffffac118321:8b3f:51d99d99:3 and /Recovery/TransactionStatusManager
> Jul 07, 2013 5:55:53 PM com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore remove_state
> WARN: ARJUNA012265: ShadowingStore::remove_state() - state 0:ffffac118321:8b3f:51d99d99:3 does not exist for type /Recovery/TransactionStatusManager
> {code}
--
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: http://www.atlassian.com/software/jira
11 years, 2 months