Java.lang.OutOfMemoryError exception

Question

Can someone comment on why OutOfMem exception is thrown based on the following GC output (OutOfMem message is actually mixed with "compacting perm gen")? does it mean it ran out of perm space? Perm space is always at 99%.
Thanks
Heap
def new generation total 14208K, used 14208K [0x029e0000, 0x03940000, 0x03940000)
eden space 12672K, 100% used [0x029e0000, 0x03640000, 0x03640000)
from space 1536K, 100% used [0x03640000, 0x037c0000, 0x037c0000)
to space 1536K, 0% used [0x037c0000, 0x037c0000, 0x03940000)
tenured generation total 189056K, used 189055K [0x03940000, 0x0f1e0000, 0x0f1e0000)
the space 189056K, 99% used [0x03940000, 0x0f1dfff8, 0x0f1e0000, 0x0f1e0000)
compacting perm gen total 16896K, used 16728K [0x0f1e0000, 0x10260000, 0x131e0000)
the space 16896K, 99% used [0x0f1e0000, 0x10236268, 0x10236400, 0x10260000)
3903.26: [Tenured: 189055K->111945K(189056K), 1.9745907 secs] 203263K->111945K(203264K) Heap after GC invocations=184:
Heap
def new generation total 14208K, used 14208K [0x029e0000, 0x03940000, 0x03940000)
eden space 12672K, 100% used [0x029e0000, 0x03640000, 0x03640000)
from space 1536K, 100% used [0x03640000, 0x037c0000, 0x037c0000)
to space 1536K, 0% used [0x037c0000, 0x037c0000, 0x03940000)
tenured generation total 189056K, used 111945K [0x03940000, 0x0f1e0000, 0x0f1e0000)
the space 189056K, 59% used [0x03940000, 0x0a6925f8, 0x0a692600, 0x0f1e0000)
compacting perjava.lang.OutOfMemoryErrorm gen total 16896K, used 16726K [0x0f1e0000, 0x10260000, 0x131e0000)
the space 16896K, 98% used [0x0f1e0000, 0x10235830, 0x10235a00, 0x10260000)
} , 2.0571367 secs]

Answer 1

That's an unfortunate interleaving of program output and
JVM output. Looks like the OutOfMemory error was thrown prior
to the GC whose output it was interkeaved into. Can you post the
entire verbose gc log? Do you see the perm gen or the
tenured gen nearly full after a GC? The snippet you posted
does not indicate memory being exhausted.
Which version of the JVM/JDK are you running? Which platform?
Can you check if you have run out of swap space and unable to
expand the Java heap? (That could be a transient condition that
manifests only occasionally because there are lotrs of processes
on your machine, which is running close to the edge of swap.
In that case, you might try running again with only this single program
running -- and sufficient swap.)