Envionment - ExaLogic Server and JDEV 11.1.1.7
Hi All, Just wanted to clarrifying on setting the Inactive Connection timeout value in weblogic server.
As per Andrejus Baranovskis Blog-Monitoring Data Source Connection Leaks-
http://andrejusb.blogspot.com/2010/02/monitoring-data-source-connection-leaks.html
-In order to optimize Data Source usage, you need to enable Inactive Connection Timeout option in WebLogic Console. With this option enabled, WebLogic will try to return inactive reserved connections from Connections in Use pool to Available Connections pool. This will prevent Connections Pool Size grow. Just set positive number of seconds
But then i read on another forum -
After more testing, research and discussion with Oracle Support we have come to the conclusion that you should not use the Inactive Connection Timeout feature of the connection pool with ADF apps. We have successfully used the Inactive Connection Timeout feature with our other in-house developed Java apps but they do not utilize the JPA. The problem is that the application modules depend on the database connections being open and not closed by some background process. Most of the time they seem to handle the loss of connections okay but occasionally they don't. I did some testing with settings of 1 and 2 hours and came to the conclusion that the Inactive Connection Timeout wasn't really needed. I believe this one feature is the sole cause of the problem we have been seeing.
Can anyone please sugegst which one is correct . Should i enable or not ?
Thanks in Advance..