On Jan 14, 2011, at 3:35 PM, Manik Surtani wrote:
On 14 Jan 2011, at 14:29, Bela Ban wrote:
>
>
> On 1/14/11 3:08 PM, Galder Zamarreño wrote:
>> -1
>>
>> If you get an OOME, chances are the system is a pretty bad shape and you
can't really do much else at that point.
>
>
> If a put() is the culprit leading to the OOME, we can definitely do
> something !
Galder is right though, even if the put() is the culprit, concurrent threads elsewhere
(out of our control) would also be seeing OOMs and even if we free up memory by evicting,
other threads may be in an unstable state.
As a side thing, IMO, rather than trying to salvage an OOME, it's better to analise
what when wrong adding these two flags:
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/java_heap
--
Manik Surtani
manik(a)jboss.org
twitter.com/maniksurtani
Lead, Infinispan
http://www.infinispan.org
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache