[TriLUG] Runaway Java Process

[Andrew C. Oliver]

kill -3 the process gives you a thread dump to most likely the console 
log (hopefully you disabled the console appender which is just 
duplicating server.log) and redirected this somewhere else

However if it is an occasional run away process then turn on garbage 
collection logging     -Xloggc:<file>    log GC status to a file with 
time stamps

Make sure you don't have RMI DGC enabled: 
http://blogs.jboss.com/blog/acoliver/2006/03/21/If_you_dont_do_this_JBoss_will_run_really_slowly.txt

(I patched I think 4.0.4 to stop doing that at least for Linux/Unix if 
you use run.sh/run.conf)

more than likely you have some memory leaking. 

-Andy

Steve Hoffman wrote:
> I have a runaway java process that happens every 3 or 4 months or so 
> that we
> can't seem to identify the cause of.  top shows that this one process is
> running @300%CPU and 24%RAM (full 2GB).  In the past we've just pulled 
> this
> server from the load balancer, restarted jboss (using java 1.5.0_10) and
> gone on with our lives, but it makes me feel incredibly dumb to not 
> know how
> to isolate the issue.
>
> What tools can anyone recommend to identify the cause of a runaway 
> thread in
> a multi threaded application and even better, once identified is there 
> a way
> to kill or renice a single thread as opposed to the whole process?
>
> Many thanks in advance.
>
> Steve


-- 
>From Windows/Exchange to Linux/Meldware
Buni Meldware Communication Suite
Email, Calendaring, ease of configuration/administration
http://buni.org