I don't think I've seen this kind of error before. At some point we
have fixed a bug in the pooling code that tended to make no
connections available to apps if enough connection errors occurred.
Can you look into whether any connection errors occurred? I'm not
sure but would hope these would end up in geronimo.log.
thanks
david jencks
On Dec 16, 2009, at 8:13 AM, ericp56 wrote:
Hello,
I have a DB Pool with a max pool size of 40.
However, when the DBA looks in the DB, he sees 300 connections!
Using netstat, I can see those 300 established connections.
If I restart the applications, the connections stay there.
If I restart the J2EE connector, the connections are closed.
I'm using G 2.1.4, oracle DB, Oracle 11 jdbc 5 driver.
99% of the time, it stays <=40 connections.
Is there a bug in 2.1.4 enforcing the max pool size? Or, does this
suggest
I look at anything in particular? I'm reviewing the apps...
Thanks,
Eric
--
View this message in context:
http://old.nabble.com/G2.1.4%2C-Pool-Max-Size-not-working-tp26813776s134p26813776.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
