weblogic.management.NoAccessRuntimeException

Access not allowed for subject: principals=[], on ResourceType: ServerRuntime Action: execute, Target: reconnectToAdminServer

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

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

Solutions on the web195

  • via Oracle Community by 3004, 1 year ago
    Access not allowed for subject: principals=[], on ResourceType: ServerRuntime Action: execute, Target: reconnectToAdminServer
  • Access not allowed for subject: principals=[system], on ResourceType: ServerRuntime Action: execute, Target: reconnectToAdminServer
  • via techpaste.com by Unknown author, 1 year ago
    Access not allowed for subject: principals=[], on ResourceType: ServerRuntime Action: execute, Target: reconnectToAdminServer
  • Stack trace

    • weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on ResourceType: ServerRuntime Action: execute, Target: reconnectToAdminServer at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108) at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138) at weblogic.management.internal.RemoteMBeanServerImpl_811_WLStub.invoke(UnknownSource) at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946) at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481) at weblogic.management.runtime.ServerRuntimeMBean_Stub.reconnectToAdminServer(ServerRuntimeMBean_Stub.java:1315) at weblogic.management.ManagedServerLocator.discoverManagedServer(ManagedServerLocator.java:260) at weblogic.management.ManagedServerLocator.discoverAllKnownServers(ManagedServerLocator.java:130) at weblogic.management.AdminServerAdmin.discoverManagedServers(AdminServerAdmin.java:527) at weblogic.management.AdminServerAdmin.finishPostListen(AdminServerAdmin.java:473) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:1041) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359) at weblogic.Server.main(Server.java:32) Caused by: weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on ResourceType: ServerRuntime Action: execute, Target: reconnectToAdminServer at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.wlsRun(SecurityHelper.java:557) at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.run(SecurityHelper.java:453) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at weblogic.management.internal.SecurityHelper.isAccessAllowed(SecurityHelper.java:347) at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:764) at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(UnknownSource) at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466) at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144) at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

    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

    You’re the first here who have seen this exception.