Heap OOM for no apparent reason?

[Manik Surtani]

On Monday, 6 June 2011 at 17:15, Raman Gupta wrote:

> To close this off from the perspective of the gc-dev list... using
> jstack in combination with the OnOutOfMemoryError parameter was indeed
> extremely useful in determining the allocation point causing the OOME.
> 
> The allocation point was an Object deserialization triggered by
> Infinispan's unmarshalling code, and the OOME was swallowed by
> org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle()
> by catching Throwable -- which only logs the Throwable if log.trace is
> enabled (yuck).
Yes, pretty ugly - thanks for bringing this up.

https://issues.jboss.org/browse/ISPN-1155

> In addition, at the point of the allocation failure the unmarshaller
> is trying to allocate a very large array of chars which *should* be no
> longer than 6, so basically it looks like there is likely a bug
> somewhere in the application, in JGroups, or in Infinispan.
How large an array are we talking about? Could be related to 

https://issues.jboss.org/browse/ISPN-1102

which is fixed in 5.0.0.CR4.

Cheers
Manik