On Tue, May 17, 2011 at 5:33 PM, Mike Jakubik <mike.jaku...@intertainservices.com> wrote: > Hello, > > I have recently discovered while updating my apache22 installation and > subsequently apr1 from 1.4.2 to 1.4.4 that mod_jk now causes the apache > server to consume 100% cpu and become unresponsive. I have tried recompiling > mod_jk with the new apr but that did not help. Below is my environment > information.
you updated Apache 2.2.x from 2.2.what to 2.2.what? (you updated apr 1.4.2 to 1.4.4) > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 11241 www 1 114 0 61492K 11200K CPU0 0 0:53 78.96% httpd > 11237 www 1 110 0 61492K 11276K RUN 1 0:40 66.26% httpd > 11238 www 1 108 0 61492K 11276K RUN 0 0:50 56.05% httpd get syscall trace of high cpu process? attach with debugger, find callstacks, let it run a while, get callstacks again, see if there are threads that didn't make useful progress? > > Process takes up all resources and is unresponsive, no errors are logged. happens immediately, gradually, immediately after some unknown event occurs? > Removing mod_jk from apache solves the problem. > > FreeBSD staging.local 8.2-STABLE FreeBSD 8.2-STABLE #0: Thu Mar 3 17:32:06 > EST 2011 root@staging.local:/usr/obj/usr/src/sys/STAGING amd64 > Apache/2.2.18 (FreeBSD) mod_jk/1.2.31 PHP/5.3.6 with Suhosin-Patch > mod_ssl/2.2.18 OpenSSL/0.9.8q > > Thanks. > > -- Born in Roswell... married an alien...
