It means that an item you are attempting to lookup in JNDI is not bound to JNDI.
This could be caused by a failed deployment or possibly using the wrong name. If this relates to using a session bean the exception is the wrong place to start diagnosing the problem, you should follow the following steps. Undeploy everything that you have currently deployed and restart JBoss. Check for any errors in the console. Deploy your session bean. Check for any errors in the console. Use JMX Console and invoke the list operation on the JNDI View MBean to see what JNDI name was used. It is only at this point that you are ready to run any client that tries to use the session bean. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3877491#3877491 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3877491 ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
