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 3004, 1 year ago
User "guest" does not have Permission "lookup" base d on ACL "weblogic.jndi.com.capgroup.btps".
via Oracle Community by 3004, 1 year ago
User "guest" does not have Permission "lookup" base d on ACL "weblogic.jndi.com.capgroup.btps".
via Google Groups by Srikanth Goli, 5 months ago
User "guest" does not have Permission "lookup" base d on ACL "weblogic.jndi.com.capgroup.btps".
via Oracle Community by 3004, 1 year ago
User "guest" does not have Permission "lookup" base d on ACL "weblogic.jndi.com.capgroup.btps".
via Oracle Community by 3004, 1 year ago
User "system" does not have Permission "execute" ba sed on ACL "weblogic.jndi.weblogic".
via Oracle Community by 3004, 1 year ago
User "APPLEJMS" does not have Permission "lookup" b ased on ACL "weblogic.jndi.kbf".
java.lang.SecurityException: User "guest" does not have Permission "lookup" base
d on ACL "weblogic.jndi.com.capgroup.btps".	at weblogic.security.acl.Security.logAndThrow(Security.java:372)	at weblogic.security.acl.Security.checkPermission(Security.java:254)	at weblogic.jndi.internal.NamingSecurityManagerImpl.checkPermission(NamingSecurityManagerImpl.java:98)	at weblogic.jndi.internal.NamingSecurityManagerImpl.checkLookup(NamingSecurityManagerImpl.java:45)	at weblogic.jndi.toolkit.BasicWLContext.resolveName(BasicWLContext.java:737)	at weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:133)	at weblogic.jndi.toolkit.BasicWLContext.lookup(BasicWLContext.java:574)	at javax.naming.InitialContext.lookup(InitialContext.java:350)	at com.capgroup.btps.server.TestThread.run(StartupTest.java:49)	at java.lang.Thread.run(Thread.java:484)