The way you've declared and looked up the remote ejb refs is correct. It's very odd that it would work when the lookup is made from the web app but hang when made from the ejb, since both
are executing in the same appserver instance. At runtime, the ejb-ref and @EJB are essentially
handled identically.
When you say the remote ejb jar is included in the classpath, do you mean the interfaces are
packaged in the caller's ejb-jar or that they are put in the appserver global classpath? It's much
better to package them in the application's module, although since you didn't get any class cast
exceptions that's unlikely to be causing the issue.
Try looking through the rest of the server.log to see if there are any other warning or severe
error messages related to the ejbs during deployment or runtime. What version of
the appserver are you using?
[Message sent by forum member 'ksak' (ksak)]
http://forums.java.net/jive/thread.jspa?messageID=320809