(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