Please see attached reproducer.

1 - sca-service-app defines SCA service binding and 2 references to JCA binding and JMS binding
2 - client-app receives message from JCA binding and references sca-service-app, global transaction required

There is propagated global transaction from client-app to sca-service-app, XTS is enabled.

If sca-service-app invokes only JMS binding, HornetQ enlists correctly to propagated XA transaction. But if sca-service-app invokes JCA binding and JMS binding too, JMS binding fails as HornetQ cannot enlist to propagated XA transaction. Error: XA start operation failed Cannot start, session is already doing work in a transaction XidImpl...

This works with ActiveMQ.

See associated BZ for stack traces and reproducer.