did you find a solution for the problem yet ?
Sorry I still not have any solution, just a workaround which is not to use HA-JNDI if you plan to use UserTransaction but normal JNDI instead.
I have no certitude but just feeling that the fact client side can access the java:/xxx HA-JNDI namespace (which is normally forbidden from client side) is due to the way HA-JNDI works. Indeed in HA-JNDI if one node cannot lookup a given entry in its local JNDI repository then it forwards the request to the second node. Also I suppose the second node can return a value since it is requested from a sever space (the 1st node). This might also explain why the problem disappears when only one node is running. But this is only suppositions...
I tied to post a bug report but didn?t found any link for that on JBoss site. If someone can help?
Hi, I am facing a similar problem... When I invoke InitialContext.lookup("UserTransaction") from a POJO client, it returns me a ClientUserTransaction which works fine however, when I do the same from an application deployed on a JBoss server (my client is also a JBoss Server), I get a ServerVMClientUserTransaction which does not participate in the transaction at the server.... What should I do to get this done??
welcome to the forum.
Instead of post to an 8 year old thread wich mean definitive a different version you should open a new question and provide more details about the used version and your code.