1 Reply Latest reply on Oct 29, 2007 10:07 PM by Scott Stark

    tx propagation over JRMP

    Jonathan Halliday Master

      Can anyone familiar with the JRMP invokers suggest how best to make them handle transaction contexts in a more flexible fashion.

      The use case I'm interested in is where true distributed transactions are needed, rather than just client side control of transactions boundaries for tx that reside in the server.

      Using the JBossTS JTS is possible where the transport is RMI/IIOP, since it has interceptors to handle the transaction propagation. That does not work with client side JRMP proxies for e.g. EJBs, since they are not aware of the JTS tx context on the client thread.

      What is the best solution here? Ideally there should be some pluggable way of having the JRMP transport find the tx context on the client thread, serialize it and deserialize it on the server side.

        • 1. Re: tx propagation over JRMP
          Scott Stark Master

          We will have to create the same type of interceptor pair to associate the tx info with the requests. The security interceptor pair is org.jboss.proxy.SecurityInterceptor (client) and org.jboss.ejb.plugins.SecurityInterceptor (ejb server). Just need to know more about what to get hold of to pass in the request.

          There is a org.jboss.tm.TransactionPropagationContextUtil, org.jboss.tm.TransactionPropagationContextImporter that the JRMPInvoker uses now for importing the transaction that could be used instead of a server side interceptor.