glassfish
  1. glassfish
  2. GLASSFISH-16013

RestartRequired: changing http port does not trigger restart required message for a standalone instance

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1_dev
    • Fix Version/s: 3.1.1_dev
    • Component/s: web_container
    • Labels:
      None
    • Environment:

      promoted build b43

      Description

      Steps to reproduce:

      1. Create a standalone instance and start it.
      2. Go to instance's configuration, System Properties page and click on Instance Values link for HTTP port.
      5. On the next page change the port to a new value, e.g. 28880, and save.
      6. Go to instance's page and notice it's still running and does not report requiring restart. CLI reports instance as running as well:

      1. a list-instances
        in1 running

      Attempting to access server on the newly specified port fails (28880), while it still responds on the old, default port 28080, hence restart is clearly required for the changes to take effect. The General tab for the instance lists new http port, even though the server is not listening on that port. This is misleading.

        Activity

          People

          • Assignee:
            Amy Roh
            Reporter:
            lidiam
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: