Return-Path: 
 <dev-return-80483-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-dev-archive@www.apache.org
Received: (qmail 56758 invoked from network); 23 Feb 2010 23:58:52 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 23 Feb 2010 23:58:52 -0000
Received: (qmail 97100 invoked by uid 500); 23 Feb 2010 23:58:51 -0000
Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org
Received: (qmail 97003 invoked by uid 500); 23 Feb 2010 23:58:51 -0000
Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@geronimo.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@geronimo.apache.org>
List-Post: <mailto:dev@geronimo.apache.org>
Reply-To: dev@geronimo.apache.org
List-Id: <dev.geronimo.apache.org>
Delivered-To: mailing list dev@geronimo.apache.org
Received: (qmail 96995 invoked by uid 99); 23 Feb 2010 23:58:51 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Feb 2010 23:58:51 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Feb 2010 23:58:49 +0000
Received: from brutus.apache.org (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id E709B234C052
	for <dev@geronimo.apache.org>; Tue, 23 Feb 2010 15:58:27 -0800 (PST)
Message-ID: <1268883302.477521266969507945.JavaMail.jira@brutus.apache.org>
Date: Tue, 23 Feb 2010 23:58:27 +0000 (UTC)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-4993) Requests for db pool resources
 will exceed Max Pool Size when EJBNetworkService beans are all busy
In-Reply-To: <824488137.1261247058232.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/GERONIMO-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837530#action_12837530 ] 

David Jencks commented on GERONIMO-4993:
----------------------------------------

Unfortunately that build was made before the fix, so it would definitely illustrate the problem :-)
We're working on getting a snapshot build out that includes the fix or if you are in a bigger hurry you can try building the 2.1 branch yourself....

> Requests for db pool resources will exceed Max Pool Size when EJBNetworkService beans are all busy
> --------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4993
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4993
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.1.3, 2.2
>         Environment: Linux and Windows XP
>            Reporter: Eric Phetteplace
>            Assignee: David Jencks
>         Attachments: _PoolTest.war, screenshot-1.jpg
>
>
> In production, I have 100 EJBNetworkService threads.  It works OK until there's a spike in traffic and all the threads are being used, and the 40 "max pool size" is ignored, and Geronimo makes 100's of DB connections.
> In production, I am using an Oracle DB pool, so the DBAs aren't happy when my servers use up all the available server connections.
> To recreate:
> 1.  Change config.xml and start Geronimo:
>     <module name="org.apache.geronimo.configs/openejb/2.2-SNAPSHOT/car">
>         <gbean name="EJBNetworkService">
>             <attribute name="port">${OpenEJBPort + PortOffset}</attribute>
>             <attribute name="host">${ServerHostname}</attribute>
>             <attribute name="multicastHost">${MulticastDiscoveryAddress}</attribute>
>             <attribute name="multicastPort">${MulticastDiscoveryPort}</attribute>
>             <attribute name="clusterName">${ClusterName}</attribute>
>             *<attribute name="threads">5</attribute>*
>         </gbean>
> 2.  Reconfigure the jdbc/ArchiveDS DB Pool:
> Max Pool Size: 3
> Blocking Timeout: 1000
> Idle Timeout: 1
> 3.  Install WAR 
> 4.  In web browser, go to http://localhost:8080/PoolTest/PoolTest.  Reload it 5 times.  Take your time It should be fine, and will give you an error when the pool is maxed.
> 5.  In JMX Viewer, go to Geronimo MBeans, JCAConnectionManager, and pull up jdbc/ArchiveDS.  Note the connection count.  Looks good.
> 6.  Wait for the connection count to return to 0.
> 7.  In your browser, hold down F5 so the page reloads many times.
> 8.  Observe the connection count again.  It will be over connections.
> 9.  If you repeat 6-9 you can easily get > 20 connections.  I just held F5 for 6 seconds and there are 60 connections.
> I will attach WAR (I don't see an option on this screen).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.