[jira] [Commented] (JCS-235) Thread leakage in JCS 3.1 with primary and secondary server configuration
[ https://issues.apache.org/jira/browse/JCS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782321#comment-17782321 ] Thomas Vandahl commented on JCS-235: [~Amol D]: Any news? Did the workaround help? > 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: JCS_3.1_HeapDump.log, 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 2 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 > 2) Restart Primary server > After certain usage by JCS client check the thread count via below command > ps -o pid,comm,user,thcount -p > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCS-235) Thread leakage in JCS 3.1 with primary and secondary server configuration
[
https://issues.apache.org/jira/browse/JCS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767179#comment-17767179
]
Thomas Vandahl commented on JCS-235:
The thread dump looks strange. Obviously, you have multiple threads for the
same CacheEventQueue which should not be possible with your configuration.
There should be exactly one "CacheEventQueue.QProcessor-<>Thread-x"
per configured cache. The thread dump shows up to 10. I suggest to investigate
this.
If you want to mimic the exact behaviour of JCS 3.0, try the following thread
pool configuration and see what happens.
{code:bash}
jcs.auxiliary.RCluster1.attributes.EventQueueType=POOLED
jcs.auxiliary.RCluster1.attributes.EventQueuePoolName=cluster_cache_event_queue
# Cluster Cache pool
thread_pool.cluster_cache_event_queue.boundarySize=0
thread_pool.cluster_cache_event_queue.useBoundary=false
thread_pool.cluster_cache_event_queue.maximumPoolSize=1
thread_pool.cluster_cache_event_queue.minimumPoolSize=0
thread_pool.cluster_cache_event_queue.keepAliveTime=1
thread_pool.cluster_cache_event_queue.startUpSize=0
thread_pool.cluster_cache_event_queue.whenBlockedPolicy=RUN
{code}
> 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: JCS_3.1_HeapDump.log, 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 2 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
> 2) Restart Primary server
> After certain usage by JCS client check the thread count via below command
> ps -o pid,comm,user,thcount -p
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JCS-235) Thread leakage in JCS 3.1 with primary and secondary server configuration
[ https://issues.apache.org/jira/browse/JCS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761990#comment-17761990 ] Amol D commented on JCS-235: Attached JCS_3.1_HeapDump.log shared by one of my colleagues. Hope it helps. > 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: JCS_3.1_HeapDump.log, 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 2 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 > 2) Restart Primary server > After certain usage by JCS client check the thread count via below command > ps -o pid,comm,user,thcount -p > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCS-235) Thread leakage in JCS 3.1 with primary and secondary server configuration
[ https://issues.apache.org/jira/browse/JCS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757496#comment-17757496 ] Thomas Vandahl commented on JCS-235: Could you please provide a log file showing the behaviour? Please check for the names of the threads running out. As a rule, JCS thread pools have meaningful names that relate to their usage context. Can you provide a thread dump? > 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 2 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 > 2) Restart Primary server > After certain usage by JCS client check the thread count via below command > ps -o pid,comm,user,thcount -p > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCS-235) Thread leakage in JCS 3.1 with primary and secondary server configuration
[ https://issues.apache.org/jira/browse/JCS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1773#comment-1773 ] 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 2 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 > 2) Restart Primary server > After certain usage by JCS client check the thread count via below command > ps -o pid,comm,user,thcount -p > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCS-235) Thread leakage in JCS 3.1 with primary and secondary server configuration
[ https://issues.apache.org/jira/browse/JCS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743775#comment-17743775 ] Gary D. Gregory commented on JCS-235: - Hello [~Amol D] Thank you for the report. The fastest way you'll get feedback IMO is if you can provide a test program that reproduces the issue. Even better if that can be in the form of a failing unit test or integration test. A GitHub PR is a good way to do that since we'll see it compile, run, and fail in the CI. > 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 2 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 > 2) Restart Primary server > After certain usage by JCS client check the thread count via below command > ps -o pid,comm,user,thcount -p > -- This message was sent by Atlassian Jira (v8.20.10#820010)
