Hello DHIS2 -
We are seeing a similar condition as referenced in archived message :#03464. The solution offered was to restart Tomcat. Periodically, our users cannot access DHIS and we will need to reboot the server. Msg 03464 implies that we cannot run multiple instances of DHIS on the same box and that this may produce a memory leak. We are wondering what is the source of the memory leak as referenced in #03464 (and as shown below) and if this could cause our system to lock up ?
Thank you for any help.
Wilson Ramos
Messages from our system:
- INFO 2015-07-13 17:40:15,685 De-registering jdbc driver: org.postgresql.Driver@524aa681 (StartupListener.java [pool-2-thread-2])
Jul 13, 2015 5:40:15 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/dhis218] appears to have started a thread named [GT authority factory disposer] but has failed to stop it. This is very likely to create a memory leak.
Jul 13, 2015 5:40:15 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/dhis218] appears to have started a thread named [WeakCollectionCleaner] but has failed to stop it. This is very likely to create a memory leak.