You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/05/14 03:39:40 UTC
DO NOT REPLY [Bug 19908] New: -
cannot re-enable lb worker after disable, lb_value stays at zero
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=19908>.
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=19908
cannot re-enable lb worker after disable, lb_value stays at zero
Summary: cannot re-enable lb worker after disable, lb_value stays
at zero
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 am using mod_jk2 to load balance sticky sessions between several
out-of-process tomcat instances. When I disable a worker gracefully, then
attempt to re-enable it via workers2.properties, the worker is never used since
the lb_value is set to zero. The only way to get lb_value back to normal for
that worker is to restart apache, which disrupts the sticky session load balancing.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org