Re: JMX OutOfMemoryError: Requested array size exceeds VM limit
mikesmith813@gmail.com writes:
Job_Executor6:class com.sun.jmx.remote.opt.util.JobExecutor java.lan.OutOfMemoryError: Requested array size exceeds VM limit
There is a ?g? missing in ?.lan.? above. Possibly, the error
message was edited by someone? Possibly by a human being?
Hearing that it crashed after about 70 hours, my first idea
was a growing array. The stack partially confirms this, but
unexpectedly, it is not a java.util.ArrayList, but a
java.io.ByteArrayOutputStream.
at java.util.Arrays.copyOf(Unknown Source)
at java.io.ByteArrayOutputStream.grow(Unknown Source)
at java.io.ByteArrayOutputStream.ensureCapacity(Unknown Source)
at java.io.ByteArrayOutputStream.write(Unknown Source)
The next lines look like someone is trying to serialize.
at java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source)
at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknown Source)
at java.io.ObjectOutputStream.writeObject0(Unknown Source)
at java.io.ObjectOutputStream.writeObject(Unknown Source)
Possible that someone is trying to write a VLO (very large
object) and during serialization, there is not enough memory
for some array buffering the output. The VLO might grow
during about 70 hours until it eventually has grown too
large for serialization. It might contain an array itself
not directly visible in the stack that has grown that much.