AW: AW: apache 2.0.54 + mod_jk 1.2.14 - sticky sessions not working
Hi, here the requested files: workers properties: --- # # wokers.properties - configuration for mod_jk # # configure path separator ps=/ # list of workers by name worker.list=loadbalancer worker.loadbalancer.type=lb worker.loadbalancer.balanced_workers=debi1, debi2 worker.loadbalancer.sticky_sessions=1 # # first application server: debi1 # worker.debi1.port=8009 worker.debi1.host=debi1.mydomain.org worker.debi1.type=ajp13 # # second worker # worker.debi2.port=8009 worker.debi2.host=debi2.mydomain.org worker.debi2.type=ajp13 And the server.xml (this is a snippet from jboss-service.xml, since i use tomcat embedded into jboss): Server Service name = JBoss-Tomcat Engine name=MainEngine defaultHost=localhost jvmRoute=debi2 Logger className = org.jboss.web.catalina.Log4jLogger verbosityLevel = debug category = org.jboss.web.localhost.Engine/ Host name=localhost !-- Access logger -- Valve className = org.apache.catalina.valves.AccessLogValve prefix = localhost_access suffix = .log pattern = common directory = /var/log/jboss / !-- Default context parameters -- DefaultContext cookies = true crossContext = true override = true / /Host /Engine !-- A HTTP/1.1 Connector on port 8080 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8080 minProcessors=3 maxProcessors=10 enableLookups=true acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false / !-- the ajp connector -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=10 enableLookups=true acceptCount=10 debug=1 connectionTimeout=2 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ /Service /Server Thanks in advance, bye Tom Right, but it would be good that you send your server.xml and workers.properties, just in case. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: AW: apache 2.0.54 + mod_jk 1.2.14 - sticky sessions not working
Doehler, Thomas wrote: Hi, !-- the ajp connector -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=10 enableLookups=true acceptCount=10 debug=1 connectionTimeout=2 protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/ IMO having 10 connections limit is way too low for any serious usage. I would suggest that you rise maxProcessor to at least 100. Also do you observe any error messages in mod_jk.log? Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: AW: apache 2.0.54 + mod_jk 1.2.14 - sticky sessions not working
The system i'm currently testing with is only a little test system, it is not inteded to go productive in that configuration ;-) But thanks for the tip you anyway. The jk.log has no error messages, and here is the log grepped for found best worker: [Tue Oct 25 15:52:23 2005] [28304:49172] [debug] get_most_suitable_worker::jk_lb_worker.c (539): found best worker (debi1) using by request method [Tue Oct 25 15:52:23 2005] [28315:16410] [debug] get_most_suitable_worker::jk_lb_worker.c (539): found best worker (debi2) using by request method [Tue Oct 25 15:52:23 2005] [28311:49176] [debug] get_most_suitable_worker::jk_lb_worker.c (539): found best worker (debi1) using by request method [Tue Oct 25 15:52:23 2005] [28307:0021] [debug] get_most_suitable_worker::jk_lb_worker.c (539): found best worker (debi2) using by request method [Tue Oct 25 15:52:23 2005] [28269:32771] [debug] get_most_suitable_worker::jk_lb_worker.c (539): found best worker (debi1) using by request method [Tue Oct 25 15:52:25 2005] [28302:32787] [debug] get_most_suitable_worker::jk_lb_worker.c (539): found best worker (debi2) using by request method [Tue Oct 25 15:52:28 2005] [28312:0025] [debug] get_most_suitable_worker::jk_lb_worker.c (539): found best worker (debi1) using by request method [Tue Oct 25 15:52:32 2005] [28308:16406] [debug] get_most_suitable_worker::jk_lb_worker.c (539): found best worker (debi2) using by request method [Tue Oct 25 15:52:38 2005] [28317:32795] [debug] get_most_suitable_worker::jk_lb_worker.c (539): found best worker (debi1) using by request method I don't know how the mod_jk wants to figure out which parameters it should use to identify requests belonging to one session. Do you have an idea? I'm not a c expert, but I think I will taje a look at the sources, maybe I find something about that. bye Tom IMO having 10 connections limit is way too low for any serious usage. I would suggest that you rise maxProcessor to at least 100. Also do you observe any error messages in mod_jk.log? Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
