Expiration and Clean up thread - MDM connector - Visual administrator

Question

Hi Experts!
I  need some suggestion from the Visual administrator - MDM connector.
We have the default setting for maximum connections, clean up thread time and the expiration set.
As of now, clean up thread value is 300 seconds. and Expiration value is set too. But we could see, as the days goes, the number of connections in the 'UsedManagedSessionsCount' is increasing. I feel the expiration is not working.
Could you kindly suggest, how to ensure the expiration and clean up thread is working?
Thanks,
SK

Answer 1

Hello,
1) Connections are used quite a long time (this depends on how
applications using the datasource is implemented, or how long it keeps
the connections referenced). In this case the solution will be to:
  1.1) Increase the pool size: Maximum Connections Number. The optimal
value for this as a rule of thumb is: the max connections with which the
backend (Database) performs best divided to number of servers in the
cluster.
  1.2) Increase the Maximum time to wait for connection - so the
resource system of J2EE Engine will wait for freed connection longer
before throwing the exception. However, from end user viepoint, this
will lower the performance. But it's better than failure.
  1.3) Enable expiration - set Connection Lifetime to 300 (5 minutes) -
this means that after it is returned to the pool if not referred again
within 5 minutes it is destroyed. Also set the automatic cleanup thread
interval to 180 (3 minutes) - each 3 minutes a thread will be run to
detect idle connections.
regards,
John Feely