|
From: Leif M. <le...@ta...> - 2004-04-14 16:21:48
|
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
>
>
|