We have the above System/Software & IS Memory setting for our PROD environment.
we are seeing the memory consumption surging, and eventually leads to out of memory issue, as to avoid the OutOfMemoryError we would need IS restart every week.
From the Coding perspective, we are clearing the pipeline before flows services are terminated.
Any pointers/suggestion on how to avoid these possible memory leaks in IS 10.3.
Also is there any latest IS core fix for 10.3 from software AG for the memory leaks.
Hi @Sujith_Kurian1 ,
If this is a outofmemory error, you will most likely need to raise a support ticket to get it investigated in detail. There is no one size fits all solution.
But in the meantime , I do have a few questions about the occurrence.
Are you using any tools to see the consumption increase?
Does the usage gradually increase or does it suddenly over a particular time period , indicating sudden increase in number of requests? (every weekend /monday for example)
Did the issues surface after installation of a certain fix or an update or a custom package ?
Before getting into the actual logs and memory usage data , it is helpful to understand the usage first.
Please set the following property in custom wrapper, which will generate a heap dump when IS reports OOM. This will help to isolate the actual piece of code which eat up more memory.
Generate heap dump on out of memory
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<PATH_FOLDER><file_name>. hprof