[GLASSFISH-2206] should admin listener be disabled and GlassFish should still come up ... Created: 24/Jan/07  Updated: 04/Jan/13  Resolved: 04/Jan/13

Status: Resolved
Project: glassfish
Component/s: other
Affects Version/s: 9.1pe
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: km Assignee: Tom Mueller
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issue Links:
blocks GLASSFISH-2195 GlassFish should stii start when an u... Resolved
Issuezilla Id: 2,206


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

Comment by km [ 24/Jan/07 ]


Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by Tom Mueller [ 04/Jan/13 ]

It is not clear what this issue is requesting. There are some services in GlassFish that must come up in order for the server to come up. The startup sequence allows these services to indicate that they are "essential".

Resolving this issue as "invalid".

Generated at Mon Mar 27 10:11:29 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.