Subramaniajeeva created SSHD-1179:
-------------------------------------

             Summary: Getting OOM after upgrading to 2.6.0
                 Key: SSHD-1179
                 URL: https://issues.apache.org/jira/browse/SSHD-1179
             Project: MINA SSHD
          Issue Type: Bug
    Affects Versions: 2.6.0
            Reporter: Subramaniajeeva


I upgraded mina version from 2.3.0 to 2.6.0 2 months back. Since then I could 
see the number of JVM threads keep on increasing(till ~12500), leading to OOM 
in production systems.

Here is the stack trace with 2100+ similar threads:


java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park({color:#000080}Native Method{color})
- parking to wait for *<0x000000079f7630c8>* (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at 
java.util.concurrent.locks.LockSupport.park({color:#000080}LockSupport.java:175{color})
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await({color:#000080}AbstractQueuedSynchronizer.java:2039{color})
at 
java.util.concurrent.LinkedBlockingQueue.take({color:#000080}LinkedBlockingQueue.java:442{color})
at 
org.apache.sshd.sftp.server.SftpSubsystem.run({color:#000080}SftpSubsystem.java:267{color})
at 
java.util.concurrent.Executors$RunnableAdapter.call({color:#000080}Executors.java:511{color})
at 
java.util.concurrent.FutureTask.run({color:#000080}FutureTask.java:266{color})
at 
java.util.concurrent.ThreadPoolExecutor.runWorker({color:#000080}ThreadPoolExecutor.java:1149{color})
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run({color:#000080}ThreadPoolExecutor.java:624{color})
at java.lang.Thread.run({color:#000080}Thread.java:748{color})

 

I tried to debug and I'm not able to isolate the root cause. Is it identified 
and fixed already in 2.7.0?

[~lgoldstein] Any help would be appreciated.

 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to