Return-Path: X-Original-To: apmail-jackrabbit-users-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4BC4464AC for ; Thu, 16 Jun 2011 17:42:15 +0000 (UTC) Received: (qmail 67289 invoked by uid 500); 16 Jun 2011 17:42:14 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 67259 invoked by uid 500); 16 Jun 2011 17:42:14 -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 67251 invoked by uid 99); 16 Jun 2011 17:42:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jun 2011 17:42:14 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of chadmichaeldavis@gmail.com designates 209.85.214.42 as permitted sender) Received: from [209.85.214.42] (HELO mail-bw0-f42.google.com) (209.85.214.42) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jun 2011 17:42:07 +0000 Received: by bwz18 with SMTP id 18so819733bwz.1 for ; Thu, 16 Jun 2011 10:41:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=1subXfVeXhpur+0qxtGvnABCWoVJlPKklmCupjkYAZQ=; b=ndW4Juv2dIf2yvHUpn4ZJx9g6Qecfh04AHFoXze9ginAs+Y2AHcWxwM6/7r5+hOPQc dOFMixbJQDujFVAr86ylLrncAF+2FsCN3B8zICYJruOUOI6FWCB/ch1fL/6W8YIM1FTR w7AiLSNqrTfqzkLt5+Eo46jQAbZ+GUzoV4F9M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=PxUQ6pTVMcDblQMEpkZqy6vM5YL85YHnMCYUhhYRNb72zPptPKS4xsbLS2INpqHAn4 1zULm4PvAO9E+NxMxadVvaXIVIX/YRzQExKgmuanMhTWWWLS9ZXbqI3nQ5kjOJFMFuL8 gP4CT7yCwqGP2TiD5Kr5c/2uPFZPLiCjytnh8= MIME-Version: 1.0 Received: by 10.204.22.12 with SMTP id l12mr116135bkb.178.1308246106803; Thu, 16 Jun 2011 10:41:46 -0700 (PDT) Received: by 10.204.114.211 with HTTP; Thu, 16 Jun 2011 10:41:46 -0700 (PDT) Date: Thu, 16 Jun 2011 11:41:46 -0600 Message-ID: Subject: DavEx Remoting Performance From: ChadDavis To: users@jackrabbit.apache.org Content-Type: multipart/alternative; boundary=00032555adfe798dd904a5d7c85c X-Virus-Checked: Checked by ClamAV on apache.org --00032555adfe798dd904a5d7c85c Content-Type: text/plain; charset=ISO-8859-1 I'm doing stress testing on a DavEx remoting set up. We're seeing a bottleneck between our app ( the JCR client in a davex remoting set up ) and the repository server. When we increase the number of concurrent users hitting the app, the number of TCP connections between our app and the repository server stays at only two. Is there some configuration for the TCP connection pool in the DavEx client? --00032555adfe798dd904a5d7c85c--