OutOfMemoryError & GC overhead limit exceeded with 10.1.3.4 SOA Suite
By clemens.utschig on May 26, 2009
As I have seen a few customers running into a strange OOM recently - I figured I publish this.
First, how to see what is actually going on?
If you run on Sun JDK 1.5.0_7+ you can set a vm flag (in the startup properties for the vm, e.g. $OH/opmn/conf/opmn.xml -> component -> startup) named -XX:+HeapDumpOnOutOfMemoryError. This will dump the complete heap every time an OOM occurs in the format of java_
Once you have that mega file (mega is depending on your heap settings - you can use one of the heap analyzers out there, my personal favorite can be found here.
If you hit the above problem (which is an XDK bug) - you should see a bunch of JXTransformer objects, that hold on to a dom document, in fact the last output doc of the xslt transformation. So the more XSLs you are using the more likely you are to hit this bug.
(6065704 - soa stress - memory leaks in xml transformer when processing large payload)
To find out which version you need the patch for - go to $OH/lib and open xmlparserv2.jar - in there you find .xdk_version - which tells you the version you need to search by on metalink.