This content has been marked as final. Show 2 replies
It seems to be a memory leak problem. Have you found OutOfMemory messages in the log file? On the other hand, it is not necessary to schedule the GC execution because it is managed by the JVM.
I recommend you to get a heap dump and then analyze it with a tool like Memory Analyzer (MAT) http://www.eclipse.org/mat/ in order to find the root cause of this problem.
Please see this thread, perhaps it could help you
Memory leak on cluster
There are several OutOfMemory in log files. The GC is managed by JVM, we know, but this is just the temporary solution we applied, at least not to crash the server.
Thanks for your thread. We had already dumped the memory & analyzing.
However, in our case, session-timesout is defined 20, in web.xml.