One reason might that connections are split into two pools, with and without transaction.
AFAIK this is dependend to the database, Oracle need this.
So if you configure 30 it can be happen that 60 are opened.
I don't think this is the case. We're seeing this with DB2 and PostgreSQL, and we see the number of connections gradually climb to more than double. For example, max=25 and we see 130 connections.
My current theory is that there is some kind of memory leak, and JBoss doesn't "know" that these connections are still open. But it's just a theory.
As i stated above, we are running JBoss EAS 4.3. I understand that this includes the code for the community version 4.2.1.
Today we were able to do preliminary testing with Community version 4.2.3, which is currently the highest available version in the 4.x trunk. We were not able to replicate the problem with 4.2.3 yet. More testing is needed, but i'm beginning to have strong suspicions that there is something wrong in the database pooling code in 4.3 (4.2.1), which was fixed in a later version. Does this ring any bells?
If i wanted to turn on debug logging for the code that maintains the database connection pool, what classes would that be?
If i wanted to replace the database pooling code on 4.3 with later code, which jar files should i replace?
Thank you again!