lookupjavax.naming.NoPermissionException: Not allowed to look up java:comp/UserTransaction, check the namespace-access tag setting in orion-application.xml for details

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 561859, 1 year ago
Not allowed to look up java:comp/UserTransaction, check the namespace-access tag setting in orion-application.xml for details
via hivmr.com by Unknown author, 1 year ago
Not allowed to look up java:comp/UserTransaction, check the namespace-access tag setting in orion-application.xml for details
lookupjavax.naming.NoPermissionException: Not allowed to look up java:comp/UserTransaction, check the namespace-access tag setting in orion-application.xml for details
at com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:109)
at com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:91)
at com.evermind.server.rmi.RMIClientConnection.waitForJndiResponse(RMIClientConnection.java:371)
at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:179)
at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
at javax.naming.InitialContext.lookup(InitialContext.java:351)

Users with the same issue

You are the first who have seen this exception.

Write tip

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