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

hivmr.com | 5 months ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    RMIClient.lookup Failed during lookup javax.naming.NoPermissionException:

    Oracle Community | 1 decade ago | 561859
    lookupjavax.naming.NoPermissionException: Not allowed to look up java:comp/UserTransaction, check the namespace-access tag setting in orion-application.xml for details
  2. 0

    db:: 5.00::NULL UserTransaction retrieved xc

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

    Root Cause Analysis

    1. 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()
    2. com.evermind.server
      RMIClientContext.lookup
      1. com.evermind.server.rmi.RMICall.EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMICall.java:109)
      2. com.evermind.server.rmi.RMICall.throwRecordedException(RMICall.java:91)
      3. com.evermind.server.rmi.RMIClientConnection.waitForJndiResponse(RMIClientConnection.java:371)
      4. com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:179)
      5. com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
      6. com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
      6 frames
    3. Java RT
      InitialContext.lookup
      1. javax.naming.InitialContext.lookup(InitialContext.java:351)
      1 frame