[Wrapper-user] Garbage collection and timeouts

[<da...@ix...>]

Ugh.  It looks like GC takes too long sometimes and Wrapper things the JVM
has hung:

INFO   | jvm 1    | 2003/07/15 20:36:49 | [GC
INFO   | jvm 1    | 2003/07/15 20:36:50 |  451745K->409600K(506368K), 1.1287680 secs]
INFO   | jvm 1    | 2003/07/15 20:36:51 | [Full GC
DEBUG  | wrapperp | 2003/07/15 20:36:52 | send a packet 103 : ping
DEBUG  | wrapperp | 2003/07/15 20:36:58 | send a packet 103 : ping
DEBUG  | wrapperp | 2003/07/15 20:37:04 | send a packet 103 : ping
DEBUG  | wrapperp | 2003/07/15 20:37:10 | send a packet 103 : ping
DEBUG  | wrapperp | 2003/07/15 20:37:16 | send a packet 103 : ping
ERROR  | wrapper  | 2003/07/15 20:37:22 | JVM appears hung: Timed out waiting for signal from JVM.
ERROR  | wrapper  | 2003/07/15 20:37:22 | JVM did not exit on request, terminated


Yeah, I am trying to figure out who is calling System.gc() once a second.

Anyway, since System.gc() causes all other threads to pause until it's
done... and no matter what timeout you set in wrapper's config file, there
will eventually be a case where gc takes just a bit longer... how to handle
this in the general case?  Is there anyway?

Meanwhile, time to figure out who's banging away on gc, read up on GC
tuning, and yell at the developer to not allocate so much shit.  :-/
Any recommendations?

mrc
-- 
     Mike Castle      da...@ix...      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc