-
Bug
-
Resolution: Fixed
-
P2
-
None
-
b03
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8334955 | 23.0.1 | Kevin Walls | P2 | Resolved | Fixed | b02 |
JDK-8333746 | 23 | Kevin Walls | P2 | Resolved | Fixed | b29 |
An app server testing with JDK 23 builds is failing since JDK-8296244.
<May 30, 2024, 10:07:33,634 AM Coordinated Universal Time> <Notice> <JMX> <BEA-149535> <JMX Resiliency Activity Server=AdminServer : Connection already exists for the server. Did not attempt to connect to the server>
<May 30, 2024, 10:07:34,356 AM Coordinated Universal Time> <Warning> <RMI> <BEA-080003> <A RuntimeException was generated by the RMI server: javax.management.remote.rmi.RMIConnectionImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.String;Ljavax.security.auth.Subject;)
weblogic.management.NoAccessRuntimeException: [Management:141302]Access not allowed for Subject: principals=[], on resource Domain, action: execute, target lookupTarget..
weblogic.management.NoAccessRuntimeException: [Management:141302]Access not allowed for Subject: principals=[], on resource Domain, action: execute, target lookupTarget.
at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.run(SecurityHelper.java:868)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:344)
<May 30, 2024, 10:07:33,634 AM Coordinated Universal Time> <Notice> <JMX> <BEA-149535> <JMX Resiliency Activity Server=AdminServer : Connection already exists for the server. Did not attempt to connect to the server>
<May 30, 2024, 10:07:34,356 AM Coordinated Universal Time> <Warning> <RMI> <BEA-080003> <A RuntimeException was generated by the RMI server: javax.management.remote.rmi.RMIConnectionImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.String;Ljavax.security.auth.Subject;)
weblogic.management.NoAccessRuntimeException: [Management:141302]Access not allowed for Subject: principals=[], on resource Domain, action: execute, target lookupTarget..
weblogic.management.NoAccessRuntimeException: [Management:141302]Access not allowed for Subject: principals=[], on resource Domain, action: execute, target lookupTarget.
at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.run(SecurityHelper.java:868)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:344)
- backported by
-
JDK-8333746 JMX attaching of Subject does not work when security manager not allowed
- Resolved
-
JDK-8334955 JMX attaching of Subject does not work when security manager not allowed
- Resolved
- relates to
-
JDK-8296244 Alternate implementation of user-based authorization Subject APIs that doesn’t depend on Security Manager APIs
- Resolved
- links to
-
Commit openjdk/jdk/23f2c97f
-
Commit openjdk/jdk/bcf4bb48
-
Review openjdk/jdk/19624
-
Review openjdk/jdk/19810
(2 links to)