Re: [Wrapper-user] Second integration method question

[Leif M. <le...@ta...>]

Marcin,
Without using the wrapper, many applications launch a second JVM
instance simply to trigger the shutdown of the first.  This is usually
done by deleting an anchor file or sending a command via a socket.
The wrapper makes this much lighter by running this shutdown
code in the same JVM.

Are you having problems running the shudown class in the same
JVM? Or just assuming that it will not work.  Shutdown classes
tend to be quite simple in most cases.

Cheers,
Leif

Marcin Waldowski wrote:
> Hello.
>
> My problem is related to itegrate Apache Geronimo 2.0.1 and JWS via 
> second integration method.
>
> The same problem was touched is following thread 
> http://www.mail-archive.com/us...@ge.../msg07665.html
>
> Calling "stop" class within the same JVM as calling *start* class 
> results with error in Geronimo. As David Jencks wrote it's intended to 
> run shutdown.jar (from JWS point of view - "stop" class) in a different vm.
>
> The workaround is to use first integration method. However it need to 
> increase wrapper.jvm_exit.timeout because Geronimo shutdown hook may 
> need some more time to complete (the time depend on what is deployed on 
> Geronimo). So it could be better to stay with second integration method.
>
> Do you have some idea what to do to use second integration in such 
> situations?
>
> Regards, Marcin
>
> Leif Mortenson wrote:
>   
>> Marcin,
>> Not currently.  The Wrapper is only capable of monitoring a single JVM at
>> the moment.   In addition to be very heavy, controlling the lifecycle and
>> all of the possible failure modes for a second JVM would get complicated
>> in a hurry.
>>
>> What is the problem you are encountering that is requiring this?
>> I may have some ideas for you.
>>
>> Cheers,
>> Leif
>>
>> Marcin Waldowski wrote:
>>     
>>> One correction:
>>>
>>> Should be: I have noticed that calling "stop" class is done within the 
>>> same JVM as calling *start* class.
>>>
>>> Marcin Waldowski wrote:
>>>   
>>>       
>>>> Hello.
>>>>
>>>> In documentation we can read:
>>>> "The Wrapper works with this kind of application by starting up the 
>>>> application, as in the first method, using the "start" class and then 
>>>> calling the main method of the "stop" class when it is time for the 
>>>> application to be shutdown.".
>>>>
>>>> I have noticed that calling "stop" class is done within the same JVM 
>>>> as calling "stop" class. Is it possible to configure wrapper to call 
>>>> "stop" class in another JVM?
>>>>
>>>> Regards, Marcin
>>>>