Threads Failing To Stop

[sschiavo]

Hello -

Seems like whenever we need to stop GoAnywhere service we get the following messages in the catalina.out log....

Code: Select all

Apr 28, 2019 8:08:28 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [/goanywhere] appears to have started a thread named [goanywhere-GlobalLog-1] but has failed to stop it. This is very likely to create a memory leak.
Apr 28, 2019 8:08:28 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [/goanywhere] appears to have started a thread named [gad-job-1] but has failed to stop it. This is very likely to create a memory leak.
Apr 28, 2019 8:08:28 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [/goanywhere] appears to have started a thread named [ghttps-startStop-2] but has failed to stop it. This is very likely to create a memory leak.
Apr 28, 2019 8:08:28 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [/goanywhere] appears to have started a thread named [localhost-startStop-2] but has failed to stop it. This is very likely to create a memory leak.

I received a JVM memory alert a few hours later as well. It was a quick spike and everything seems normal now, just worried that these messages in the log effected the JVM memory.

Is this causing an issue? What can i do to fix this? Is there a way to manually stop these threads or see if they truly are stopped?

[Support_Nolan]

To answer your question, these alerts are Tomcat’s way of saying GoAnywhere MFT is creating threads through the tomcat service.

Since these threads are managed by GA and not Tomcat, Tomcat warns us that it could be a memory leak even though it is not.

These threads are gracefully managed by GA and they need to be left open for GA’s services to run properly.