From users-return-13284-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Thu Nov 12 03:28:20 2009 Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 3637 invoked from network); 12 Nov 2009 03:28:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Nov 2009 03:28:20 -0000 Received: (qmail 88608 invoked by uid 500); 12 Nov 2009 03:28:19 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 88544 invoked by uid 500); 12 Nov 2009 03:28:19 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 88532 invoked by uid 99); 12 Nov 2009 03:28:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Nov 2009 03:28:19 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists+1257438615597-510167@n4.nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Nov 2009 03:28:08 +0000 Received: from joe.nabble.com ([192.168.236.151]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1N8QLb-0003bF-GS for users@jackrabbit.apache.org; Wed, 11 Nov 2009 19:27:47 -0800 Date: Wed, 11 Nov 2009 19:27:47 -0800 (PST) From: rokham To: users@jackrabbit.apache.org Message-ID: <1257996467501-612788.post@n4.nabble.com> In-Reply-To: <1257990026096-605518.post@n4.nabble.com> References: <1257990026096-605518.post@n4.nabble.com> Subject: Re: Tomcat stops responding due to too many requests - using Jackrabbit MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: rokham X-Virus-Checked: Checked by ClamAV on apache.org Note that all these requests are WRITING to Jackrabbit. I also just came across this article, claiming that "Jackrabbit isn=E2=80=99t actually able = to handle concurrent queries well".=20 Does this mean I should move away from Jackrabbit? rokham wrote: >=20 > Hi, >=20 > I've written a web application using Jackrabbit. I have Tomcat as my web > server and I'm having a strange problem when a large number of requests > are sent to Tomcat simultaneously.=20 >=20 > Here's the scenario: >=20 > When I have about 7 people accessing the server and sending about 10-15 > requests at a time, the server starts off very strong and keeps going for > about 5 minutes (Each of the 7 people sends 3-4 batches of requests over > those 5 minutes. This means in 5 minutes we have 7 people sending about 5= 0 > requests each. Therefore a total of 350 requests). After the 5 minutes th= e > sever slows down and about 2-3 minutes after doing the same routine, > Tomcat stops responding. >=20 > I was monitoring the system and the CPU was calm and the memory was > running at about 100 MB. But it's really strange that Tomcat stops > responding even though the server is not doing anything. And it's not lik= e > the request has timed out. No error msg or anything is sent back from > Tomcat. >=20 > I'm using Jackrabbit as my DB and I'm having a really hard time spotting > the problem. I don't know if I need to tweak tomcat's configs, or > something in Jackrabbit or is it something with Tomcat and Jackrabbit > talking to each other, that I need to know about. >=20 > I came across the post below and the line saying It is caused by an in > accessible data base. made me wonder if there's a glitch between tomcat > and jackrabbit. > http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg158745.html >=20 > Thank you in advance. Any help is much appreciated, since I need to have > the system ready in a week. >=20 >=20 >=20 --=20 View this message in context: http://n4.nabble.com/Tomcat-stops-responding-= due-to-too-many-requests-using-Jackrabbit-tp605518p612788.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.