anonymous wrote : Are you saying that after 5 minutes the number of connections falls below 10? Perhaps, and No. Let me try to clarify what I was trying to say in my previous post: It only takes about five minutes for all existing connections to the database to be closed and replaced with new ones (the PIDs on the db server verify this). What I suspect is happening is this: connection #10 of 10 (the LRU) has exceeded idle-timeout-minutes so it gets closed leaving only 9 connections in the pool. A different thread notices the number of connections has fallen below the min-pool-size and creates a new one. This was supposed to be my first question: Why doesn't one hand no what the other is doing? Why have one thread close an "idle" connection if that will cause the number of connections to fall below the specified min-pool-size? The quote in my original post referenced the - to me - confusing section of the documentation that led me to question this. To me the documentation implies that this is what is going on. Secondly, in my environment ALL connections get closed & replaced and this only takes about 5 minutes. We have approx. 300 simultaneous users accessing the system w/ an auto-refresh configured to take place every 3 minutes. In other words we see about 100 hits per minute. With this kind of activity - why would we see the top n connections get recycled? Shouldn't some of the connections be used over & over and not be idle? This is based on my understanding of the MRU strategy used to dole out connections from the pool. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137910#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...