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 2005/04/16 10:26:01 UTC
DO NOT REPLY [Bug 34481] New: -
mod_jk 1.2.10 status worker quick refresh problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34481>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34481
Summary: mod_jk 1.2.10 status worker quick refresh problem
Product: Tomcat 5
Version: Unknown
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Native:JK
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: puckman@taglab.com
I'm testing the load balancing worker. My setup is: 2 hosts running Debian Linux
(Sarge), Debian stock install of apache2. Apache2 using prefork workers.
I've got two such Linux boxes, my workers.properties is:
-------------------------------------------
worker.list=lb,status
worker.status.type=status
worker.node1.port=10900
worker.node1.host=rhubarb
worker.node1.type=ajp13
worker.node1.disabled=true
worker.node2.port=10900
worker.node2.host=blueberry
worker.node2.type=ajp13
worker.lb.balance_workers=node1,node2
worker.lb.type=lb
worker.lb.sticky_session=true
-------------------------------------------
My <VirtualHost> directive is:
-------------------------------------------
<VirtualHost *>
ServerName martin.rhubarb.salad.taglab.com
ServerAlias martin.rhubarb
JKMount /* lb
JKMount /status status
</VirtualHost>
------------------------------------------
I start doing some requests to "http://martin.rhubarb/test.jsp" and it works
fine, the test jsp prints out the session id and some trace output in the log.
All requests keep going to the same host. All is fine.
-------------------------------------------
I look at the http://martin.rhubarb/status page and I can see:
node1 ajp13 rhubarb:10900 192.168.100.85:10900 Disabled 1 1 0 0 0 0 0
node2 ajp13 blueberry:10900 192.168.100.86:10900 OK 1 1 15 0 7.1K 2.0K 0
-------------------------------------------
If I refresh the /status page too quickly (click reload before the previous page
has loaded), the status can often get reset:
-------------------------------------------
node1 ajp13 rhubarb:10900 192.168.100.85:10900 Disabled 1 1 0 0 0 0 0
node2 ajp13 blueberry:10900 192.168.100.86:10900 OK 1 1 0 0 0 0 0
-------------------------------------------
Not only that, but sometimes it starts showing the "Disabled" and "OK" states
completely erratic reporting "Disabled" or "OK" on the wrong one. This looks
like a thread issue in the status worker since as far as I can tell the actual
lb worker continues to work fine.
Details of how I installed mod_jk.so:
I downloaded the source for the connectors 1.2.10. Compiled and installed it like.
$ cd jk/native
$ ./configure --with-apxs=/usr/bin/apxs2
$ make
$ cp apache-2.0/mod_jk.so /usr/lib/apache2/modules/
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org