dev@glassfish.java.net

Re: [V3] Web container not destroyed during domain shutdown

From: Byron Nevins <Byron.Nevins_at_Sun.COM>
Date: Tue, 12 Aug 2008 13:56:12 -0700

It would be interesting to comment out the sledgehammer and then just
start and stop GF and see what happens nowadays
The sledgehammer hides any new problems that can be added like
non-daemon threads left running.


Kedar Mhaswade wrote:
>
>
> Jan.Luehe_at_Sun.COM wrote:
>>
>> Kedar Mhaswade wrote:
>>
>>>
>>>
>>> Byron Nevins wrote:
>>>
>>>> I noticed this behavior in embedded -- a clean shutdown of GF is
>>>> impossible, the System.exit() sledgehammer has to be used...
>>>
>>>
>>> Why? Who does not "normally" respond to the "stop" call?
>>
>>
>> Is there any "stop" event?
>>
>
> When asadmin stop-domain is called, here is what happens:
> - iterate through inhabitants that satisfy the "Startup" Contract
> and call the Inhabitant.release() method on it. An example of
> startup service is:
> "com.sun.enterprise.v3.services.impl.GrizzlyService"
>
>
> Finally, System.exit is called because the "force" option is true
> by default. I am not sure what we can do to address both embedded
> and non-embedded case w.r.t. this.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>

-- 
Byron Nevins Work 408-276-4089, Home 650-359-1290, Cell 650-784-4123 - Sun Microsystems, Inc.