glassfish
  1. glassfish
  2. GLASSFISH-2206

should admin listener be disabled and GlassFish should still come up ...

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: 9.1pe
    • Fix Version/s: not determined
    • Component/s: other
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      2,206

      Description

      See: 2195.

      (1) If a module/container throws an unexpected exception, GlassFish must log it
      and continue its startup. This must be fixed.

      This bug is for the above sub-issue.

      Frankly, I am not sure I understand. Some life cycle modules are "essential"
      which means if they don't come up, server should not come up. This bug calls for
      change in that philosophy and I am not sure if we should attempt that.

      But anyway, filing this bug as a P3.

      JF: If you feel strongly about it, please make it a P2. This is not an
      admin issue only and hence filing as "other". Also, marking this as
      enhancement.

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Tom Mueller
              Reporter:
              km
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: