WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Reap timeout in Connection pool

    Posted 02/04/14 09:00 AM
    Hello,

    I understand that we require Reap timeout setting to run maintenance thread to pull back the Unused Timeouted & Aged Timeouted Connection to the pool, but a very simple doubt is Once a connection reaches or exceeds Unused Timeout & Aged Timeout they should be ideally back to the pool why do we need a separate maintenance thread to be run'ed after specific time to collect those, at first look I feel its an overhead on the PoolManager. I also understand there would be some logic for sure but I am not able to judge it. Can someone help me explain it if they know it?

    Thanks
    Sumit Tambe


  • 2.  Reap timeout in Connection pool

    Posted 02/04/14 08:59 PM
    Hi Sumit,

      I'm not understanding well your doubt.
     
      Reap timeout is the frecuency of the maintenance thread, Unused timeout discard connections and stop in the min connections and Aged Timeout discard connections below the min connections.
     
      Hope this helps.
     
    regards