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. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860907#3860907 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860907 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
