[Rabbit-proxy-users] Re: OutOfMemoryError
Brought to you by:
ernimril
From: Sam <Sam...@Co...> - 2004-04-03 15:37:27
|
Right now at any given time the load is about 25 users tops. I have the cache set to 30 gigs but I think it is at about 60 megs when that happens. It is normally around 60 megs. The index does not seem to get very big but I guess it would if I actually used 30 gigs for cache. This seems to happen every 24 hours, seems like exactly 24 hours. I will need to redirect to a file to get the further information. Thanks. Sam Robert Olofsson wrote: > Sam wrote: > >> I know the error is pretty clear but the box is truly not running out >> of memory as far as I can see. >> Both RAM and disk are plenty. >> >> [03/Apr/2004:11:21:24 GMT][ERROR][java.lang.OutOfMemoryError] > > > Depending on how big load you expect to take you can increase the > memory for java. > Normally it has a 64 MB heap size, when that is used one gets a > OutOfMemoryError > (garbage collector has to fail to free memory).. > > "java -Xmx128m rabbit.proxy.Proxy " to give rabbit 128 MB heap... > > If rabbit does have a memory leak (Im not aware of any, but that say > very little) > this will help keep rabbit running longer, but not cure the problem. > If you have to big load for the normal 64 MB heap this will cure the > problem... > > How big is the cache when this happens? The cache index is stored in > memory... > How long time has rabbit been running? (in days/hours/seconds/minutes) > How many requests have rabbit served since the start > How many request handlers do rabbit have at this time? Can you get a > thread > dump? send a SIGQUIT to it (kill -QUIT <pid of rabbit process>) and > you will > get a full stack trace for all threads in the jvm (hopefully this > works after a > OOME). > The stack trace will come on the console you started rabbit in, so you > may want to > redirect stdout to a file when you start rabbit. > > /robo > > > |