[ https://issues.apache.org/jira/browse/JCS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744443#comment-17744443 ]
Amol D commented on JCS-235: ---------------------------- Ok will try to share > Thread leakage in JCS 3.1 with primary and secondary server configuration > ------------------------------------------------------------------------- > > Key: JCS-235 > URL: https://issues.apache.org/jira/browse/JCS-235 > Project: Commons JCS > Issue Type: Bug > Components: RMI Remote Cache > Affects Versions: jcs-3.1 > Reporter: Amol D > Priority: Major > Attachments: client-remoet-cache.ccf, primaryserver-remote-cache.ccf, > secondaryserver-remote-cache.ccf > > > We are using Apache JCS as a primary cache server in our application. The > version we are using is apache-commons-jcs3 3.1. On production environment we > have observed that this specific version is having a thread leakage issue > where on the production servers, the thread count is increasing rapidly and > reaching 20000 threads, and the system crashes due to the OutOfMemory error. > It is observed while degrading the JCS version from 3.1 to 3.0. The problem > is no longer reproducible. With the JCS 3.1 version we have also tried > implementing thread pooling, but it did not solve the problem . > Steps to reproduce - > 1) JCS configured to have primary and failover server > Please refer cache.ccf configurations attached > Check thread count via command > ps -o pid,comm,user,thcount -p <PID> > 2) Restart Primary server > After certain usage by JCS client check the thread count via below command > ps -o pid,comm,user,thcount -p <PID> > -- This message was sent by Atlassian Jira (v8.20.10#820010)