Looks like there are a few different issues here.
First, to get more information on what caused the business
method to fail, take a look at the server.log. Sometimes the details of the exception are not
propagated to the client.
Regarding global JNDI names, an EJB that exposes a Remote interface has 1 JNDI name.
It could either be "ejb/risk" or "com.theocc.interfaces.RiskServer", but not both. The rules
for how global JNDI names are assigned to Remote EJBs in Glassfish are described here :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html#SessionBeanGlobalJNDINameAssignment
Lastly, it's OK to use a global JNDI name from a stand-alone client but understand that
whenever an EJB is accessed from within a Java EE component you should be using
the component environment approach (either @EJB or EJBContext.lookup or
lookup via java:comp/env) instead. Global JNDI names should really only be used
to resolve remote ejb dependencies, not as strings that directly appear in application code.
--ken
[Message sent by forum member 'ksak' (ksak)]
http://forums.java.net/jive/thread.jspa?messageID=219272