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 <[EMAIL PROTECTED]> 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.
