glassfish
  1. glassfish
  2. GLASSFISH-19877

SDK 4.0 - Installer is unable to create domain on Windows system

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 4.0_b82_EE7MS7
    • Fix Version/s: 4.0_b82_EE7MS7
    • Component/s: installation
    • Labels:
      None
    • Environment:

      Using build java_ee_sdk-7-b79-windows.exe, Windows 7 64 bit, JDK 1.7.0_10.

      Description

      Using Typical installation. Install location is C:\workspace\glassfish4 (non-default). Seeing the following on "Config Results" panel:

      The Configuration has failed. Please see the output below

      Creating domain
      __________________
      Executing command :C:\workspace\glassfish4\glassfish\asadmin.bat --user admin --passwordfile - create-domain --template=C:\workspace\glassfish4/glassfish/common/templates/gf/appserver-domain.jar --savelogin --checkports=false --adminport 4848 --instanceport 8080 --domainproperties=jms.port=7676:domain.jmxPort=8686:orblistener.port= 3920 domain1

      When the system tries to execute, the following error is reported
      "The system cannot find the path specified"

      I see the same issue if I use the "default" install location C:\glassfish4.

        Activity

        Hide
        Alex Pineda added a comment -

        Yes. It's my office system "wildhawk". All what I reported, I'm seeing on the same system. Have not rebooted it or done anything to it today. Just using it for testing.

        Show
        Alex Pineda added a comment - Yes. It's my office system "wildhawk". All what I reported, I'm seeing on the same system. Have not rebooted it or done anything to it today. Just using it for testing.
        Hide
        Snjezana Sevo-Zenzerovic added a comment -

        Based on analysis, this is unlikely to be a real regression after all, but recent JRE security updates probably made the issue more prominent.

        The underlying problem are known Windows installer wrapper problems with the detection of 64 bit JDK installation. In affected installations, installer probably falls back to system JRE installation and in typical installation mode same installation is propagated to GF configuration to be used for GF runtime. As the result, default domain creation fails.

        Temporary workaround is to use -j option and explicitly pass path to JDK installation while invoking installer executable. This is obviously not viable solution, so we'll need to find the least risky fix option. One improvement would be to require explicit JDK installation selection in typical installation mode. This would ensure valid JDK being used for GF runtime. Other option is to try to fix the native wrapper.

        Show
        Snjezana Sevo-Zenzerovic added a comment - Based on analysis, this is unlikely to be a real regression after all, but recent JRE security updates probably made the issue more prominent. The underlying problem are known Windows installer wrapper problems with the detection of 64 bit JDK installation. In affected installations, installer probably falls back to system JRE installation and in typical installation mode same installation is propagated to GF configuration to be used for GF runtime. As the result, default domain creation fails. Temporary workaround is to use -j option and explicitly pass path to JDK installation while invoking installer executable. This is obviously not viable solution, so we'll need to find the least risky fix option. One improvement would be to require explicit JDK installation selection in typical installation mode. This would ensure valid JDK being used for GF runtime. Other option is to try to fix the native wrapper.
        Hide
        bhavya_h_s added a comment -

        With SDK distribution (b80) , I am not facing this issue. Domain creation works fine.

        Show
        bhavya_h_s added a comment - With SDK distribution (b80) , I am not facing this issue. Domain creation works fine.
        Hide
        Alex Pineda added a comment -

        I believe your assessment is right. There's something going on with the wrapper with the detection of 64 bit JDK installation. I just tried from one of our lab system and everything install correctly if I use the -j option. I believe we should go with the workaround and explicitly pass the JDK path to the Installer.

        Show
        Alex Pineda added a comment - I believe your assessment is right. There's something going on with the wrapper with the detection of 64 bit JDK installation. I just tried from one of our lab system and everything install correctly if I use the -j option. I believe we should go with the workaround and explicitly pass the JDK path to the Installer.
        Hide
        Snjezana Sevo-Zenzerovic added a comment -

        This will be implicitly addressed in SDK b82 when we add JDK selection and verification screen into typical install sequence. As the result, domain creation should always use valid JDK 7 installation instead of whatever was used for installer runtime.

        Show
        Snjezana Sevo-Zenzerovic added a comment - This will be implicitly addressed in SDK b82 when we add JDK selection and verification screen into typical install sequence. As the result, domain creation should always use valid JDK 7 installation instead of whatever was used for installer runtime.

          People

          • Assignee:
            Snjezana Sevo-Zenzerovic
            Reporter:
            Alex Pineda
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: