https://issues.apache.org/bugzilla/show_bug.cgi?id=56733
Bug ID: 56733
Summary: Memory leak when JkOption +FlushPackets is enabled
Product: Tomcat Connectors
Version: 1.2.40
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: mod_jk
Assignee: dev@tomcat.apache.org
Reporter: do...@moonteeth.com
This appears to be the same as:
https://issues.apache.org/bugzilla/show_bug.cgi?id=42366
I'm opening a new one though since that one is so old. If this is incorrect
please let me know.
The issue is reproducible with any fairly recent mod_jk but I'm testing 1.2.40
right now. httpd -V output:
Server version: Apache/2.2.27 (Win32)
Server built: May 15 2014 17:04:25
Server's Module Magic Number: 20051115:33
Server loaded: APR 1.5.0, APR-Util 1.5.3
Compiled using: APR 1.5.0, APR-Util 1.5.3
Architecture: 32-bit
Server MPM: WinNT
threaded: yes (fixed thread count)
forked: no
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/winnt"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses disabled)
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=128
-D HTTPD_ROOT="/apache"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_ERRORLOG="logs/error.log"
-D AP_TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf"
What i did was simply created a 600mb file using dd if=/dev/urandom
plopped it into tomcat's webapps/example directory
configured
JkMount /examples/* ajpWorker
and used wget to download it. I ran wget in a loop and eventually stopped it
when private bytes hit around 300MB.
I can't reliably reproduce it with all workers.properties options. For example
this:
worker.tomcat1.type=ajp13
worker.tomcat1.host=localhost
worker.tomcat1.port=8010
worker.tomcat1.max_packet_size=8192
worker.tomcat1.connection_pool_size=120
worker.tomcat1.connection_pool_minsize=8
worker.tomcat1.connection_pool_timeout=900
triggers the problem
but
this alone:
worker.tomcat1.type=ajp13
worker.tomcat1.host=localhost
worker.tomcat1.port=8010
does not.
I'm in the process of testing to see if the connection_pool configuration may
be what's doing it.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
