Sorry about that. I noticed it a couple weeks ago and have fixed it in the
CVS version. It was a stupid typo in the C source. One line change.
It will be in the 3.0.4 release.
This new version also includes a couple of bug fixes with the sh and bash
scripts used to control the Wrapper.
Could you check out the latest from CVS? It will fix your problems. I'll
try to get a new version released fairly soon, but there are a few more
things that I want to get into the next release.
Cheers,
Leif
Sergey Kapustin wrote:
> Hello,
> I'm trying out the wrapper and ran into one problem. When I request a
> thread dump through the shell script first time, everything works as
> expected. Although, when I try to get dump for the second time, the
> wrapper simply kills the JVM.
> wrapper version is 3.0.3, it was tested on Solaris 5.8 and RedHat
> Linux 7.2
> Could you please explain why the wrapper is doing it and how to fix it?
>
> Thank you
>
> Here is the wrapper log with normal dump:
> --------------------------------------------------
> wrapper | Dumping JVM state.
> jvm 1 | Full thread dump:
> .....
>
> This what happens when dump is requested for the second time:
> --------------------------------------------------
> wrapper | Shutting down.
> wrapper | wrapperStopProcess(0) called.
> wrapper | Sending stop signal to JVM
> wrapperp | send a packet 101 : NULL
> jvm 1 | Received a packet 101 :
> jvm 1 | Thread, Wrapper-Connection, handling the shutdown process.
> jvm 1 | calling listener.stop()
> jvm 1 | WrapperSimpleApp: stop(0)
> jvm 1 | returned from listener.stop()
> jvm 1 | Send a packet 107 : 0
> jvm 1 | Closing socket.
> wrapperp | read a packet 107 : 0
> wrapper | JVM signalled that it was stopped.
> wrapperp | socket read no code (closed?).
> jvm 1 | calling System.exit(0)
> wrapper | JVM exited normally.
> wrapper | <-- Wrapper Stopped
>
|
