Re: mod_jk logging issue

> Hi Rainer/Simon - I've just had another look at this. With no > application running (IOW, all Java processes killed), I see this > behaviour: Sorry, I was confused because I thought we're talking about files from Tomcat and not from Apache/mod_jk. Regards, Simon > >  # systemctl start

Re: mod_jk logging issue

Hi Rainer/Simon - I've just had another look at this. With no application running (IOW, all Java processes killed), I see this behaviour:  # systemctl start apache2 This create a number of apache2 processes (generally 7). 2 new mod_jk files are created, corresponding to the apache2 process

Re: mod_jk logging issue

Hi, > Hi - I'm running mod_jk with an Apache front-end, and I'm having an > issue with the JkShmFile files. > > Every time Apache restarts mod_jk creates two new files > (jk-runtime-status.PID and jk-runtime-status.PID.lock). These are never > cleaned up; the log directory simply fills up with

Re: mod_jk logging issue

Hi there, Am 19.12.23 um 18:05 schrieb EML: Hi - I'm running mod_jk with an Apache front-end, and I'm having an issue with the JkShmFile files. Every time Apache restarts mod_jk creates two new files (jk-runtime-status.PID and jk-runtime-status.PID.lock). These are never cleaned up; the log

mod_jk logging issue

Hi - I'm running mod_jk with an Apache front-end, and I'm having an issue with the JkShmFile files. Every time Apache restarts mod_jk creates two new files (jk-runtime-status.PID and jk-runtime-status.PID.lock). These are never cleaned up; the log directory simply fills up with these files.