glassfish
  1. glassfish
  2. GLASSFISH-15638

Show "restart required" status when IIOP service configuration / port is changed

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1_b38
    • Fix Version/s: 4.1
    • Component/s: orb
    • Labels:
      None

      Description

      Per Admin Guide, "Impact of Configuration Changes" section, Configuration Changes That Require Server Restart include: Managing IIOP services.

      However, "restart required" is not indicated by Admin CLI/GUI when IIOP service configuration is changed.

      Example Steps:

      on Admin Console

      Click Server Config - ORB - IIOP Listeners - orb-listener-1 - Listener Port - Change to "3702" - Save

      Expected: Restart Required notification is displayed.

        Activity

        Hide
        Ken Cavanaugh added a comment -

        One last question: is this fix needed for 3.1, or should we defer it to 3.2?

        Show
        Ken Cavanaugh added a comment - One last question: is this fix needed for 3.1, or should we defer it to 3.2?
        Hide
        kumara added a comment -

        This is arguably likely to cause confusion to the end users but is lower priority because –

        1. port change is a one-time activity in most real deployments
        2. After port change, a user is likely to try the application to verify that it works and will discover the problem.
        3. Restart is a natural first step towards solving the problem.

        I would recommend addressing it in next release and documenting in release notes that clusters/server instances need to be restarted for any configuration changes to IIOP service to take effect.

        Show
        kumara added a comment - This is arguably likely to cause confusion to the end users but is lower priority because – 1. port change is a one-time activity in most real deployments 2. After port change, a user is likely to try the application to verify that it works and will discover the problem. 3. Restart is a natural first step towards solving the problem. I would recommend addressing it in next release and documenting in release notes that clusters/server instances need to be restarted for any configuration changes to IIOP service to take effect.
        Hide
        Ken Cavanaugh added a comment -

        Moving to 3.2 per Kumara's comment.

        Should add some of the simple cases of ORB dynamic reconfiguration in that release in any case.

        Show
        Ken Cavanaugh added a comment - Moving to 3.2 per Kumara's comment. Should add some of the simple cases of ORB dynamic reconfiguration in that release in any case.
        Hide
        Scott Fordin added a comment -

        Added topic under "Restart Required" umbrella issue (http://java.net/jira/browse/GLASSFISH-16040) in 3.1 Release Notes.

        Show
        Scott Fordin added a comment - Added topic under "Restart Required" umbrella issue ( http://java.net/jira/browse/GLASSFISH-16040 ) in 3.1 Release Notes.
        Hide
        Tom Mueller added a comment -

        Targeting for 4.0.1 as bugs related to the orb do not need to be fixed for the RI/SDK.

        Show
        Tom Mueller added a comment - Targeting for 4.0.1 as bugs related to the orb do not need to be fixed for the RI/SDK.

          People

          • Assignee:
            Harshad Vilekar
            Reporter:
            Harshad Vilekar
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: