java.lang.SecurityException

[Security:090398]Invalid Subject: principals=[weblogic, Administrators, FormCheckers]

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web2

  • Stack trace

    • java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, FormCheckers] at weblogic.security.service.SecurityServiceManagerDelegate2Impl.seal(SecurityServiceManagerDelegate2Impl.java:484) at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:524) at weblogic.security.service.IdentityUtility.authenticatedSubjectToIdentity(IdentityUtility.java:30) at weblogic.security.service.RoleManagerImpl.getRoles(RoleManagerImpl.java:195) at weblogic.security.service.AuthorizationManagerImpl.isAccessAllowed(AuthorizationManagerImpl.java:383) at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at weblogic.security.service.ServiceHandler.invoke(ServiceHandler.java:55) at com.sun.proxy.$Proxy95.isAccessAllowed(Unknown Source) at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:530) at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:499) at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:215) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:213) at weblogic.jndi.internal.ServerNamingNode.lookup(ServerNamingNode.java:582) at weblogic.jndi.internal.RootNamingNode.lookup(RootNamingNode.java:81) at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:307) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:430) at javax.naming.InitialContext.lookup(Unknown Source) at oracle.jbo.server.DBTransactionImpl.lookupDataSource(DBTransactionImpl.java:1476) at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:328) at oracle.jbo.common.ampool.DefaultConnectionStrategy.connect(DefaultConnectionStrategy.java:203) at oracle.jbo.server.ApplicationPoolMessageHandler.doPoolConnect(ApplicationPoolMessageHandler.java:643) at oracle.jbo.server.ApplicationPoolMessageHandler.doPoolMessage(ApplicationPoolMessageHandler.java:439) at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:9909) at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:4538) at oracle.jbo.common.ampool.ApplicationPoolImpl.prepareApplicationModule(ApplicationPoolImpl.java:2453) at oracle.jbo.common.ampool.ApplicationPoolImpl.doCheckout(ApplicationPoolImpl.java:2263) at oracle.jbo.common.ampool.ApplicationPoolImpl.useApplicationModule(ApplicationPoolImpl.java:3162) at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:604) at oracle.jbo.http.HttpSessionCookieImpl.useApplicationModule(HttpSessionCookieImpl.java:224) at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:537) at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:532) at oracle.jbo.client.Configuration.getApplicationModule(Configuration.java:1507) at oracle.jbo.client.Configuration.createRootApplicationModule(Configuration.java:1398) at oracle.jbo.client.Configuration.createRootApplicationModule(Configuration.java:1366) at en.integration.model.adfc.utils.IntegrationModelUtils.createRootApplicationModule(IntegrationModelUtils.java:19) at en.bpm.lib.core.impl.ServiceCoreFactory.<init>(ServiceCoreFactory.java:18) at en.bpm.lib.impl.BasicProcessService.<init>(BasicProcessService.java:71)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown visitor
    Unknown visitorOnce,