Jaison,
The original JVM exit does appear to have been caused by a timeout. The
JVM is going away. Are there any dump files in the working directory?
The subsequent restart failures are because the system is still too
heavily
loaded to start the JVM. The ping timeout only applies after the JVM
application is up and running. You need to extend the
wrapper.startup.timeout
property to handle startups.
Also, could you please set wrapper.debug=true and then post a log which
reproduces this? I only need a couple minutes before the restart and then
the first full failed restart.
Thanks,
Leif
maria jaison wrote:
> Hi Leif,
>
> Thank you very much for your suggestion to resolve
> Solaris console issue. Now I come out of Solaris
> console issue.
> But I am facing another issue now. If CPU is around
> 97 to 100% for more than five minutes, wrapper(3.2.0
> version) stopped in Sun Solaris 5.8. I got following
> messages in wrapper.log at last.
>
> ERROR | wrapper | 2006/07/17 08:49:53 | JVM exited
> unexpectedly.
> STATUS | wrapper | 2006/07/17 08:49:58 | Launching a
> JVM...
> ERROR | wrapper | 2006/07/17 08:51:13 | Startup
> failed: Timed out waiting for a signal from the JVM.
> ...
> .....
> ERROR | wrapper | 2006/07/17 08:56:29 | JVM did not
> exit on request, terminated
> FATAL | wrapper | 2006/07/17 08:56:29 | There were 5
> failed launches in a row, each lasting less than 300
> seconds. Giving up.
>
> Previously I faced this issue in windows. After I
> had set property wrapper.ping.timeout=0, this problem
> was resolved. But even I keep this property with zero
> value for Solaris platform, this wrapper stopping
> issue occurs.
>
> Could you please help me to come out of this problem
> also?
>
> Thanks and regards
> Jaison
|