Thanks. I changed the identifiers to be unique but nothing changes .

Sorry for late response.

The breakpoint in UserTransactionImple did not trigger at all (not at caller side nor at callee). I tried other UserTransaction implementations but no luck either. This is definetely not a debugger issue as it triggers breakpoints in any other classes, i.e. JBossWSInvoker.

This is very strange as the transaction works fine (I changed in callee WS @TransactionAttribute to be MANDATORY and the transaction to be sure is active).

I've put my stack frames here:

• caller - https://pastebin.com/MmDgnEzc
• callee - https://pastebin.com/56ZFvHuR

I see CMTTxInterceptor at the caller side which basically creates the transaction but I don't know which interceptor is supporting the transaction at the callee side.

Do I need some more configuration other than replacing standalone.xml with standalone-xts.xml?

Thanks!

I think I found the issue causing coordinator URL to be ignored.

During XTS subsystem startup in com.arjuna.webservices11.wscoor.server.ActivationCoordinatorInitialisation.startup() I can see wscEnvironmentBean initialized with the following properties:

asyncRequestWait 10000

bindAddress10 localhost

bindAddress11 172.18.0.9

bindPort10 8080

bindPort11 8080

bindPortSecure10 8080

bindPortSecure11 8443

coordinatorAddress10 null

coordinatorAddress11 null

coordinatorPath10 ws-c10/soap/ActivationCoordinator

coordinatorPath11 ws-c11/ActivationService

coordinatorPort10 8080

coordinatorPort11 8080

coordinatorScheme10 http

coordinatorScheme11 http

coordinatorURL10 null

coordinatorURL11 http://coordinator:8080/ws-c11/ActivationService

initialTransportPeriod 5000

maximumTransportPeriod 300000

serviceURLPath null

transportTimeout 30000

useAsynchronousRequest NO

The xts-environment property sets the coordinatorURL11 field but it is not used in the URL generation code:

   public static void startup()

  {

        final ServiceRegistry serviceRegistry = PrivilegedServiceRegistryFactory.getInstance().getServiceRegistry();

        WSCEnvironmentBean wscEnvironmentBean = XTSPropertyManager.getWSCEnvironmentBean();

        String bindAddress = wscEnvironmentBean.getBindAddress11();

        int bindPort = wscEnvironmentBean.getBindPort11();

        int secureBindPort = wscEnvironmentBean.getBindPortSecure11();

        String serviceURLPath = wscEnvironmentBean.getServiceURLPath();

        if (serviceURLPath == null) {

            serviceURLPath = "/ws-c11";

        }

        if (bindAddress == null) {

            bindAddress = "localhost";

        }

        if (bindPort == 0) {

            bindPort = 8080;

        }

        if (secureBindPort == 0) {

            secureBindPort = 8443;

        }

        final String baseUri = "http://" +  bindAddress + ":" + bindPort + serviceURLPath;

        final String uri = baseUri + "/ActivationService";

        final String secureBaseUri = "https://" + bindAddress + ":" + secureBindPort + serviceURLPath;

        final String secureUri = secureBaseUri + "/ActivationService";

        serviceRegistry.registerServiceProvider(CoordinationConstants.ACTIVATION_SERVICE_NAME, uri) ;

        serviceRegistry.registerSecureServiceProvider(CoordinationConstants.ACTIVATION_SERVICE_NAME, secureUri) ;

  }

Is it possible to configure the remaining properties in standalone.xml?

I've attached traces from the `org.jboss.jbossts.txbridge` category and did some debugging (JaxWSTxOutboundBridgeHandler is invoked successfully indeed). Unfortunately the traces do not contain tx-coordinator URL information.