Re: What is the benifit for enabling oracle.net.keepAlive
This post was updated on .
Are you referring to the Oracle keepAlive for the JDBC thin driver? This is typically related to TCP IP keepAlive at the JDBC driver level.
Typically this is used for thin driver to keep the Socket alive and prevent closure from Oracle side.
You usually don't need to setup this property for type 4 JDBC driver as Java EE containers typically have built-in refresh and "test Connection on reserve" mechanisms which will ensure a JDBC Connection (from the pool) is healthy before using it for your application transaction.