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
Stuijt, Johan wrote:
> Hello everybody!
>
>
>
> Has anybody an explanation and/or solution for the following message
> appearing in my wrapper/logs/application.log file when I tell the
> wrapper to stop the application on linux redhat 9?
>
> I have my own shutdown-hook registered and it does not run because it
> should have said something in this logfile.
>
> I use the WrapperListener integration method.
>
>
>
>
>
> ****************
>
> Another exception has been detected while we were handling last error.
>
> Dumping information about last error:
>
> ERROR REPORT FILE = (N/A)
>
> PC = 0x5140a7c3
>
> SIGNAL = 11
>
> FUNCTION NAME = (N/A)
>
> OFFSET = 0xFFFFFFFF
>
> LIBRARY NAME = (N/A)
>
> Please check ERROR REPORT FILE for further information, if there is any.
>
> Good bye.
>
> JVM exited unexpectedly.
>
> TERM trapped. Shutting down.
>
> <-- Wrapper Stopped
>
>
>
> First time wrapper user.
>
|