Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8217341

Fails to start RMIConnectorServer if jdk.naming.rmi module is not observable

    Details

    • Type: Bug
    • Status: Open
    • Priority: P3
    • Resolution: Unresolved
    • Affects Version/s: 9, 10, 11, 12
    • Fix Version/s: 14
    • Component/s: core-svc
    • Labels:
      None

      Description

      As described in javax.management.remote.rmi package summary, java.management.rmi supports both JNDI form and the encoded form of RMI connector addresses. So the support for JNDI form address is not optional.

      However, if jdk.naming.rmi module is not observable, RMIConnectorServer will fail to start and its cause is:

      Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or in an application resource file: java.naming.factory.initial
          at java.naming/javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:685)
          at java.naming/javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305)
          at java.naming/javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:342)
          at java.naming/javax.naming.InitialContext.bind(InitialContext.java:417)
          at java.management.rmi/javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:713)
          at java.management.rmi/javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:496)
          ... 9 more

      Is the JNDI form an optional part of java.management.rmi? Or should it?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mchung Mandy Chung
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: