glassfish
  1. glassfish
  2. GLASSFISH-16146

Umbrella bug. Created a domain with master password. Several start commands failed.

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: future release
    • Component/s: admin
    • Labels:
      None

      Description

      Build 43. Sparc machine.
      1) Created a new domain with master password. I.e. was used such command:

      asadmin --passwordfile ./password.txt --user admin create-domain --domaindir /opt/glassfish3/glassfish/domains --adminport 9999 --instanceport 4444 --savemasterpassword=true --usemasterpassword=true --savelogin=false --checkports=true --nopassword=false domain12

      2) Started domain
      3) Created a cluster: asadmin --passwordfile ./password.txt --port 9999 --host localhost --user admin create-cluster c1
      Command create-cluster executed successfully.
      4) Created a local instance: asadmin --passwordfile ./password.txt --port 9999 --host localhost --user admin create-local-instance --cluster c1 --node localhost-domain12 in9
      Rendezvoused with DAS on localhost:9999.
      Port Assignments for server instance in9:
      JMX_SYSTEM_CONNECTOR_PORT=28689
      JMS_PROVIDER_PORT=27679
      HTTP_LISTENER_PORT=28083
      ASADMIN_LISTENER_PORT=24851
      JAVA_DEBUGGER_PORT=29009
      IIOP_SSL_LISTENER_PORT=23820
      IIOP_LISTENER_PORT=23700
      OSGI_SHELL_TELNET_PORT=26666
      HTTP_SSL_LISTENER_PORT=28184
      IIOP_SSL_MUTUALAUTH_PORT=23920
      Command create-local-instance executed successfully.

      5) Started a local instance: asadmin --passwordfile ./password.txt --port 9999 --host localhost --user admin start-local-instance --node localhost-domain12 in9
      Waiting for in9 to start .................................
      Successfully started the instance: in9
      instance Location: /opt/glassfish3/glassfish/nodes/localhost-domain12/in9
      Log File: /opt/glassfish3/glassfish/nodes/localhost-domain12/in9/logs/server.log
      Admin Port: 24851
      Command start-local-instance executed successfully.
      6) Stopped a local instance: asadmin --passwordfile ./password.txt --port 9999 --host localhost --user admin stop-local-instance --node localhost-domain12 in9
      Waiting for the instance to stop ...
      Command stop-local-instance executed successfully.

      Then tried to execute start-instance, restart-instance, start-cluster, all these commands failed. This is an umbrella bug for start with master password issues. For domains without master password, all these commnds worked fine.

        Issue Links

          Activity

          easarina created issue -
          easarina made changes -
          Field Original Value New Value
          Component/s admin [ 10589 ]
          easarina made changes -
          Link This issue depends on GLASSFISH-16147 [ GLASSFISH-16147 ]
          easarina made changes -
          Link This issue depends on GLASSFISH-16149 [ GLASSFISH-16149 ]
          easarina made changes -
          Link This issue depends on GLASSFISH-16150 [ GLASSFISH-16150 ]
          Hide
          Nazrul added a comment -

          Requesting Bhakti to investigate if these are real issues.

          Show
          Nazrul added a comment - Requesting Bhakti to investigate if these are real issues.
          Nazrul made changes -
          Assignee Nazrul [ ai109478 ] Bhakti Mehta [ bhaktimehta ]
          Hide
          Byron Nevins added a comment -

          Bhakti - take a look at 16150 comments from me.

          Try replacing the relative path of the password file to an absolute path (in the asadmin commands). Should only take a couple minutes to try...

          Show
          Byron Nevins added a comment - Bhakti - take a look at 16150 comments from me. Try replacing the relative path of the password file to an absolute path (in the asadmin commands). Should only take a couple minutes to try...
          Bhakti Mehta made changes -
          Tags 3_1-next
          Bhakti Mehta made changes -
          Fix Version/s 3.2 [ 10969 ]
          Nazrul made changes -
          Tags 3_1-next 3_1-next 3_1_1-review
          Hide
          Nazrul added a comment -

          We should look in this issue during 3.1.1

          Show
          Nazrul added a comment - We should look in this issue during 3.1.1
          Hide
          Nazrul added a comment -

          GlassFish 3.1 is behaving as expected. We never send master password over the wire. If user sets a master password, then 3.1 offer the following options:

          1) Use create-local-instance --savemasterpassword option to save the master password locally
          2) Use change-master-password --savemasterpassword option to save the master password locally

          Converting these 3 issues to Improvement to investigate if we can make life any easier without compromising security.

          Show
          Nazrul added a comment - GlassFish 3.1 is behaving as expected. We never send master password over the wire. If user sets a master password, then 3.1 offer the following options: 1) Use create-local-instance --savemasterpassword option to save the master password locally 2) Use change-master-password --savemasterpassword option to save the master password locally Converting these 3 issues to Improvement to investigate if we can make life any easier without compromising security.
          Nazrul made changes -
          Issue Type Bug [ 1 ] Improvement [ 4 ]
          Bhakti Mehta made changes -
          Tags 3_1-next 3_1_1-review 3_1-next
          Bhakti Mehta made changes -
          Tags 3_1-next 3_1-next 3_1_1-scrubbed
          Jill Sato made changes -
          Fix Version/s 4.0 [ 10970 ]
          Fix Version/s 3.2 [ 10969 ]
          Hide
          Tom Mueller added a comment -

          Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issues was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.

          Show
          Tom Mueller added a comment - Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issues was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.
          Tom Mueller made changes -
          Tags 3_1-next 3_1_1-scrubbed ee7ri_cleanup_deferred
          Fix Version/s future release [ 11148 ]
          Fix Version/s 4.0 [ 10970 ]

            People

            • Assignee:
              Bhakti Mehta
              Reporter:
              easarina
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: