We just upgraded to E1 adapter, since then we started getting:
Java.lang.OutOfMemoryError
had anybody seen this error after an E1 upgrade.
thanks
We just upgraded to E1 adapter, since then we started getting:
Java.lang.OutOfMemoryError
had anybody seen this error after an E1 upgrade.
thanks
What are the min and max Java memory settings for your IS installation? It is certainly within the realm of possibility that the newer adapter version consumes more memory.
Mark
Mark,
Thanks for the help, here is the value from Server.bat
set JAVA_MIN_MEM=1024M
set JAVA_MAX_MEM=1024M
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