On Oct 2, 2008, at 2:30 PM, Tom Hintz wrote:
> Thread count climbed steadily from a beginning of 70 to 300+ to
> 500+ when heap was exhausted.
That's interesting. It would explain the memory error. If it's
possible, a thread dump would really help.
Also, the <memory-free-max>1M</memory-free-max> setting would help.
Its main purpose is to prevent the JVM from continually spinning when
memory is almost exhausted. In that situation, a forced restart is
One issue, though, is that 3.0 is frozen, so other than configuration
tweaks, any Resin code changes would be in 3.1 or 3.2.
> resin-interest mailing list
resin-interest mailing list