We have an application running that runs out of Java heap space memory every once in a while. There are a lot of large microflows handling big sets of objects that are called through scheduled events. Most, if not all, are already using batches to work through everything but the heap error has happened 3 times over the past 2 weeks. Is there a way to fine tune the log or microflow such that we can pin point more accurately what is causing the issue? The objects in cache before the crash yield no conclusive evidence since the application crashed with 5k, 10k and 20k objects in cache. Increase the java heap memory won't definitely sovle the problem.
↧