When you have a java app that is encountering out of memory errors you need to run the vendor’s version of verboseGC and use one of the many available tools to see what is happening with your application at steady state and peak loads.
If you are processing large documents, you may need to optimize your integration services by using large document processing techniques such as nodeIterators.
You should always drop objects (especially large ones) as soon as you are finished using them in your Flow services. IS creates multiple copies of objects in memory already. You can make this worse by not following good Flow hygiene practices (drop early, drop often).
What vendor’s JVM are you using? Click on the About link in IS if you don’t know.
Mark
#Integration-Server-and-ESB#webMethods#Adapters-and-E-Standards