Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 52093 invoked from network); 23 Feb 2007 08:30:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Feb 2007 08:30:19 -0000 Received: (qmail 97664 invoked by uid 500); 23 Feb 2007 08:30:14 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 97636 invoked by uid 500); 23 Feb 2007 08:30:13 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 97625 invoked by uid 99); 23 Feb 2007 08:30:13 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Feb 2007 00:30:13 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [195.227.30.246] (HELO datura.kippdata.de) (195.227.30.246) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Feb 2007 00:30:01 -0800 Received: from [195.227.30.148] (larix [195.227.30.148]) by datura.kippdata.de (8.13.5/8.13.5) with ESMTP id l1N8TeWr025735 for ; Fri, 23 Feb 2007 09:29:40 +0100 (CET) Message-ID: <45DEA5F4.3060908@kippdata.de> Date: Fri, 23 Feb 2007 09:29:40 +0100 From: Rainer Jung User-Agent: Thunderbird 1.5.0.8 (X11/20061110) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: mod_jk sticky session not working?? References: <45DE3883.7090601@epathlearning.com> In-Reply-To: <45DE3883.7090601@epathlearning.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Did you set jmvRoute in server.xml? Scott Danforth wrote: > I'm trying to use jk1.2.20 mod_jk with Apache 1.3 for load balancing two > tomcat services and sticky sessions aren't working. > > My application requires authentication, and displays a login on a new > session. When I kill one of the tomcats, the application works fine > (i.e., the authenticated session is retained and used for each > subsequent request). But if both workers are running, mod_jk ping-pongs > between them (which results in new sessions being created on each request). > > The thing I think is most revealing is that when I run with only one > worker alive (so the application works), mod_jk is still trying to > round-robin the two workers. > > Here's are some excerpts from mod_jk.log that clearly show mod_jk trying > to use both tomcat1 and tomcat2 for the same session. (is "partial > sessionid" a clue??) > > What's going on, and how do I fix this? > > -- Scott. > > > service sticky_session=1 id='B4FE8293E8E81F8071F39EDD1E594BEC' > [Thu Feb 22 19:08:13 2007] [3786:0000] [debug] > get_most_suitable_worker::jk_lb_worker.c (733): searching worker for > partial sessionid B4FE8293E8E81F8071F39EDD1E594BEC > [Thu Feb 22 19:08:13 2007] [3786:0000] [debug] > get_most_suitable_worker::jk_lb_worker.c (785): found best worker > tomcat1 (tomcat1) using method 'Request' > > service sticky_session=1 id='B4FE8293E8E81F8071F39EDD1E594BEC' > [Thu Feb 22 19:08:16 2007] [3786:0000] [debug] > get_most_suitable_worker::jk_lb_worker.c (733): searching worker for > partial sessionid B4FE8293E8E81F8071F39EDD1E594BEC > [Thu Feb 22 19:08:16 2007] [3786:0000] [debug] > get_most_suitable_worker::jk_lb_worker.c (785): found best worker > tomcat2 (tomcat2) using method 'Request' > > service sticky_session=1 id='B4FE8293E8E81F8071F39EDD1E594BEC' > [Thu Feb 22 19:08:16 2007] [3786:0000] [debug] > get_most_suitable_worker::jk_lb_worker.c (733): searching worker for > partial sessionid B4FE8293E8E81F8071F39EDD1E594BEC > [Thu Feb 22 19:08:16 2007] [3786:0000] [debug] > get_most_suitable_worker::jk_lb_worker.c (785): found best worker > tomcat1 (tomcat1) using method 'Request' > > service sticky_session=1 id='B4FE8293E8E81F8071F39EDD1E594BEC' > [Thu Feb 22 19:10:47 2007] [3788:0000] [debug] > get_most_suitable_worker::jk_lb_worker.c (733): searching worker for > partial sessionid B4FE8293E8E81F8071F39EDD1E594BEC > [Thu Feb 22 19:10:47 2007] [3788:0000] [debug] > get_most_suitable_worker::jk_lb_worker.c (785): found best worker > tomcat2 (tomcat2) using method 'Request' > [Thu Feb 22 19:10:47 2007] [3788:0000] [debug] service::jk_lb_worker.c > (860): service worker=tomcat2 route=tomcat2 > > service sticky_session=1 id='B4FE8293E8E81F8071F39EDD1E594BEC' > [Thu Feb 22 19:10:47 2007] [3788:0000] [debug] > get_most_suitable_worker::jk_lb_worker.c (733): searching worker for > partial sessionid B4FE8293E8E81F8071F39EDD1E594BEC > [Thu Feb 22 19:10:47 2007] [3788:0000] [debug] > get_most_suitable_worker::jk_lb_worker.c (785): found best worker > tomcat1 (tomcat1) using method 'Request' > [Thu Feb 22 19:10:47 2007] [3788:0000] [debug] service::jk_lb_worker.c > (860): service worker=tomcat1 route=tomcat1 > > service sticky_session=1 id='B4FE8293E8E81F8071F39EDD1E594BEC' > [Thu Feb 22 19:11:57 2007] [3790:0000] [debug] > get_most_suitable_worker::jk_lb_worker.c (733): searching worker for > partial sessionid B4FE8293E8E81F8071F39EDD1E594BEC > [Thu Feb 22 19:11:57 2007] [3790:0000] [debug] > get_most_suitable_worker::jk_lb_worker.c (785): found best worker > tomcat2 (tomcat2) using method 'Request' > [Thu Feb 22 19:11:57 2007] [3790:0000] [debug] service::jk_lb_worker.c > (860): service worker=tomcat2 route=tomcat2 --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org