Strange Connection Pool Behavior
There was one oddity I observed in our app server logs. Due to a problem with running out of DB connections, I turned on connection pool logging.Up to a point, the connection pool reporting is listed as [InUser/Available/Max]: [0/20/20], with the max being [1/19/20] For some reason, there is a log entry that shows a modification of the registering pool to have an idle timeout of 900000 milleseconds (the old being 450000).
After that log line, the connection pool reporting is listed as [0/40/20], which doesn't make much sense. How can there be 40 available connections with 20 max?
Here is the log snippet:
2005-06-06 19:24:47,868 TRACE [org.jboss.resource.connectionmanager.TxConnection
Manager] getManagedConnection trackByTx=true tx=TransactionImpl:XidImpl[FormatId
=257, GlobalId=app1/8, BranchQual=, localId=8]
2005-06-06 19:24:47,868 DEBUG [org.jboss.resource.connectionmanager.IdleRemover]
internalRegisterPool: registering pool with interval 900000 old interval: 45000 0
2005-06-06 19:24:47,913 TRACE [org.jboss.resource.connectionmanager.JBossManaged
ConnectionPool] supplying new ManagedConnection: org.jboss.resource.connectionma nager.TxConnectionManager$TxConnectionEventListener@c15ff6[state=NORMAL mc=org.j
boss.resource.adapter.jdbc.xa.XAManagedConnection@1834848 handles=0 lastUse=1118
103887913 permit=false trackByTx=false mcp=org.jboss.resource.connectionmanager.
JBossManagedConnectionPool$OnePool@149959a context=org.jboss.resource.connection
manager.InternalManagedConnectionPool@1fe9ce1]
2005-06-06 19:24:47,913 TRACE [org.jboss.resource.connectionmanager.JBossManaged
ConnectionPool] Getting connection from pool org.jboss.resource.connectionmanage
r.TxConnectionManager$TxConnectionEventListener@c15ff6[state=NORMAL mc=org.jboss
.resource.adapter.jdbc.xa.XAManagedConnection@1834848 handles=0 lastUse=11181038
87913 permit=true trackByTx=true mcp=org.jboss.resource.connectionmanager.JBossM
anagedConnectionPool$OnePool@149959a context=org.jboss.resource.connectionmanage
r.InternalManagedConnectionPool@1fe9ce1] [InUse/Available/Max]: [1/39/20]