RE: Jakarta Tomcat Connector - Load Balancing
Derek Greer wrote: > Thanks. I don't recall reading this in any of the documentation. Can > you explain what setting this actually does? > > > Derek > > Mladen Turk wrote: > >> Derek Greer wrote: >> >>> I'm trying to use the Tomcat Connector to do load balancing through >>> the IIS filter, however the sessions do not seem to be '"sticky". >>> According to the documentation, the session is set to sticky by >>> default. Even so, after seeing non-sticky behavior I set my lb >>> worker explicitly (i.e. worker.lbworker.sticky_session=1). Why is >>> this not working? >>> >> >> Could be various reasons, but the first one is: >> Did you set the jvmRoute to match the worker names? It is documented both in the server.xml, in the JK doc and in the Tomcat configuration documentation. e.g - http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/engine.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta Tomcat Connector - Load Balancing
Thanks. I don't recall reading this in any of the documentation. Can you explain what setting this actually does? Derek Mladen Turk wrote: Derek Greer wrote: I'm trying to use the Tomcat Connector to do load balancing through the IIS filter, however the sessions do not seem to be '"sticky". According to the documentation, the session is set to sticky by default. Even so, after seeing non-sticky behavior I set my lb worker explicitly (i.e. worker.lbworker.sticky_session=1). Why is this not working? Could be various reasons, but the first one is: Did you set the jvmRoute to match the worker names? Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta Tomcat Connector - Load Balancing
Derek Greer wrote: I'm trying to use the Tomcat Connector to do load balancing through the IIS filter, however the sessions do not seem to be '"sticky". According to the documentation, the session is set to sticky by default. Even so, after seeing non-sticky behavior I set my lb worker explicitly (i.e. worker.lbworker.sticky_session=1). Why is this not working? Could be various reasons, but the first one is: Did you set the jvmRoute to match the worker names? Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
