wrapper-user

RE: [Wrapper-user] stopping wrapped java app on linux (rh9) SOLVE D

[Stuijt, J. <JS...@gt...>]

Hello Leigh,

Thanks for your quick response.
As soon as you mentioned the start/stop script, I realized what the cause
was. 

I have extended the script so that all needed jar-files and other resources
for the service would be copied to a lib-run subdirectory in the bin
directory. I could then recompile without disturbing the running service.

In the script, the resources were copied before the application would really
start, but also before the application would stop! So the running JVM got
its jar-files refreshed just before stopping, and this caused the strange
error message.

Changing the script to only copy the resources in case of a start solved the
problem rightaway!

Greetings,
johan




Met vriendelijke groet,
Johan Stuijt
Application Engineer
MES Expert Center
Doorkiesnummer: 075 612 79 34
 
GTI Industrie Noordwest bv
	Industrial Automation

	Houthavenkade 44  1506 PD Zaandam
	Postbus 1377  1500 AJ Zaandam
	tel.: 075 612 76 00   fax: 075 612 30 60
	www.gti-group.com/ia



-----Oorspronkelijk bericht-----
Van: Leif Mortenson [mailto:le...@ta...] 
Verzonden: Tuesday, April 13, 2004 11:23 AM
Aan: wra...@li...
Onderwerp: Re: [Wrapper-user] stopping wrapped java app on linux (rh9)

Johan,
    From the output, I am not clear where exactly that message is coming 
from.
The Wrapper or your JVM?  I am pretty sure it is the JVM because you still
get output after the dump from the Wrapper.

    Could you enable debug output using wrapper.debug=true and then post the
resulting wrapper.log file.  Don't include output from previous runs.

    Is this happening every time?   How are you asking the Wrapper to quit?
Are you using the Wrapper scripts?

    Was there a core dump from the JVM in the directory containing the 
wrapper
binary?  It might give you more info as well.

Cheers,
Leif


================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en 
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht 
onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en 
de afzender direct te informeren door het bericht te retourneren. 
================================================
The information contained in this message may be confidential 
and is intended to be exclusively for the addressee. Should you 
receive this message unintentionally, please do not use the contents 
herein and notify the sender immediately by return e-mail.
================================================

Re: [Wrapper-user] stopping wrapped java app on linux (rh9) SOLVE D

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

Hohan,
    Yes, that would do it.  I have seen this problem in the past as 
well.  Its not a
Wrapper related issue.  But Java does not always behave very nicely when the
jar files it is reading from are swapped out from underneath it.  A good 
thing
to avoid when possible.  I occasionally forget and run "ant deploy" 
before stopping
my app and will get this or other problems on shutdown.

Cheers,
Leif

Stuijt, Johan wrote:

>Hello Leigh,
>
>Thanks for your quick response.
>As soon as you mentioned the start/stop script, I realized what the cause
>was. 
>
>I have extended the script so that all needed jar-files and other resources
>for the service would be copied to a lib-run subdirectory in the bin
>directory. I could then recompile without disturbing the running service.
>
>In the script, the resources were copied before the application would really
>start, but also before the application would stop! So the running JVM got
>its jar-files refreshed just before stopping, and this caused the strange
>error message.
>
>Changing the script to only copy the resources in case of a start solved the
>problem rightaway!
>
>Greetings,
>johan
>  
>