LifecycleEvent.STARTUP_EVENT fires after Servlet.init(). about glassfish

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/glassfish/issues/22
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @yaminikb
• Original Issue Closed By:@glassfishrobot

[glassfishrobot]

@glassfishrobot Commented
jluehe said:
Hi Dan,

I am able to reproduce this issue.

Here's an initial analysis:

Web modules are started, and their load-on-startup servlets
initialized, as part of WebContainer.start().

WebContainer.start() and notification of LifecycleListener instances
occur on different threads:

• LifecycleListener notification occurs on the main thread, as part of
  PEMain.run(), in this sequence:

_server.onInitialization(context);

_server.onStartup();

_server.onReady();

At the end of this sequence, the main thread notifies all threads that
have been waiting on PEMain's monitor ("this.notifyAll()").

• WebContainer.start() occurs on
  com.sun.enterprise.server.ss.ASSocketService$EntryPointThread:

at com.sun.enterprise.web.WebContainer.start(WebContainer.java:711)
at com.sun.enterprise.web.PEWebContainer.startInstance(PEWebContainer.java:649)
at
com.sun.enterprise.web.PEWebContainerLifecycle.onStartup(PEWebContainerLifecycle.java:70)
at
com.sun.enterprise.server.ondemand.ServiceGroup.startLifecycleServices(ServiceGroup.java:160)
at
com.sun.enterprise.server.ondemand.WebServiceGroup.startLifecycleServices(WebServiceGroup.java:197)
at
com.sun.enterprise.server.ondemand.WebServiceGroup.start(WebServiceGroup.java:56)
at
com.sun.enterprise.server.ondemand.ServiceGroup.startChildren(ServiceGroup.java:111)
at
com.sun.enterprise.server.ondemand.MainServiceGroup.start(MainServiceGroup.java:43)
at
com.sun.enterprise.server.ondemand.ServerEntryListenerImpl.notifyEntry(ServerEntryListenerImpl.java:61)
at
com.sun.enterprise.server.ondemand.entry.ServerEntryHelper.sendEvent(ServerEntryHelper.java:60)
at
com.sun.enterprise.server.ondemand.entry.ServerEntryHelper.generatePortEntryContext(ServerEntryHelper.java:41)
at
com.sun.enterprise.server.ss.ASSocketService.generateEntryContext(ASSocketService.java:222)
at
com.sun.enterprise.server.ss.ASSocketService$EntryPointThread.run(ASSocketService.java:420)

| #] |

This thread should not proceed with starting the WebContainer until
the main thread has fired the START_EVENT.

I'll check with Binod if he knows why this is not happening.

[glassfishrobot]

@glassfishrobot Commented
binod said:
If a servlet (that require a webcontainer) is deployed in the appserver then the
webcontainer startup doesnt wait until the server startup is complete. It
happens during the app loading itself.

I think you are hitting the If a servlet (that require a webcontainer) is deployed in the appserver then the
webcontainer startup doesnt wait until the server startup is complete. It
happens during the app loading itself.

I think you are hitting the bug 6311875..

[glassfishrobot]

@glassfishrobot Commented
qouyang said:
Transfer to Binod for better tracking as he is working on a similar issue.

[glassfishrobot]

@glassfishrobot Commented
binod said:
Checked in a fix for Checked in a fix for bug 6311875.
LifeCycleModuleService now is placed before the ApplicationLifeCycle
and PEWebContainerLifeCycle. User can set JVM option
com.sun.enterprise.server.DelayLifecycleInit to true to get the old
load order. Marking this bug as fixed..
LifeCycleModuleService now is placed before the ApplicationLifeCycle
and PEWebContainerLifeCycle. User can set JVM option
com.sun.enterprise.server.DelayLifecycleInit to true to get the old
load order. Marking this bug as fixed.

[glassfishrobot]

@glassfishrobot Commented
Was assigned to binod

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA GLASSFISH-22

[glassfishrobot]

@glassfishrobot Commented
Reported by danbrice

[glassfishrobot]

@glassfishrobot Commented
Marked as fixed on Tuesday, March 7th 2006, 10:37:06 pm