Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (herse.apache.org: domain of david.vancouvering@gmail.com
 designates 209.85.146.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=rWNXe0AEcDr6s7p5szUmMnqdvLNbektAK4kSNGNg4rxUJIOLuNpOFvmux1VZjuQuhvnn6IuBlqMZ9OSv1VSRVzgF7QRWrQiAdnwnzLTaNkYwMYV4qYKPUZRpoQgXGIMxmZdK7aX6NJbMusd1xK4J/4A4wj9OSHA1O5Q63hbhTpY=
Message-ID: <56a83cd00706022158q4c3036dfq8f996067ffb32cac@mail.gmail.com>
Date: Sat, 2 Jun 2007 21:58:18 -0700
From: "David Van Couvering" <david@vancouvering.com>
Sender: david.vancouvering@gmail.com
To: "Derby Discussion" <derby-user@db.apache.org>
Subject: Re: Cannot get a connection, pool exhausted
In-Reply-To: <10922522.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <10922522.post@talk.nabble.com>

This might be a better question for the forum of the app server you're
running on.  I can't tell which app server it is, it looks like
Glassfish?

It sounds like the connections are not being released after you use
them.  I don't know what your application code looks like, but could
you be possibly holding on to a reference to the connection object
somewhere?  Are you calling close() on the connection object at the
end of each transaction?

David

On 6/1/07, hk <hyunkichung@yahoo.com> wrote:
>
> Even though I am the only user to connect a database, I get the error message
> quite soon.
> How can I avoid the error message? I have tried to increase maxActive to
> double, however it just can stay double number of database connection. In
> fact, I was expecting that, because I was the only user, the database
> conection maxActive 8 should be enough.
>
> I use JNDI connection pool. My resource in the context.xml is set up like
> below
>
>
>   <Resource
>     name="jdbc/NetBlockFlixster"
>     url="jdbc:derby://localhost:1527/Net"
>     auth="Container"
>     driverClassName="org.apache.derby.jdbc.ClientDriver"
>     type="javax.sql.DataSource"
>     maxActive="8"   maxIdle="4"
>     maxWait="1000"
>     username="app"  password="app" />
>
>
>
>
> --
> View this message in context: http://www.nabble.com/Cannot-get-a-connection%2C-pool-exhausted-tf3855182.html#a10922522
> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>
>