Open stuehmer opened 10 years ago
Updating the mongo-java-driver (to a version >=2.11.0) helped resolve a similar issue in Tomcat: SHA: bec59e1defb14cf799e854602748639271497b84
SEVERE: The web application [/play] created a ThreadLocal with key of
type [com.mongodb.DBTCPConnector$1] [...] but failed to remove it when
the web application was stopped. This is very likely to create a memory
leak.
... however the issue above remains.
Tomcat crashes sometimes (irregularily) with this message:
There is a related Mongo issue https://jira.mongodb.org/browse/JAVA-306