Re: Sticky sessions not working at get_most_suitable_worker
Thanks Chirs, you are right. I've changed jvmRoute to worker's name, not worker's hostname, and it's working fine. Thanks, again. Carlos De: Christopher Schultz Enviado: sábado, 30 de junio de 2018 22:04:21 Para: Tomcat Users List; Carlos García Asunto: Re: Sticky sessions not working at get_most_suitable_worker -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Carlos, On 6/30/18 4:12 AM, Carlos García wrote: > I' m working on a LB configuration with Apache/2.4.18 (Ubuntu) > mod_jk/1.2.41 and not getting wanted results. > > > My workers config is: > > > worker.list=balanceFFG, jk-status # tomcat-pro-03 por COLT > worker.FFG1.host=tomcat-pro-03 worker.FFG1.port=8009 > worker.FFG1.type=ajp13 worker.FFG1.sticky_session=true > > # tomcat-pro-06 por COLT worker.FFG2.host=tomcat-pro-06 > worker.FFG2.port=8010 worker.FFG2.type=ajp13 > worker.FFG2.sticky_session=true > > worker.balanceFFG.type=lb worker.balanceFFG.balance_workers=FFG1, > FFG2 worker.jk-status.type=status Thank you for posting your configuration. You need to set the sticky_session attribute on the *balancer* and not on the individual workers, although the default value for "sticky_session" is in fact "true", so this should not matter. If you look at your mod_jk log file, does it say that sticky_session isn't valid for a normal AJP13 worker? (It really should if it doesn't.) > VirtualHost config is: > > Header edit Set-Cookie "^(.*; Path=)/ffgonzalezarch_pro/?(.*)" > $1/$2 What is *this* for? > RewriteEngine on RewriteRule ^(.*)$ /ffgonzalezarch_pro$1 [PT,L] > RewriteRule ^(.*)$ /ffgonzalezarch_pro/$1 [CO] > > JkMount /ffgonzalezarch_pro/* balanceFFG > > > jvmRoute set in Engine section in Tomcat server.xml What did you set it/them to? > And finally, this is the result in mod_jk debug log: > > > [Sat Jun 30 06:52:29.565 2018] [6628:139806621300480] [debug] > service::jk_lb_worker.c (1270): service sticky_session=1 > id='7E9778933D54A11F3D91B9AF81653C53.tomcat-pro-06' [Sat Jun 30 > 06:52:29.565 2018] [6628:139806621300480] [debug] > get_most_suitable_worker::jk_lb_worker.c (1078): searching worker > for partial sessionid > 7E9778933D54A11F3D91B9AF81653C53.tomcat-pro-06 [Sat Jun 30 > 06:52:29.565 2018] [6628:139806621300480] [debug] > get_most_suitable_worker::jk_lb_worker.c (1086): searching worker > for session route tomcat-pro-06 [Sat Jun 30 06:52:29.565 2018] > [6628:139806621300480] [debug] > get_most_suitable_worker::jk_lb_worker.c (1136): found best worker > FFG1 (FFG1) using method 'Request' > > So, a session from FFG2(omcat-pro-06) ends in FFG1(tomcat-pro-03). > Why!! Sessionid is telling you FFG2(omcat-pro-06)!! It looks like you have set jvmRoute to "tomcat-pro-06" and "tomcat-pro-03" but the worker's route names default to the worker names (FFG1, FFG2). So, you either need this in workers.properties: worker.FFG1.route=tomcat-pro-03 and worker.FFG2.route=tomcat-pro-06 or you need this in conf/server.xml and Hope that helps, - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAls34kQACgkQHPApP6U8 pFhJRw/+JWWNWq4Vp+dMGo6YmeTcYJfRdaUiIjw3vCZxl8fDh9UBGufvQO44I1QO RuH0X155zb0csN3THWyA15pWicFLt3XNdjZIzy9X3J2K7E366wD7GJtmP/bm+ua8 LaEkwx/Iu2jADWn/FRl6k58m+xXk9LUWWpLw0YJGE2Go/PXFM9ZAsBLHi9sdPQlW xAotxkqopP4lx5CGtUARRP66cygsQQltUKbLyUhwnP4gKJgN27hw+mRuSf86H+Kh 2aXJSdDHkulgdFOBauZzVzUgctAcDi0vkxzjLmHApgCTUzQ5KHu8ChqZstOR4jaO h3g0QJzuvcGmtlZfCJte6U2YhoCgDVgIaN106BnJ1UlFICqmvi8leERTG5Da1Blx HbTi1sVxytYhm/troPNgTAnnYGRDQqtPxuFq33jZHHvHGZvSGbZYxPtb8bqTL+x6 x1vB5jhqC5mmA5on/UG+B6Xzb12BbaluJ8TLkd/HW4MiiLnX04/nkCsw2WaZAqee TJLg7cIBMeNM3H7EPlghuN9FnGeTnZgD5xRmJZOCGXvtp3DPT0JbE5I56nj0oowQ SD9qzoMDE+krdwz5B+0ZtXql/GixEsxW3S/szUQO6e2Z4YdrliHlaWnWTh9d6ezg rDxkPWrYCBOOe3XO6nSqKsgehCdZgv5yqdG3AZeRIE9eSZ+aXRs= =IF98 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Sticky sessions not working at get_most_suitable_worker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Carlos, On 6/30/18 4:12 AM, Carlos García wrote: > I' m working on a LB configuration with Apache/2.4.18 (Ubuntu) > mod_jk/1.2.41 and not getting wanted results. > > > My workers config is: > > > worker.list=balanceFFG, jk-status # tomcat-pro-03 por COLT > worker.FFG1.host=tomcat-pro-03 worker.FFG1.port=8009 > worker.FFG1.type=ajp13 worker.FFG1.sticky_session=true > > # tomcat-pro-06 por COLT worker.FFG2.host=tomcat-pro-06 > worker.FFG2.port=8010 worker.FFG2.type=ajp13 > worker.FFG2.sticky_session=true > > worker.balanceFFG.type=lb worker.balanceFFG.balance_workers=FFG1, > FFG2 worker.jk-status.type=status Thank you for posting your configuration. You need to set the sticky_session attribute on the *balancer* and not on the individual workers, although the default value for "sticky_session" is in fact "true", so this should not matter. If you look at your mod_jk log file, does it say that sticky_session isn't valid for a normal AJP13 worker? (It really should if it doesn't.) > VirtualHost config is: > > Header edit Set-Cookie "^(.*; Path=)/ffgonzalezarch_pro/?(.*)" > $1/$2 What is *this* for? > RewriteEngine on RewriteRule ^(.*)$ /ffgonzalezarch_pro$1 [PT,L] > RewriteRule ^(.*)$ /ffgonzalezarch_pro/$1 [CO] > > JkMount /ffgonzalezarch_pro/* balanceFFG > > > jvmRoute set in Engine section in Tomcat server.xml What did you set it/them to? > And finally, this is the result in mod_jk debug log: > > > [Sat Jun 30 06:52:29.565 2018] [6628:139806621300480] [debug] > service::jk_lb_worker.c (1270): service sticky_session=1 > id='7E9778933D54A11F3D91B9AF81653C53.tomcat-pro-06' [Sat Jun 30 > 06:52:29.565 2018] [6628:139806621300480] [debug] > get_most_suitable_worker::jk_lb_worker.c (1078): searching worker > for partial sessionid > 7E9778933D54A11F3D91B9AF81653C53.tomcat-pro-06 [Sat Jun 30 > 06:52:29.565 2018] [6628:139806621300480] [debug] > get_most_suitable_worker::jk_lb_worker.c (1086): searching worker > for session route tomcat-pro-06 [Sat Jun 30 06:52:29.565 2018] > [6628:139806621300480] [debug] > get_most_suitable_worker::jk_lb_worker.c (1136): found best worker > FFG1 (FFG1) using method 'Request' > > So, a session from FFG2(omcat-pro-06) ends in FFG1(tomcat-pro-03). > Why!! Sessionid is telling you FFG2(omcat-pro-06)!! It looks like you have set jvmRoute to "tomcat-pro-06" and "tomcat-pro-03" but the worker's route names default to the worker names (FFG1, FFG2). So, you either need this in workers.properties: worker.FFG1.route=tomcat-pro-03 and worker.FFG2.route=tomcat-pro-06 or you need this in conf/server.xml and Hope that helps, - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAls34kQACgkQHPApP6U8 pFhJRw/+JWWNWq4Vp+dMGo6YmeTcYJfRdaUiIjw3vCZxl8fDh9UBGufvQO44I1QO RuH0X155zb0csN3THWyA15pWicFLt3XNdjZIzy9X3J2K7E366wD7GJtmP/bm+ua8 LaEkwx/Iu2jADWn/FRl6k58m+xXk9LUWWpLw0YJGE2Go/PXFM9ZAsBLHi9sdPQlW xAotxkqopP4lx5CGtUARRP66cygsQQltUKbLyUhwnP4gKJgN27hw+mRuSf86H+Kh 2aXJSdDHkulgdFOBauZzVzUgctAcDi0vkxzjLmHApgCTUzQ5KHu8ChqZstOR4jaO h3g0QJzuvcGmtlZfCJte6U2YhoCgDVgIaN106BnJ1UlFICqmvi8leERTG5Da1Blx HbTi1sVxytYhm/troPNgTAnnYGRDQqtPxuFq33jZHHvHGZvSGbZYxPtb8bqTL+x6 x1vB5jhqC5mmA5on/UG+B6Xzb12BbaluJ8TLkd/HW4MiiLnX04/nkCsw2WaZAqee TJLg7cIBMeNM3H7EPlghuN9FnGeTnZgD5xRmJZOCGXvtp3DPT0JbE5I56nj0oowQ SD9qzoMDE+krdwz5B+0ZtXql/GixEsxW3S/szUQO6e2Z4YdrliHlaWnWTh9d6ezg rDxkPWrYCBOOe3XO6nSqKsgehCdZgv5yqdG3AZeRIE9eSZ+aXRs= =IF98 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Sticky sessions not working at get_most_suitable_worker
Hello. I' m working on a LB configuration with Apache/2.4.18 (Ubuntu) mod_jk/1.2.41 and not getting wanted results. My workers config is: worker.list=balanceFFG, jk-status # tomcat-pro-03 por COLT worker.FFG1.host=tomcat-pro-03 worker.FFG1.port=8009 worker.FFG1.type=ajp13 worker.FFG1.sticky_session=true # tomcat-pro-06 por COLT worker.FFG2.host=tomcat-pro-06 worker.FFG2.port=8010 worker.FFG2.type=ajp13 worker.FFG2.sticky_session=true worker.balanceFFG.type=lb worker.balanceFFG.balance_workers=FFG1, FFG2 worker.jk-status.type=status VirtualHost config is: Header edit Set-Cookie "^(.*; Path=)/ffgonzalezarch_pro/?(.*)" $1/$2 RewriteEngine on RewriteRule ^(.*)$ /ffgonzalezarch_pro$1 [PT,L] RewriteRule ^(.*)$ /ffgonzalezarch_pro/$1 [CO] JkMount /ffgonzalezarch_pro/* balanceFFG jvmRoute set in Engine section in Tomcat server.xml And finally, this is the result in mod_jk debug log: [Sat Jun 30 06:52:29.565 2018] [6628:139806621300480] [debug] service::jk_lb_worker.c (1270): service sticky_session=1 id='7E9778933D54A11F3D91B9AF81653C53.tomcat-pro-06' [Sat Jun 30 06:52:29.565 2018] [6628:139806621300480] [debug] get_most_suitable_worker::jk_lb_worker.c (1078): searching worker for partial sessionid 7E9778933D54A11F3D91B9AF81653C53.tomcat-pro-06 [Sat Jun 30 06:52:29.565 2018] [6628:139806621300480] [debug] get_most_suitable_worker::jk_lb_worker.c (1086): searching worker for session route tomcat-pro-06 [Sat Jun 30 06:52:29.565 2018] [6628:139806621300480] [debug] get_most_suitable_worker::jk_lb_worker.c (1136): found best worker FFG1 (FFG1) using method 'Request' So, a session from FFG2(omcat-pro-06) ends in FFG1(tomcat-pro-03). Why!! Sessionid is telling you FFG2(omcat-pro-06)!! Thanks for help!
Re: Sticky sessions not working
Thank you all for your responses. We found that sticky was set up properly. The problem was with the application and how it handles clustering. Thanks again... On Fri, Sep 21, 2012 at 11:51 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nicolas, On 9/21/12 12:58 AM, Nicolas Sarazin wrote: Add : worker.node1.route=node1 And : worker.node2.route=node2 To use sticky session. These directives attach name route at the end of JSESSIONID. That shouldn't be necessary, as the worker's name is the default 'route', and the OP has them set up properly. I think this might be interfering with your setup: Le vendredi 21 septembre 2012, Lou Henry a écrit : worker.node1.domain=jvm1 worker.node2.domain=jvm2 Lou, do you need the domain for anything? The docs say that when sticky_session=true (which is the default, and you haven't overridden it), then the domain becomes the 'route'. Since you aren't explicitly specifying the route, then you are probably getting implicitly: worker.node1.route=jvm1 worker.node2.route=jvm2 when what you want is 'node1' and 'node2'. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBdNa0ACgkQ9CaO5/Lv0PBMFwCfQZdAuuEH+FNiwli6n7+dk22B 6/4AoIk1i4MnH3qglv8pah5xY47Jzos+ =EA2N -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Sticky sessions not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nicolas, On 9/21/12 12:58 AM, Nicolas Sarazin wrote: Add : worker.node1.route=node1 And : worker.node2.route=node2 To use sticky session. These directives attach name route at the end of JSESSIONID. That shouldn't be necessary, as the worker's name is the default 'route', and the OP has them set up properly. I think this might be interfering with your setup: Le vendredi 21 septembre 2012, Lou Henry a écrit : worker.node1.domain=jvm1 worker.node2.domain=jvm2 Lou, do you need the domain for anything? The docs say that when sticky_session=true (which is the default, and you haven't overridden it), then the domain becomes the 'route'. Since you aren't explicitly specifying the route, then you are probably getting implicitly: worker.node1.route=jvm1 worker.node2.route=jvm2 when what you want is 'node1' and 'node2'. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBdNa0ACgkQ9CaO5/Lv0PBMFwCfQZdAuuEH+FNiwli6n7+dk22B 6/4AoIk1i4MnH3qglv8pah5xY47Jzos+ =EA2N -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Sticky sessions not working
I'm running Apache Tomcat 7.0.14 and Apache 2.2.21 (mod_jk1.2.37). I am trying to load balance two Tomcat Servers and sticky sessions are not working. I am running a two-factor authentication package and it looks like my LB configuration is directing the user to one Tomcat for part of the transaction and to the other Tomcat server for the other part. When I bring down one of the Tomcat servers, everything works fine; but with both Tomcat servers up, I get 500 errors. So, I am trying to stick the webserver session to one particular Tomcat server. Listed below is my configuration. Also, I tried without the domain directive also. I am not quite sure if that's a random name or should it be something specific. Can someone please assist? Thank you... *workers.properties* worker.list=loadbalancer,status # Define Node1 # modify the host as your host IP or DNS name. worker.node1.domain=jvm1 worker.node1.port= worker.node1.host=t*20.x. worker.node1.type=ajp13 worker.node1.lbfactor=1 worker.node1.ping_mode=A # Define Node2 # modify the host as your host IP or DNS name. worker.node2.domain=jvm2 worker.node2.port= worker.node2.host=t*21.x. worker.node2.type=ajp13 worker.node2.lbfactor=1 worker.node2.ping_mode=A # Load-balancing behaviour worker.loadbalancer.type=lb worker.loadbalancer.balance_workers=node1,node2 worker.loadbalancer.sticky_session=True # Status worker for managing load balancer worker.status.type=status # Added per Anakam direction 113010 worker.node1.socket_keepalive=True worker.node1.socket_timeout=300 # Added per Anakam direction 113010 worker.node2.socket_keepalive=True worker.node2.socket_keepalive=300 *server.xml on Tomcat Node 1* Engine name=Catalina defaultHost=localhost jvmRoute=node1 *server.xml on Tomcat Node 2* Engine name=Catalina defaultHost=localhost jvmRoute=node2
Re: Sticky sessions not working
Hello, Add : worker.node1.route=node1 And : worker.node2.route=node2 To use sticky session. These directives attach name route at the end of JSESSIONID. Best regards, Nicolas SARAZIN Le vendredi 21 septembre 2012, Lou Henry a écrit : I'm running Apache Tomcat 7.0.14 and Apache 2.2.21 (mod_jk1.2.37). I am trying to load balance two Tomcat Servers and sticky sessions are not working. I am running a two-factor authentication package and it looks like my LB configuration is directing the user to one Tomcat for part of the transaction and to the other Tomcat server for the other part. When I bring down one of the Tomcat servers, everything works fine; but with both Tomcat servers up, I get 500 errors. So, I am trying to stick the webserver session to one particular Tomcat server. Listed below is my configuration. Also, I tried without the domain directive also. I am not quite sure if that's a random name or should it be something specific. Can someone please assist? Thank you... *workers.properties* worker.list=loadbalancer,status # Define Node1 # modify the host as your host IP or DNS name. worker.node1.domain=jvm1 worker.node1.port= worker.node1.host=t*20.x. worker.node1.type=ajp13 worker.node1.lbfactor=1 worker.node1.ping_mode=A # Define Node2 # modify the host as your host IP or DNS name. worker.node2.domain=jvm2 worker.node2.port= worker.node2.host=t*21.x. worker.node2.type=ajp13 worker.node2.lbfactor=1 worker.node2.ping_mode=A # Load-balancing behaviour worker.loadbalancer.type=lb worker.loadbalancer.balance_workers=node1,node2 worker.loadbalancer.sticky_session=True # Status worker for managing load balancer worker.status.type=status # Added per Anakam direction 113010 worker.node1.socket_keepalive=True worker.node1.socket_timeout=300 # Added per Anakam direction 113010 worker.node2.socket_keepalive=True worker.node2.socket_keepalive=300 *server.xml on Tomcat Node 1* Engine name=Catalina defaultHost=localhost jvmRoute=node1 *server.xml on Tomcat Node 2* Engine name=Catalina defaultHost=localhost jvmRoute=node2
Re: apache 2.0.54 + mod_jk 1.2.14 - sticky sessions not working
Doehler, Thomas wrote: Hi list, I'm using apache 2.0.54 + mod_jk 1.2.14 on a debian 3.1 server. I have 2 tomcat workers running on different machines. Although I configured the load balancing worker with sticky_session=1, all requests get spread over the tomcat workers in round robin. My question is, how does mod_jk recognize the session id? Is there a way to configure which request parameter is the session id? Did you set the jvmRoute=your worker name in the Tomcat's server.xml? This is probably the cause of your problem. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: apache 2.0.54 + mod_jk 1.2.14 - sticky sessions not working
Hi, thanks for the quick response, jvmRoute is configured on both instances. We do not use the standard tomcat url rewriting (which is http://...;jsessionid=...?x=y), we use simply a standard http paramter and do our own url rewriting. Regards, Tom Did you set the jvmRoute=your worker name in the Tomcat's server.xml? This is probably the cause of your problem. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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]
