Symptom	Explanation	Possible Reasons	How to Check
All my connections are broken	Host sessions become broken if they cannot get to Ready state. Ready means that: The connection is alive. If an "initial screen" is defined by the pool, the session must get there.	Host is unavailable.	Try to connect to the host without the pool.
		Initialization path needs to be modified.	Create a connection outside the pool, run the initialization path and verify it gets to the "initial screen".
Connections disconnect after use but I want to reuse them	The pool may be configured to allow reusing a host connection that was used by a previous user. This would require returning the connection to the initial screen, either by implementing a robust navigation logic inside the invoked procedure or in the recycle path.	The Disconnect after usage option is checked.	Observe the state of the Disconnect after usage checkbox in pool tab of the connection pool.
		The logic of the user activity or the recycle path causes a disconnection from the host.	Capture a trace file for the user activity and recycle path. Observe that the host session is not terminated during the invocation of user activity or the recycle path.
		When a connection is returned to the pool and it is not in the "initial screen", and there is no recycle path that successfully navigates to the initial screen.	Capture a trace file for the user activity and recycle path. Observe that at the end of the user activity and the recycle path invocation, the connection is in the initial screen.
Connections remain Active after use	Upon finishing the user activity on a pool connection, the state of the connection would change according to the pool configuration and the state of the user session. The state of the connection would remain active if the session used by the pool has not ended.	A flow procedure creates an emulation session on a pool connection, but the "end session" node is not called on that session.	Verify the existence of an "end session" node in the flow procedure that creates the emulation session. Verify that the "end session" node is reached by capturing a trace file or by logging the invocation of the flow procedure.
Connections remain Terminating after use	A pool may be terminating a connection based on the pool's configuration, connection count and the status of the session. When doing so, the connection status would become "Terminating" and the termination path would run on the connection. After the termination path is completed, the connection is removed from the pool.	An exception in the termination path is causing the host connection to either get stuck or to terminate before completing the path.	Capture a trace file that includes the invocation of the termination path and observe that the path has completed successfully. Search for exceptions in the server logs that occurred during the invocation of the termination path.
A used connection is disconnecting while being used		The host is disconnecting the pool connection based on the user activity or due to the host state.	Capture a trace file for the user activity, observe the last packet transmissions between the server and the host. Look in the server log for an error indicating a socket close around this timestamp. Also ask the host administrator to inspect the host's log for disconnections.
		Another host connection is using the same host credentials/device name and hijacking the session.	When capturing trace files, you would notice a trace file created at the time when a previous trace file is closed. Both traces will include send sections containing the same credentials or device name.

Note:
When recording trace files to capture the symptoms mentioned above, we recommend using the following variables in the trace file name: connection ID (%c), session ID (%u), creation time of file (%t). See Recording Trace Files for more information.

See Connection Pools for more information.