PreciseAyo commented on issue #721: URL: https://github.com/apache/mina-sshd/issues/721#issuecomment-3700743563
What is the status on this bug fix considering that it's from April? I have several clients that are experiencing OOM issues in relation to this issue and we need a resolution ASAP. I have also opened up a ticket that relates to this issue under https://github.com/apache/mina-sshd/issues/859. All the timer-threads that spin up in our environments have the following stack trace: at jdk/internal/misc/Unsafe.park(Native Method) at java/util/concurrent/locks/LockSupport.parkNanos(LockSupport.java:252(Compiled Code)) at java/util/concurrent/locks/AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1679(Compiled Code) at java/util/concurrent/ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182(Compiled Code)) at java/util/concurrent/ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899(Compiled Code)) at java/util/concurrent/ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062(Compiled Code)) at java/util/concurrent/ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122(Compiled Code)) at java/util/concurrent/ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635(Compiled Code)) at java/lang/Thread.run(Thread.java:853(Compiled Code)) Our expectation is that as apache is creating these timer threads that they need to be cleaned up by apache as well which is not currently happening. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
