Re: [Wrapper-user] Second integration method question

[Hubert F. <Hub...@ab...>]

Hi,

IllegalStateException while stopping Wrapper? Sounds familiar somehow.

Maybe it has something to do with this?
http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1799489&group_=
id=3D39428&atid=3D425187

The solution worked for me. No more IllegalStateException on shutdown.
hub

>>> Marcin Waldowski <mwa...@su...> 22.10.2007 09:58 >>>
Hello.

My problem is related to itegrate Apache Geronimo 2.0.1 and JWS via=20
second integration method.

The same problem was touched is following thread=20
http://www.mail-archive.com/us...@ge.../msg07665.html=20

Calling "stop" class within the same JVM as calling *start* class=20
results with error in Geronimo. As David Jencks wrote it's intended to=20
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=20
increase wrapper.jvm_exit.timeout because Geronimo shutdown hook may=20
need some more time to complete (the time depend on what is deployed on=20
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=20
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.
>=20
> What is the problem you are encountering that is requiring this?
> I may have some ideas for you.
>=20
> Cheers,
> Leif
>=20
> Marcin Waldowski wrote:
>> One correction:
>>
>> Should be: I have noticed that calling "stop" class is done within =
the=20
>> same JVM as calling *start* class.
>>
>> Marcin Waldowski wrote:
>>  =20
>>> Hello.
>>>
>>> In documentation we can read:
>>> "The Wrapper works with this kind of application by starting up the=20
>>> application, as in the first method, using the "start" class and =
then=20
>>> calling the main method of the "stop" class when it is time for the=20
>>> application to be shutdown.".
>>>
>>> I have noticed that calling "stop" class is done within the same =
JVM=20
>>> as calling "stop" class. Is it possible to configure wrapper to =
call=20
>>> "stop" class in another JVM?
>>>
>>> Regards, Marcin
>>>    =20
>=20
>=20
> -------------------------------------------------------------------------=

> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/=20
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...=20
> https://lists.sourceforge.net/lists/listinfo/wrapper-user=20
>=20
>=20


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/=20
_______________________________________________
Wrapper-user mailing list
Wra...@li...=20
https://lists.sourceforge.net/lists/listinfo/wrapper-user