javax.naming.NamingException: Not in an application scope - start OC4J with the -userThreads switch if using user-created threads

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

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via Oracle Community by 439806, 1 year ago
Not in an application scope - start OC4J with the -userThreads switch if using user-created threads
via Oracle Community by 439806, 1 year ago
Not in an application scope - start OC4J with the -userThreads switch if using user-created threads
via Oracle Community by 608659, 11 months ago
null should only be used inside OC4J server environments. Check the user documentation for the appropriate client initial context factory
via Oracle Community by 624383, 1 year ago
Not in an application scope - start OC4J with the -userThreads switch if using user-created threads
via Oracle Community by 485040, 1 year ago
Not in an application scope - start OC4J with the -userThreads switch if using user-created threads
via Oracle Community by 628454, 1 year ago
Not in an application scope - start OC4J with the -userThreads switch if using user-created threads
javax.naming.NamingException: Not in an application scope - start OC4J with the -userThreads switch if using user-created threads
at com.evermind.server.PreemptiveApplicationContext.getContext(PreemptiveApplicationContext.java:30)
at com.evermind.naming.FilterContext.lookup(FilterContext.java:126)
at com.evermind.server.PreemptiveApplicationContext.lookup(PreemptiveApplicationContext.java:42)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at oracle.jbo.server.DBTransactionImpl.lookupDataSource(DBTransactionImpl.java:1434)
at oracle.jbo.server.DBTransactionImpl.getInternalConnection(DBTransactionImpl.java:1398)
at oracle.jbo.server.DBTransactionImpl.getPersistManagerConnection(DBTransactionImpl.java:1300)
at oracle.jbo.pcoll.PCollManager.ensureConnection(PCollManager.java:489)
at oracle.jbo.pcoll.OraclePersistManager.getConnection(OraclePersistManager.java:148)
at oracle.jbo.pcoll.OraclePersistManager.queryNextCollectionId(OraclePersistManager.java:1448)
at oracle.jbo.pcoll.PCollManager.register(PCollManager.java:566)
at oracle.jbo.pcoll.PCollection.(PCollection.java:103)
at oracle.jbo.pcoll.PCollManager.createCollection(PCollManager.java:464)
at oracle.jbo.server.DBSerializer.setup(DBSerializer.java:153)
at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:286)
at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:267)
at oracle.jbo.server.ApplicationModuleImpl.passivateStateInternal(ApplicationModuleImpl.java:5303)
at oracle.jbo.server.ApplicationModuleImpl.passivateState(ApplicationModuleImpl.java:5195)
at oracle.jbo.server.ApplicationPoolMessageHandler.doPoolMessage(ApplicationPoolMessageHandler.java:308)
at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:7763)
at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:4074)
at oracle.jbo.common.ampool.ApplicationPoolImpl.manageReferencingState(ApplicationPoolImpl.java:1239)
at oracle.jbo.common.ampool.ApplicationPoolImpl.finalizeResource(ApplicationPoolImpl.java:1156)
at oracle.jbo.pool.ResourcePool.removeResourceInternal(ResourcePool.java:749)
at oracle.jbo.pool.ResourcePool.setState(ResourcePool.java:1004)
at oracle.jbo.pool.ResourcePool.gc(ResourcePool.java:1423)
at oracle.jbo.pool.ResourcePool.wakeup(ResourcePool.java:774)
at oracle.jbo.pool.ResourcePool.wakeup(ResourcePool.java:779)
at oracle.jbo.pool.ResourcePoolMonitor.run(ResourcePoolMonitor.java:98)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.