-
Type:
Task
-
Resolution: Done
-
Priority:
Blocker - P1
-
None
-
Affects Version/s: 3.0.4
-
Component/s: Async
-
None
-
Environment:mongo db 2.6
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Mongo Async JDBC driver 3.0.4 and leak, When I am using the code in a stand alone java program I am getting result back and no issue. same code if i apply in a spring app , I am seeing that I never got result back and tomcat gave me below warning. On SinleResultCallbak apply method never get the result and I keep getting below error.
Thu Mar 17 11:08:15 MDT 2016 WARN [APP:null TRACKING_ID:null ACCOUNT_NUM:null] org.apache.catalina.loader.WebappClassLoaderBase - The web application [ROOT] appears to have started a thread named [expiringMap-0] 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:1067) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) java.lang.Thread.run(Thread.java:745)