> -----Original Message----- > From: Rainer Jung [mailto:rainer.j...@kippdata.de] > Sent: Wednesday, February 25, 2015 3:41 AM > To: Tomcat Users List > Subject: Re: mod_jk causing stuck Apache processes > > So here is a patch for version 1.2.40: > > http://people.apache.org/~rjung/patches/jk_shm_lock.patch > > The patch is non-trivial though. It reduces the load on the lock by > > - moving some trivial stuff done for each lb member in a separate > lock/unlock block (per member) to the lb itself, using its own lock/unlock > block. That doesn't reduce the total time locks are held, but the number > of lock/unlock ops. > > - using a different mechanism to check, whether the global maintenance > should actually run (based on atomics and a global decision instead of a > per lb decision). That should be more efficient and again reduces > lock/unlock ops, because the check can now be done without the lock and > only if the global maintenance has to run is the locking needed. > Introduces atomics though. > > You would have to rebuild mod_jk completely, not only the changed files, > because of header file changes. So do a "make clean" before the "make". > > There are no configuration changes needed. You could run one of your > Apaches with the patched mod_jk and compare behavior. Give it a try on a > test system first please. I haven't done a thorough testing myself yet. > > I plan to include this in the next version (1.2.41), which is not far > away. Testing and checking whether it helps would be really helpful. > > Regards and thanks > > Rainer
I've put the patched mod_jk on 4 of our 16 servers and it's working good so far. I will continue to monitor and let you know. Respectfully, Jesse --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
