I am using common-dbcp-1.4 and commons-pool-1.5.7.
I have a pool that has the following settings:
MaxActive=96
MaxIdle=24
InitialSize=24
MinEvictableIdleTimeMillis=1800000 (30 mins)
NumTestsPerEvictionRun=3
TimeBetweenEvictionRunsMillis=120000 (2 mins)
When I first start up my application that uses this pool the app starts 28
connections. I see monitoring the database that 28 connections are initially
made and monitoring getNumActive() on the pool instance shows 28 connections
too.
But within seconds the database shows that this drops down to 24 connections.
Whilst the application isn't using these connections now I still would not
expect the connections over the MaxIdle setting to be collected so quickly.
I would expect the evictor running every 2 minutes not to clean up these idle
connections until they have been idle for 30 minutes. Is my understanding
correct?
***********************************************************************************
The Royal Bank of Scotland plc. Registered in Scotland No 90312.
Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB.
Authorised and regulated by the Financial Services Authority. The
Royal Bank of Scotland N.V. is authorised and regulated by the
De Nederlandsche Bank and has its seat at Amsterdam, the
Netherlands, and is registered in the Commercial Register under
number 33002587. Registered Office: Gustav Mahlerlaan 350,
Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and
The Royal Bank of Scotland plc are authorised to act as agent for each
other in certain jurisdictions.
This e-mail message is confidential and for use by the addressee only.
If the message is received by anyone other than the addressee, please
return the message to the sender by replying to it and then delete the
message from your computer. Internet e-mails are not necessarily
secure. The Royal Bank of Scotland plc and The Royal Bank of Scotland
N.V. including its affiliates ("RBS group") does not accept responsibility
for changes made to this message after it was sent. For the protection
of RBS group and its clients and customers, and in compliance with
regulatory requirements, the contents of both incoming and outgoing
e-mail communications, which could include proprietary information and
Non-Public Personal Information, may be read by authorised persons
within RBS group other than the intended recipient(s).
Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the onward
transmission, opening or use of this message and any attachments will
not adversely affect its systems or data. No responsibility is accepted
by the RBS group in this regard and the recipient should carry out such
virus and other checks as it considers appropriate.
Visit our website at www.rbs.com
***********************************************************************************
