What is the relationship between the SessionPool.timeout value and Connection object behavior?
I have an application using a global SessionPool and child threads use Connection objects passed to them from
acquire to get connection objects to do work. The main thread maintains a list of some of these connections that need to be reused later for multiple queries.
I set a SessionPool.timeout to something like 1hr in the hopes that as the main thread's list of Connections grows, if they arent used then they closed automatically. Is this the intended behavior/purpose of the SessionPool.timeout property or am I misunderstanding what its there for?
It just seems odd to have that property in the SessionPool but not be able to ask an individual Connection object if it has been closed due to inactivity if thats the case.