javax.naming.NamingException: Not in an application scope - start Orion with t -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

Solutions on the web

via Oracle Community by 843793, 1 year ago
Not in an application scope - start Orion with t -userThreads switch if using user-created threads
via Oracle Community by 397916, 1 year ago
Not in an application scope - start Orion with t -userThreads switch if using user-created threads
via Oracle Community by 45826, 1 year ago
Not in an application scope - start Orion with the -userThreads switch if using user-created threads
via Oracle Community by 430107, 1 year ago
Not in an application scope - start Orion with the -userThreads switch if using user-created threads [java]
via Oracle Community by 418500, 1 year ago
com.evermind.server.ApplicationInitialContextFactory should only be used inside Orion server environments. For client com.evermind.server.ApplicationClientInitialContextFactory or com.evermind.server.rmi.RMIInitialContextFactory should be used
via Oracle Community by 391086, 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 Orion with t -userThreads switch if using user-created threads
at com.evermind.server.PreemptiveApplicationContext.getContext(PreempteApplicationContext.java:34)
at com.evermind.naming.FilterContext.lookup(FilterContext.java:138)

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.

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