Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 30607 invoked from network); 10 Dec 2002 16:33:53 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 Dec 2002 16:33:52 -0000 Received: (qmail 11481 invoked by uid 97); 10 Dec 2002 16:33:00 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 11450 invoked by uid 97); 10 Dec 2002 16:33:00 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 11402 invoked by uid 98); 10 Dec 2002 16:32:59 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <01c101c2a069$b255c190$2405a8c0@wookie> From: =?iso-8859-1?Q?Julian_L=F6ffelhardt?= To: "Tomcat Users List" References: Subject: Re: tomcat,mod_jk & loadbalancing Date: Tue, 10 Dec 2002 17:31:48 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > > - Another idea: We are operating a newspaper website, and > > offering our users > > to log into our system to get additional services. > > Of course most people won't log in because they just want to read > > the news. > > Depending on how you code your application you will configure accordingly. > Are you using encodeURL()? If not, your users are probably bouncing around > with each click even when they are not logged in. In my opinion, you should > really maintain a session for each user whether they login or not. This > way, they won't be connecting to a new Tomcat thread with each click. You > can set the default session to expire in 3 mins or some other short time in > web.xml. Then for those who logins, the web application expires in much > longer period. There were just posts covering this topic. This should > decrease your Tomcat threads. We maintain our sessions using cookies. Using some web stress tools, I also found out that the loadbalancer sometimes has problems working small scale. it's not uncommon that it will route 10-20 sequential requests (without sessionid) to the samr tomcat instance. These requests then remain bound to this tomcat due to the sticky session functionality (which is good). I just hoped the load-balancer would distribute the requests more evenly when most of the requests don't have a sessionid and thus aren't bound to a specific tomcat instance. llap, julian -- To unsubscribe, e-mail: For additional commands, e-mail: