Environment:
OS - Linux Suse 9.1
Java - 1.4.2_05
Wrapper 3.1.1
The wrapper (JVM?) generates native code exception
messages hs_err_XXX at application shutdown. In the
enclosed wrapper.log this line indicates application
startup
INFO | jvm 1 | 2004/10/02 00:21:38 | loading
logging properties...
and this line indicates application shutdown:
INFO | jvm 1 | 2004/10/02 19:26:34 | closing log
stream
I haven't noticed an adverse impact on the application
performance or stability, however I am concerned that
this bug may still cause a disruption to our shutdown
processes which involves shutdown hooks. Also
hs_err_XXX messages are logged in the same directory
where the application jar is located thus polluting the
file system.
Error Logs
Logged In: YES
user_id=228081
hs_err_<pid> files are output by some JVMs when the JVM
itself crashes. To date, I have not seen any such problems
that ended up being caused by the Wrapper. These are
actually why the Wrapper was created originally. :-)
In pretty much all reproduceable cases, this will also
happen without the Wrapper in the equation.
How reproduceable is this? If it is easy to reproduce,
could you set the wrapper.debug=true property and then post
the full wrapper.log file from a single JVM run showing this
crash, using the upload button at the bottom of this issue.
I will make sure that it does not look suspicious.
Cheers,
Leif