On 17.05.2011 23:33, Mike Jakubik 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. > > 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 > > Process takes up all resources and is unresponsive, no errors are > logged. 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 for the report. Would you mind opening an issues in Bugzilla? You can choose the Tomcat project and Tomcat Connectors as a component. If it turns out as an APR bug, we can move the issue there later. It would be very helpful, if you could provide thread stacks using pstack or gdb. Please provide a couple of such threads stack outputs. Furthermore, if your MPM is worker, not prefork, it would be helpful if you could check using ps, which of the threads in the process actually consume the CPU. I'm not sure about FreeBSD ps flags, but -H -p ... could be right. This helps us select out the right thread stack. Regards, Rainer
