4 Replies Latest reply on Nov 7, 2014 11:03 AM by jesper.pedersen

    JCA connection manager ActiveCount

    jrwhitley

      I've been monitoring the number of Connections in the pool and it doesn't behave as I would expect. in that I  normally have a small number of connections actually in use (<5), the connections in the pool do not get removed as idle. This appears to be because the pooled connections are used in a round robin fashion and do not stay idle for long enough to meet the idle timeout I have set (10 minutes). Until I discovered this, I spent sometime looking for 'leaking' connections that were preventing connections being timed out of the pool.

       

      Can someone confirm that this behaviour is to be expected?