[jira] [Commented] (OFBIZ-11250) Getting a warning while testing a unit test case

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-11250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950986#comment-16950986 ]

Devanshu Vyas commented on OFBIZ-11250:
---------------------------------------

I found this log while working on the OFBIZ-11248 ticket.

> Getting a warning while testing a unit test case
> ------------------------------------------------
>
>                 Key: OFBIZ-11250
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11250
>             Project: OFBiz
>          Issue Type: Bug
>            Reporter: Devanshu Vyas
>            Priority: Trivial
>
> While converting a XML unit test case to groovy, I encountered this warning after the test case successful completion.
>  
> WARNING: The web application [ebay] appears to have started a thread named [Log4j2-TF-8-Scheduled-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
>  sun.misc.Unsafe.park(Native Method)
>  java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
>  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
>  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
>  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
>  java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
>  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
>  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  java.lang.Thread.run(Thread.java:748)
> Oct 14, 2019 3:44:32 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
> WARNING: The web application [ebay] appears to have started a thread named [AsyncAppender-async] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
>  sun.misc.Unsafe.park(Native Method)
>  java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
>  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
>  java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403)
>  org.apache.logging.log4j.core.appender.AsyncAppender$AsyncThread.run(AsyncAppender.java:398)

--
This message was sent by Atlassian Jira
(v8.3.4#803005)