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 JBoss Issue Tracker by Jacques Desmazières, 1 year ago
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 that J2EE application. Such code does not necessarily run on
via JBoss Issue Tracker by Jacques Desmazières, 1 year ago
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 that J2EE application. Such code does not necessarily run on
via Oracle Community by Suren.Khatana, 1 year ago
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 that J2EE application. Such code does not necessarily run on the
via programask.com by Unknown author, 2 years ago
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 that J2EE application. Such code does not necessarily run on
via Stack Overflow by sab
, 2 years ago
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 that J2EE application. Such code does not necessarily run on
javax.naming.ConfigurationException: A JNDI operation on a "java:" name cannot be completed because the serverruntime is not able to associate the operation's thread with any J2EE application component.  This condition can 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 that J2EE application.  Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on "java:" names. [Root exception is javax.naming.NameNotFoundException: Name comp/env/jdbc not found in context "java:".]	at com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS(javaURLContextImpl.java:416)	at com.ibm.ws.naming.java.javaURLContextImpl.lookup(javaURLContextImpl.java:388)	at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:204)	at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:144)	at javax.naming.InitialContext.lookup(InitialContext.java:363)	at org.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:52)	at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124)	at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:56)	at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:410)	at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:62)	at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009)	at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292)	at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:91)	at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:94)	at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:98)	at org.jbpm.persistence.db.DbPersistenceService.getJobSession(DbPersistenceService.java:354)	at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:563)	at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread.java:109)	at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:56)