BasicNamingNode.lookup() has thrown a SecurityException

We found this prefix in 4 webpages.
MapChildren (2)Typical messages (2)TraceDetailed Map
  1. java.lang.SecurityException
    1.   at weblogic.security.service.SecurityServiceManager.seal()
    2.   at weblogic.security.service.RoleManager.getRoles()
    3.   at weblogic.security.service.AuthorizationManager.isAccessAllowed()
    4.   at weblogic.jndi.internal.ServerNamingNode.checkPermission()
    5.   at weblogic.jndi.internal.ServerNamingNode.checkLookup()
    6.   at weblogic.jndi.internal.ServerNamingNode.lookupHere()
    7.   at weblogic.jndi.internal.BasicNamingNode.lookup()
  1. SecurityException

    ExecuteThread.run()
    Crashes:4
    Projects:0
    Web Pages:3
    Error Reports:0
    First:4 months ago
    Last:4 months ago
    preview
  2. DB Connection problem after the call returns from JAR file

    First:13 years ago
    Last:2 years ago
    Author:666705
MessageNumber of crashes
Invalid Subject: principals=[gfsadmin]3
[Security:090398]Invalid Subject: principals=[<user>, <group>]1
  1. java.lang.SecurityException
    1.   at weblogic.security.service.SecurityServiceManager.seal()
    2.   at weblogic.security.service.RoleManager.getRoles()
    3.   at weblogic.security.service.AuthorizationManager.isAccessAllowed()
    4.   at weblogic.jndi.internal.ServerNamingNode.checkPermission()
    5.   at weblogic.jndi.internal.ServerNamingNode.checkLookup()
    6.   at weblogic.jndi.internal.ServerNamingNode.lookupHere()
    7.   at weblogic.jndi.internal.BasicNamingNode.lookup()