DO NOT REPLY [Bug 20689] New: - mod_jk2, the /jkstatus page, and apache::worker

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20689>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20689

mod_jk2, the /jkstatus page, and apache::worker

           Summary: mod_jk2, the /jkstatus page, and apache::worker
           Product: Tomcat 4
           Version: 4.1.24
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Connector:Coyote JK 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: crozierm@conducivetech.com


I'm using mod_jk2 with apache in "worker" mode, meaning that there are several 
different httpd processes that stay alive (instead of forking) and are delegated 
requests.  I noticed that when setting a jk2 channel to graceful by updating 
workers2.properties and hitting the /jkstatus page, only one of the "worker" httpd's 
would pick up the change.  Other httpd+mod_jk2 processes would continue to forward 
new sessions to the "graceful" channel.  The solution was to access the /jkstatus page 
repeatedly until every httpd process had served /jkstatus and picked up the changed 
attributes. 
 
If possible, it would be more convenient if accessing /jkstatus a single time would cause 
all the httpd workers to check workers2.properties for updates. 
 
Thanks!

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org