Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8D8D5C4A7 for ; Tue, 11 Jun 2013 13:54:35 +0000 (UTC) Received: (qmail 73742 invoked by uid 500); 11 Jun 2013 13:54:32 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 73581 invoked by uid 500); 11 Jun 2013 13:54:31 -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 73569 invoked by uid 99); 11 Jun 2013 13:54:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jun 2013 13:54:31 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jjakub83@gmail.com designates 209.85.212.43 as permitted sender) Received: from [209.85.212.43] (HELO mail-vb0-f43.google.com) (209.85.212.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jun 2013 13:54:26 +0000 Received: by mail-vb0-f43.google.com with SMTP id e12so2781519vbg.30 for ; Tue, 11 Jun 2013 06:54:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=b6tf8Cb/0WuWh1rme/VzO9joeOb2eM9J+0MHpAcNj7o=; b=K503rsnWYgeWZij9b92V0JuCW9xfuQYbgX8+Pkvx88UhZ52IWAt5jL4sfX7PJAGlz6 UsMbCfg9184ehJ2rb5gGNvr4fMvcjUg5B2vsZxZa5gNtG8zlPWbaMXRcGCJB0OOYXqA5 TttsK9uP/+5nRyM1JgGki5JQH6RYI84ILL1XS0e75jGyDdhZTKdecFP+Zj0mZzjbyoeO uT8eIOu0RwO7jG96WPi8Y5OrtUH7SWy33Rfan6RsV+b1lP32D1JCsopiUc/62dtSLTAB g5zFI5IAZSIWuO1dSgefyeBhDjPsIvXJZhwmsy7xPKK58Ont/hcdf/tDqzkfGFxQJUSn tstA== MIME-Version: 1.0 X-Received: by 10.58.22.36 with SMTP id a4mr8070722vef.28.1370958845530; Tue, 11 Jun 2013 06:54:05 -0700 (PDT) Received: by 10.58.239.68 with HTTP; Tue, 11 Jun 2013 06:54:05 -0700 (PDT) Date: Tue, 11 Jun 2013 15:54:05 +0200 Message-ID: Subject: http request (no only session) replication in cluster From: Ja kub To: Tomcat Users List Content-Type: multipart/alternative; boundary=089e013a0624fd581604dee13a53 X-Virus-Checked: Checked by ClamAV on apache.org --089e013a0624fd581604dee13a53 Content-Type: text/plain; charset=ISO-8859-1 What can be done to guarantee failover in below scenario: 2 tomcats behind cisco loadbalancer 1 http request can last very long about 50 seconds - response from webservice can take so long load is 200 requests per second I must response in max 4 seconds more than backing webservice is there something like http request replication ? 50 s * 200 req/s = 10.000 pending requests if one tomcat is eg killed, can in any way other tomcat serve his requests ? is there any out of the box solution, eg similar to session replication ? regards ps is it possible to save socket to database, or send it via network? --089e013a0624fd581604dee13a53--