How and when is a JCO connection closed in version 3.xx?
Hi, in older versions of JCO (2.xx), the connections where handled directly: the developer needed to create the connection and then close it. It was intuititve.
With the newer versions there's no closing connection method, just getDestination methods.
I was wondering: how and when is an established connection closed?
Thanks in advance.
Markus Tolksdorf replied
Connection management has been moved into the JCo runtime. Separation of concerns: Applications should concentrate on application logic and should not have to deal with technical stuff like opening and closing connections.
When a connection is closed depends on the configuration of the destination, from which the connection was generated from. Typically, connections are pooled and as long s the idle timeout is not reached, the connection will remain open. How long and how many connections are pooled is described in the configuration of a destination. Check out the DestinationDataProvider documentation. Furthermore, connections stay open that are still in use in an active client session context.