Adam Gordon schrieb: > The 'wget' command allows the user to play with Cookies so our next step > is to see if we can specify a fake JSESSIONID in cookie form to see if > we can dictate to which server Apache will send us. As previously > mentioned, we cannot simply put this on the URL as a parameter because > we are using sticky sessions.
If the sole purpose of the cookie is to tell mod_jk which Tomcat instance it should use, then using an appropriate cookie is equivalent to using a jsessionid path parameter like in http://mybalancer:myport/myapp/mymonitorservlet;jsessionid=.nodeX and nodeX is the jvmRoute of the node you want to talk to. A mod_jk load balancer worker will look in the value of the jsessionid path parameter and the value of the JSESSIONID cookie whether there is a dot "." included and take everything behind it as the name of the member worker to which it should send the request. If that member is broken and you don't have sticky_session_force (which you usually don't have), then it will instead send the request to some other member. So make sure, the URL you call returns the jvmRoute of the called node and compare it to "nodeX" to make sure you actually talked to nodeX. If you only want to know, whether mod_jk has detected a node to be in error, have a look at the JK status worker and monitor its result instead. Recommendation for a full-blown solution: Check general worker state in the mod_jk status worker and more detailed application status via a monitor servlet inside your app. Regards, Rainer --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
