[FINERACT-1395] Shutdown leaves java process running with leaked threads

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.5.0
• Component/s: Build

Environment

declare -x HOME="/root"
declare -x JAVA_HOME="/usr/lib/jvm/jdk-15.0.2"
declare -x LANG="C.UTF-8"
declare -x LESSCLOSE="/usr/bin/lesspipe %s %s"
declare -x LESSOPEN="| /usr/bin/lesspipe %s"
declare -x LOGNAME="root"
declare -x MAIL="/var/mail/root"
declare -x OLDPWD
declare -x PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/usr/lib/jvm/jdk-15.0.2/bin"
declare -x PWD="/root"
declare -x SHELL="/bin/bash"
declare -x SHLVL="1"
declare -x SUDO_COMMAND="/bin/bash"
declare -x SUDO_GID="0"
declare -x SUDO_UID="0"
declare -x SUDO_USER="root"
declare -x TERM="screen-256color"
declare -x USER="root"
declare -x USERNAME="root"
declare -x XDG_DATA_DIRS="/usr/local/share:/usr/share:/var/lib/snapd/desktop"

• Assignee: Unassigned
• Reporter: Thomas Kerin
• Created: 10/Sep/21 15:38
• Updated: 10/Sep/21 15:38

Description

I have installed Mifos mifosplatform-21.07.01.RELEASE which uses fineract 1.5.0

When I trigger shutdown, a number of warnings about leaked threads are written to the log. After the shutdown completes, I notice a java process is still running

Sorry if I've posted this in the wrong place or if this is covered somewhere. I've searched for the 'org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads' on the mailing list but it hasn't turned up much.

Here is the first error reported in the log, although there are several more

{{10-Sep-2021 14:37:44.339 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [fineract-provider] appears to have started a thread named [fineract_default_po}}{{ol housekeeper] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.base@11.0.11/jdk.internal.misc.Unsafe.park(Native Method) }}
{{ java.base@11.0.11/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)}}
{{ java.base@11.0.11/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)}}
{{ java.base@11.0.11/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182) }}
{{ java.base@11.0.11/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899) }}
{{ java.base@11.0.11/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054) }}
{{ java.base@11.0.11/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)}}
{{ java.base@11.0.11/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)}}
{{ java.base@11.0.11/java.lang.Thread.run(Thread.java:829) }}

 

I grepped the logs for the names of the other threads:

 

The web application [fineract-provider] appears to have started a thread named [fineract_default_pool housekeeper]
{{}}

The web application [fineract-provider] appears to have started a thread named [Scheduler1_Worker-5]
{{}}

The web application [fineract-provider] appears to have started a thread named [Scheduler1_Worker-6]
{{}}

The web application [fineract-provider] appears to have started a thread named [Scheduler1_Worker-7]
{{}}

The web application [fineract-provider] appears to have started a thread named [pool-11-thread-1]
{{}}

The web application [fineract-provider] appears to have started a thread named [Scheduler1group1_Worker-1]
{{}}

The web application [fineract-provider] appears to have started a thread named [Scheduler1group3_Worker-1]
{{}}

The web application [fineract-provider] appears to have started a thread named [pool-12-thread-1]
{{}}

The web application [fineract-provider] appears to have started a thread named [pool-13-thread-1]
{{}}

The web application [fineract-provider] appears to have started a thread named [SimpleAsyncTaskExecutor-27]