Hmmm... we do have a <memory-free-min> setting of 1MB (Scott asked about
that just before this email).  So then how would Resin still get an OOM
error?  Is there a thread in the server that watches the heap space?
Because we do a lot of in-JVM image manipulation, which takes up a LOT
of memory and quite quickly.  So if it is a timing issue, it's possible
that the heap-watcher doesn't have a chance to act quickly enough.


-----Original Message-----
[mailto:[EMAIL PROTECTED] On Behalf Of Sam
Sent: Monday, March 10, 2008 3:38 PM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] Resin cluster failure with a single
noderunning out of heap space

> We are currently looking at our watchdog process config to see why it
> did not auto-restart Resin.  I think we didn't give enough memory
> for the watchdog to detect a needed restart, and our app lost
> responsiveness before the watchdog could restart it.  But that's just
> theory.

The memory low detection happens within the server itself.  If the
server itself detects that the memory is about to be exhausted, it
exits.  The watchdog then notices that the server did not exit cleanly,
and starts a new server to replace it.

-- Sam

resin-interest mailing list

resin-interest mailing list

Reply via email to