Hi
> > Here, the log. I am quite sure how to go about troubleshooting it.
> > Any help is greatly appreciated.
> The application has a memory leak. You need to get it fixed.
> > catalina.out.prob:SEVERE: The web application [] appears to have
> > started a thread named
> > [cluster-ClusterId{value='5745ebcecdb2e06579174645',
> > description='null'}-devnymongodb01.meridiancapital.com:27017] but has
> > failed to stop it. This is very likely to create a memory leak.
There MIGHT be a memory leak but this does NOT have to be one.
I have seen several libraries that tell their maintenance threads to stop and
they actually DO, but the library itself does no join() so the thread stops a
little later (depending on the library, "little" was between a few milliseconds
and 10 minutes).
But this message is only logged when the application is stopped, so if it runs
out of memory during operation, this is a rather unrelated shutdown problem.
Anyway, check if there is a memory leak by taking a memory dump (probably using
jmap) and analyze that.
Eclipse MAT has nice tools for this.
> > MemTotal: 8061448 kB
> > MemFree: 5399052 kB
This means that your server has 5.3 GB free memory.
Do you configure the amount of memory assigned to tomcat in any way?
If you have 5.3 GB of free memory while tomcat starves, you misconfigured that.
(Misconfiguration might as well include not configuring min/max heap sizes at
all.)
Regards,
Steffen
smime.p7s
Description: S/MIME cryptographic signature
