Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Orphan Timeout & Idle Timeout in WebSphere 4.0

 
Carol Chen
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Everybody,
I am a little confused about the Orphan timeout & Idle timeout of Data source connection pool used for Servlet. What will WebSphere do after the number of seconds of Orphan timeout? WebSphere will close the connection or return to the connection pool?
What is happening to the Idle timeout?
Thanks,
Carol Chen
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Carol Chen:
Hi Everybody,
I am a little confused about the Orphan timeout & Idle timeout of Data source connection pool used for Servlet. What will WebSphere do after the number of seconds of Orphan timeout? WebSphere will close the connection or return to the connection pool?
What is happening to the Idle timeout?
Thanks,
Carol Chen

If a connection is held outside the pool but not used longer than the "Orphan" timeout it is then returned to the pool. If a connection remains unused in the pool longer than the idle timeout, and if the pool is greater than the minimum pool size, the connection is removed from the pool and destroyed.
Kyle
 
Carol Chen
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Kyle:
I read an article about WAS v3.5 for AS/400, and it says:
"Orphan timeout
Type the number of seconds that a connection holder is able to hold a connection without using it. If a connection holder does not use the connection that it has for this number of seconds, WebSphere Application Server closes the connection. "
My question: Is the "WAS returns the connection to the pool" the same as " WAS close the connection" ?
Thanks
Carol Chen
 
sandhya menon
Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
with my little experience I feel this way :
Orphan time out make sure idle connection held by ur application is returned to pool even if close() is supposed to do the same.
Idle time out returns back idle connection to your DataBase .
Pls comment
Regards
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Carol,
Sending close() to a Connection returned from a DataSource (a pooled connection) doesn't destroy it -- it just returns it to the pool. When the orphan timeout expires (which means that the program did NOT send close() to it) then the framework sends close() to the connection, thus returning it to the pool.
Kyle
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic