continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter" <brett.por...@gmail.com>
Subject Re: continuum crashes regularly because of JVM - why?
Date Thu, 17 Jul 2008 19:28:20 GMT
This usually indicates that java has hung - is Continuum responsive at
those times?

Some things you can try to do:
- extend the timeout in wrapper.conf
- if it does appear hung, try kill -3 on the process or "run.sh dump"
to get a stack trace in the logs, which should help identify the
problem if it responds.

I've noticed that it can become unresponsive if you do an unusually
high amount of disk i/o (eg, setting the build to do a clean checkout
every time). It's worth considering if your build schedule is too
ambitious.

Cheers,
Brett

2008/7/17 Y.B. <yegor256@yahoo.com>:
> This is what I receive in wrapper.log regularly:
>
> (Continuum works for some time 30-40 minutes and than crashes with this)
>
> ERROR  | wrapper  | 2008/07/16 11:40:17 | JVM appears hung: Timed out
> waiting for signal from JVM.
> ERROR  | wrapper  | 2008/07/16 11:40:22 | JVM did not exit on request,
> terminated
> STATUS | wrapper  | 2008/07/16 11:40:30 | Launching a JVM...
> WARN   | wrapper  | 2008/07/16 11:40:37 | JVM process was still running
> after receiving a SIGCHLD signal.
> ERROR  | wrapper  | 2008/07/16 11:40:58 | Startup failed: Timed out waiting
> for a signal from the JVM.
> ERROR  | wrapper  | 2008/07/16 11:40:58 | JVM did not exit on request,
> terminated
> STATUS | wrapper  | 2008/07/16 11:41:02 | Launching a JVM...
> WARN   | wrapper  | 2008/07/16 11:41:06 | JVM process was still running
> after receiving a SIGCHLD signal.
> ERROR  | wrapper  | 2008/07/16 11:41:32 | Startup failed: Timed out waiting
> for a signal from the JVM.
> ERROR  | wrapper  | 2008/07/16 11:41:32 | JVM did not exit on request,
> terminated
> STATUS | wrapper  | 2008/07/16 11:41:37 | Launching a JVM...
> WARN   | wrapper  | 2008/07/16 11:41:43 | JVM process was still running
> after receiving a SIGCHLD signal.
> ERROR  | wrapper  | 2008/07/16 11:42:07 | Startup failed: Timed out waiting
> for a signal from the JVM.
> ERROR  | wrapper  | 2008/07/16 11:42:07 | JVM did not exit on request,
> terminated
> STATUS | wrapper  | 2008/07/16 11:42:08 | JVM exited in response to signal
> SIGKILL (9).
> ERROR  | wrapper  | 2008/07/16 11:42:08 | Unable to start a JVM
> STATUS | wrapper  | 2008/07/16 11:42:08 | <-- Wrapper Stopped
>
> Any ideas, suggestions?
>
> Thanks
>
> Y.B.
>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 3274 (20080716) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Mime
View raw message