|Summary:||Changes made to ping_timeout via Status Worker not synced across Apache Children|
|Product:||Tomcat Connectors||Reporter:||Joe Kislo <joekislos>|
|Component:||mod_jk||Assignee:||Tomcat Developers Mailing List <dev>|
Description Joe Kislo 2009-05-19 15:06:22 UTC
Changes made to ping_timeout via Status Worker not synced across Apache Children Configure Apache to use the mpm_worker, and start 2 children by default Access the Status Worker, and change the "Ping Timeout:" on a worker. EG: Change it from 10000 to 15000 Query the status worker using a non-keepalived webbrowser (such as curl) and see what the setting is set to. It will alternate between the OLD setting and the NEW setting. EG: curl "http://SERVERNAMEHERE/ajpstatus?cmd=show&w=WORKERNAMEHERE&mime=txt" -> First request returned 10000 (the 'old' value) curl "http://SERVERNAMEHERE/ajpstatus?cmd=show&w=WORKERNAMEHERE&mime=txt" -> Second request returned 15000 (the 'new' value) If you change another value, such as 'Retries', your change will by synced across the children
Comment 1 Joe Kislo 2009-05-19 15:07:26 UTC
This bug seems simple now, but it caused alot of head banging for me. I didn't realize that it was just this one parameter; I was assuming it was ALL parameters that weren't being synced, and I kept looking for problems with my Shm file. It wasn't until I was writing this bug report I discovered it appears (although I didn't throughly test) that it's just this one parameter
Comment 2 Rainer Jung 2009-05-20 04:08:02 UTC
I will investigate.
Comment 3 Mladen Turk 2009-12-21 03:47:10 UTC
Fixed in the SVN by adding ping_timeout to the shared memory
Comment 4 Rainer Jung 2010-02-23 02:56:24 UTC
Will be part of 1.2.29.