Applies to:
JBoss
Description:
Error while trying to view a portlet which is used to access an ejb at Sun Application server remotely.
Cause:
JBoss is not set as the classloader for EJBs and web applications in server.xml file.
JAVA-EJB "is not bound in this context" ejb, "name ejb is not bound in this context" jetty, "name running mode is not bound in this context", "name xxx is not bound in this context", @ejb not bound in this context, axis ejb * not bound, ejb glassfish is not bound in this context, ejb is not bound in this context, ejb is not bound in this context tomcat jboss, ejb name farmer is not bound in this context, ejb name is not bound in this context, ejb name not bound in jmx-console, ejb not bound, ejb remote jboss not bound, ejb tomcat 6 name is not bound in this context, error, j, java ejb is not bound in this context, java webapp remote ejb name is not bound in this context, lrm-00118: syntax error at '=' at the end of input, name "is already bound in this context", name com.unibet.money.ejb.moneyservice is not bound in this context, name ejb is not bound in this context, name ejb is not bound in this context remote, name ejb not bound in this context, name end is not bound in this context, name external is not bound in this context, name is not bound in this context ejb, name is not bound in this context web application, name remote ejb is already bound in this context, name xxxis not bound in this context, remote access ejb linux not bound, remote call, remote not bound jboss, tomcat "name ejb is not bound in this context", tomcat "not bound" remote, tomcat ejb context name, what is xdoclet
Configure the jndi name and the EJB location under external jndi services in JBoss JMX console.