[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
|Fix Version/s:||not determined|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Operating System: All
(1) If a module/container throws an unexpected exception, GlassFish must log it
This bug is for the above sub-issue.
Frankly, I am not sure I understand. Some life cycle modules are "essential"
But anyway, filing this bug as a P3.
JF: If you feel strongly about it, please make it a P2. This is not an
|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".