-
1. Re: Problem to lookup client side UserTransation from HA-JND
dirkniemeierde Jan 5, 2005 7:29 AM (in response to herthie57)Hi,
did you find a solution for the problem yet ?
regards,
Dirk -
2. Re: Problem to lookup client side UserTransation from HA-JND
herthie57 Jan 6, 2005 8:47 AM (in response to herthie57)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?
Best regards,
Thierry. -
3. Re: Problem to lookup client side UserTransation from HA-JNDI
memyself141 Nov 8, 2013 2:37 PM (in response to herthie57)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??
-
4. Re: Problem to lookup client side UserTransation from HA-JNDI
wdfink Nov 9, 2013 6:54 AM (in response to memyself141)Hi Aayush,
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.