[
https://issues.apache.org/jira/browse/CASSANDRA-10861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056883#comment-15056883
]
Carlos Scheidecker commented on CASSANDRA-10861:
------------------------------------------------
Michael,
I had it increased on Tomcat updstart script to 50000 let's see how it goes now.
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 256854 256854 processes
Max open files 50000 50000 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 256854 256854 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
> Memory leak with Cassadra java driver 3.0.0-beta1 and Cassandra 3.0.1
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-10861
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10861
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Environment: Ubuntu 14.04.3 LTS 64 bits, Java build 1.8.0_66-b17,
> tomcat 8.0.23
> Reporter: Carlos Scheidecker
> Fix For: 3.0.1
>
> Attachments: error_log_tomcat.txt
>
>
> Same dev environment with same application on Tomcat 8.0.23. However the dev
> nodes have been upgraded to 3.0.0 and later to 3.0.1. The Cassandra driver is
> version 3.0.0-beta1.
> It seems that connections crash, do not get cleared and it leads to a memory
> leak stack overflow condition.
> Attached is an error log file from tomcat.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
