Difference in behavior for the orphan_timeout and idle_timeout in connection pool
 Technote (FAQ)
 
Problem
Difference in behavior for the orphan_timeout and idle_timeout in connection pool
 
Solution
Q1: What is the Orphan Timeout and Idle Timeout?
 A1: In the WebSphere infocenter, Properties of datasources,
Idle Timeout is defined as follows: The maximum time in seconds that an idle (unallocated) connection can remain in the pool before being removed to free resources.
This value must be a positive integer.

Orphan Timeout is defined as follows:
The maximum time in seconds that an inactive (but allocated) connection can remain in the pool before being removed.
This value must be a positive integer.

Note that the actual amount of time before a connection is closed is approximately twice the orphan timeout value.

Q2: Is the same is true for Idle Timeouts (the actual amount of time before a connection is closed is approximately twice the Idle Timeout value)?
A2: The answer is no. The actual amount of time before a connection is closed is the approximately the Idle Timeout value.

Q3: Why is actual amount of time before a connection is closed is approximately twice the orphan timeout value?
A3: The timeout for the Orphan Timeout is alarm thread that run in the background.When it awake the first time it marks their victim, and then sleep again for the time.  When it awake the second time, and connections still marked will be handled.



 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server
Operating system(s): HP-UX
Software version: 4.0
Software edition:
Reference #: 1108099
IBM Group: Software Group
Modified date: Apr 17, 2003