optimal setting for Maximum Java Heap size in mendix console

0
our Maximum Java Heap size is set to 6144. Often our memory usage goes up to 6.7 gig and then users complain about performance. then only a restart fix it. Normally under heavy processing it goes up. It just does not come down. (release the memory) Anyone had this? Also what will be the optimal Maximum Java Heap size. How much more can i set it for a large transnational system? Thanks recently got this error: 2015-06-28 16:37:49.034 CRITICAL - M2EE: java.lang.OutOfMemoryError: GC overhead limit exceeded
asked
2 answers
1

This sounds like you have a memory leak in your application, in which case only rewriting your project will be a solution. Normally the memory should be available again after a garbage collection cycle.

answered
1

As Jouke said, this is a memory leak. For what this error means exactly, see the first reply of this thread.

What you should do is make a heap dump and inspect it to see what objects are clogging your memory. Then, once you know which objects are causing the problem, you should inspect your model and make sure these objects are cleaned up properly.

To make a heap dump, you can use jmap, see here how to.

To analyse the heap dump, you can use Eclipse, in combination with Memory Analyser

answered