Nobody else has seen a remotable object JNDI lookup fail with a "Not remotable" error message?
I assume that people are assuming that the object is, in fact, not remotable; however, 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. ----- - Tim -- View this message in context: http://openejb.979440.n4.nabble.com/Intermittant-javax-naming-NamingException-Not-remotable-tp4665677p4665699.html Sent from the OpenEJB User mailing list archive at Nabble.com.
