Occasionally, a JNDI lookup of a remote business interface from a java client running in a seperate jvm results in the following exception:
Once it happens, it seems to continue to happen until I restart the server. The object is remotable; the same remote business interface lookup, called from the same code path against the same server with the same deployed applications, succeeds most of the time. It seems to be when the server is extremely loaded, possibly with excessive restful web service calls coming in and accessing other EJBs via injection, that might trigger this behavior. Unfortunately, I have not been able to confirm that this is the situation that causes this to occur. Has anyone else seen this? ----- - Tim -- View this message in context: http://openejb.979440.n4.nabble.com/Intermittant-javax-naming-NamingException-Not-remotable-tp4665741.html Sent from the OpenEJB User mailing list archive at Nabble.com.
