Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Terracotta by jadey, 1 year ago
occur when the JNDI client using the "java:" name is not executed on the thread of a server application request. Make sure that a J2EE application does not execute JNDI operations on "java:" names within static code blocks or in threads created by
javax.naming.NameNotFoundException: Name comp/env/ejb not found in context "java:".	at com.ibm.ws.naming.ipbase.NameSpace.getParentCtxInternal(NameSpace.java:1969)	at com.ibm.ws.naming.ipbase.NameSpace.retrieveBinding(NameSpace.java:1376)	at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java:1219)	at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:1141)	at com.ibm.ws.naming.urlbase.UrlContextImpl.lookupExt(UrlContextImpl.java:1436)	at com.ibm.ws.naming.java.javaURLContextImpl.lookupExt(javaURLContextImpl.java:477)	at com.ibm.ws.naming.java.javaURLContextRoot.lookupExt(javaURLContextRoot.java:485)	at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:370)	at org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161)	at javax.naming.InitialContext.lookup(InitialContext.java:431)	at org.quartz.jobs.ee.ejb.EJBInvokerJob.execute(EJBInvokerJob.java:156)	at org.quartz.core.JobRunShell.run(JobRunShell.java:213)	at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)