Geronimo
  1. Geronimo
  2. GERONIMO-2340

Network Listener state not persisted across server startups

    Details

    • Type: Bug Bug
    • Status: Reopened
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0, 2.0.1, 2.0.2, 2.0.x, 2.1, 2.1.1, 2.2
    • Fix Version/s: Wish List
    • Component/s: console
    • Security Level: public (Regular issues)
    • Labels:
      None
    • Environment:

      Win XP, Geronimo 1.1.1-SNAPSHOT

    • Regression:
      Regression

      Description

      I have stopped the HTTPS and AJP Network Listeners thru "Web Servers" portlet. Upon restarting the server, these stopped listeners have started automatically. Happens with both Jetty and Tomcat.

        Activity

        Vamsavardhana Reddy created issue -
        Vamsavardhana Reddy made changes -
        Field Original Value New Value
        Summary Jetty Network Listener state not persisted across server startups Network Listener state not persisted across server startups
        Environment Win XP, Geronimo Jetty 1.1.1-SNAPSHOT Win XP, Geronimo 1.1.1-SNAPSHOT
        Description I have stopped the Jetty HTTPS and AJP Network Listeners thru "Web Servers" portlet. Upon restarting the server, these stopped listeners have started automatically. I have stopped the HTTPS and AJP Network Listeners thru "Web Servers" portlet. Upon restarting the server, these stopped listeners have started automatically. Happens with both Jetty and Tomcat.
        Hide
        Vamsavardhana Reddy added a comment -

        Same happens with JMS Listeners too.

        Show
        Vamsavardhana Reddy added a comment - Same happens with JMS Listeners too.
        Hide
        Donald Woods added a comment -

        If we change Stop to also mean load=false, then we need an Info dialog telling the Admin that the stop operation will be preserved across server restarts.

        Show
        Donald Woods added a comment - If we change Stop to also mean load=false, then we need an Info dialog telling the Admin that the stop operation will be preserved across server restarts.
        Hide
        Paul McMahan added a comment -

        Instead of changing the stop behavior to persist across server restarts (which is desirable in some cases, but not in others) it might be better to broaden the accepted values from the "load" attribute from
        true | false
        to
        automatic | manual | disabled

        Show
        Paul McMahan added a comment - Instead of changing the stop behavior to persist across server restarts (which is desirable in some cases, but not in others) it might be better to broaden the accepted values from the "load" attribute from true | false to automatic | manual | disabled
        Hide
        Donald Woods added a comment -

        Not sure why we need to change the "load" attribute. If the Portlet presents the user with stop/start and disable/enable choices, then that should suffice.
        Disable would mean set the load=false attribute
        Enable would mean remove any load=false attribute
        Stop would only stop (as today) and not touch the load attribute
        Start would only start (as today) and not touch the load attribute
        Setting a connector to Disable, would also disable the Start/Stop actions in the Portlet.

        Show
        Donald Woods added a comment - Not sure why we need to change the "load" attribute. If the Portlet presents the user with stop/start and disable/enable choices, then that should suffice. Disable would mean set the load=false attribute Enable would mean remove any load=false attribute Stop would only stop (as today) and not touch the load attribute Start would only start (as today) and not touch the load attribute Setting a connector to Disable, would also disable the Start/Stop actions in the Portlet.
        Hide
        Paul McMahan added a comment -

        Donald, I agree that your suggestion would work just as well. My suggestion was based on other similar guis I've seen like the windows services control panel which use automatic | manual | disabled.

        Show
        Paul McMahan added a comment - Donald, I agree that your suggestion would work just as well. My suggestion was based on other similar guis I've seen like the windows services control panel which use automatic | manual | disabled.
        Vamsavardhana Reddy made changes -
        Fix Version/s 1.x [ 12310618 ]
        Fix Version/s 1.1.2 [ 12312026 ]
        Fix Version/s 1.2 [ 12310181 ]
        Donald Woods made changes -
        Fix Version/s 1.x [ 12310618 ]
        Fix Version/s 2.1 [ 12312602 ]
        Fix Version/s 2.0.x [ 12312601 ]
        Donald Woods made changes -
        Assignee Donald Woods [ drwoods ]
        Hide
        Kevan Miller added a comment -

        "stopping" does not permanently disable a gbean. You'll need to "delete" the gbean if you don't want it started after a server restart. This will set load=false on the gbean.

        Show
        Kevan Miller added a comment - "stopping" does not permanently disable a gbean. You'll need to "delete" the gbean if you don't want it started after a server restart. This will set load=false on the gbean.
        Kevan Miller made changes -
        Resolution Won't Fix [ 2 ]
        Status Open [ 1 ] Closed [ 6 ]
        Hide
        Vamsavardhana Reddy added a comment -

        Stopping a connector without deleting it was possible in G 1.0. I do not know what changed from 1.0 to 1.1.

        Show
        Vamsavardhana Reddy added a comment - Stopping a connector without deleting it was possible in G 1.0. I do not know what changed from 1.0 to 1.1.
        Vamsavardhana Reddy made changes -
        Resolution Won't Fix [ 2 ]
        Regression [Regression]
        Status Closed [ 6 ] Reopened [ 4 ]
        Hide
        Vamsavardhana Reddy added a comment -

        Moving the issue to 2.1.1.

        Show
        Vamsavardhana Reddy added a comment - Moving the issue to 2.1.1.
        Vamsavardhana Reddy made changes -
        Fix Version/s 2.1 [ 12312602 ]
        Affects Version/s 2.0.x [ 12312601 ]
        Affects Version/s 2.1 [ 12312602 ]
        Fix Version/s 2.1.1 [ 12312941 ]
        Hide
        Joe Bohn added a comment -

        Donald, Since you are currently the assignee ... is there any movement on this issue or any chance we will address it in 2.1.1 (as currently indicated in the fix release)? I doubt it will be resolved in 2.1.1 given that we haven't reached consensus on a fix so perhaps it should move to 2.2.

        Show
        Joe Bohn added a comment - Donald, Since you are currently the assignee ... is there any movement on this issue or any chance we will address it in 2.1.1 (as currently indicated in the fix release)? I doubt it will be resolved in 2.1.1 given that we haven't reached consensus on a fix so perhaps it should move to 2.2.
        Donald Woods made changes -
        Affects Version/s 2.1 [ 12312602 ]
        Affects Version/s Wish List [ 12310202 ]
        Affects Version/s 2.0.x [ 12312601 ]
        Assignee Donald Woods [ drwoods ]
        Affects Version/s 1.1.1 [ 12311927 ]
        Donald Woods made changes -
        Affects Version/s 2.0 [ 12312600 ]
        Fix Version/s 2.0.x [ 12312601 ]
        Fix Version/s Wish List [ 12310202 ]
        Affects Version/s Wish List [ 12310202 ]
        Affects Version/s 2.1.1 [ 12312941 ]
        Affects Version/s 2.0.1 [ 12312730 ]
        Affects Version/s 2.0.2 [ 12312731 ]
        Affects Version/s 2.1 [ 12312602 ]
        Affects Version/s 2.0.x [ 12312601 ]
        Fix Version/s 2.1.1 [ 12312941 ]
        Affects Version/s 2.2 [ 12312965 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Vamsavardhana Reddy
          • Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development