|
From: Leif M. <le...@ta...> - 2007-10-19 16:28:23
|
Marcin, Answered you on the 17th: --- 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: > Hello. > > Had anyone similar problem? > > Regards, Marcin > > 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 >>> |