Catching OutOfMemoryErrors using try/catch isn't the way to go. Like Taariq I
advice monitoring your app and make heap dumps for memory analysis purposes.
A tip: If you add -XX:+HeapDumpOnOutOfMemoryError as a JVM startup parameter
you can have JVM automatically create a heap dump in the unfortun
I don't know if you've been trying this in the meantime, but have the JVM write
a heap dump when it runs out of memory.
Then you can see what's going on, fix it, and not have to try to handle it at
all.
Taariq
-Original Message-
From: Sri [mailto:sri.tec...@googlemail.com]
Sent: 18 Ma
