I'm investigating an issue with an application that uses "connection pooling". Basically it creates a number of connections at start-up and and then uses them as required. What I think is happening is that as the connections are idle until used, they are being timed out. Is there any way of logging when a connection is timed out, to confirm this.
I know I could just increase the timeout, but want to prove my theory before I investigate this option.
Error Message %PIX|ASA-6-302014: Teardown TCP connection id for
interface:real-address/real-port to interface:real-address/real-port duration hh:mm:ss bytes
bytes [reason] [(user)]
<<<<< Reason = Conn-timeout
should have one for UDP as well but I did not find it.