Doug, Life was definitely simpler when I only had 6.3 RUT straight to the 6.3 AR Server to worry about. Users in a busy environment tend to lose track of time so the timeout they are experiencing may not be as short as 15-20 minutes, but that is what they reported. I read the tomcat session timeout is 30 minutes by default and that could be part of the issue. Still digging. Any insight on fine tuning would be greatly appreciated.
Mark From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mueller, Doug Sent: Friday, February 22, 2013 3:20 PM To: [email protected] Subject: Re: Frequent Session Timouts ** Mark, Many others have commented about various topics around this. Yes, you do need the "sticky" setting for the load balancer in front of mid-tiers (you do not have to have that over the AR System server). Over time we will not require it over the mid-tier either but we do for now. You have two things that can timeout - your AR System session and your web connection. If either of them timeout, you will get the login message. Note, if your web connection times out, you do have to relogin to re-establish even though the AR System session may still be active. You comment folks are getting timeouts at the 15 minute or so interval..... Wellllll, looking at your configuration below, there is a very interesting number 15 sitting there on the load balancer connection lifespan (minutes) line.... So, if you are timing out of the load balancer, you are losing contact with your midtier instance which triggers a relogin from the midtier. An interesting thing you could check. If you went into the Current Users screen, you may see a user who is getting the relogin still present and registered with AR System. This is an indication of losing the midtier session but not the AR System session. The link between the 15 minute for user error and connection lifespan of 15 minutes seems compelling. What if you made that 60 minutes to match the AR timeout. An even if not this, you should make any SESSION type timeout match what you set AR System to so that the same interval in all these places is what triggers a timeout for a user. Doug Mueller From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Brittain, Mark Sent: Friday, February 22, 2013 9:52 AM To: [email protected]<mailto:[email protected]> Subject: Frequent Session Timouts ** Hi All & TGIF, Currently I have a VIP and then two load balancers pointing to two mid-tier servers. Each mid-tier points to a load balancer that points to the two AR Servers. As shown below the session timeout is set to 60 minutes but I have users complaining the frequently need to log back in after about 15-20 minutes. The desired behavior is that any load balancing takes place when the session is started (e.g. login). If the user is active at least every 59 minutes, the session remains in place. After 60 minutes of inactivity, the session is terminated. Any setting suggestions on how to a achieve this would be greatly appreciated. Finally is there a difference between a session and a connection? Thinking like an end user, it is the same. Mid-Tier Version 7.6.04 SP3 General Settings - Session Timeout (minutes) - 60 Setting to support Load Balancers Enable Lifespan - checked Connection Lifespan (Minutes) - 15 Connection Pool Settings Maximum Settings per Server - 80 Connection Timeout (Minutes) - 5 Idle Connections per server - 5 Mark Mark Brittain Remedy Developer ITILv3 Foundation NaviSite - A Time Warner Cable Company [email protected]<mailto:[email protected]> Office: 315-453-2912 x5335 Mobile: 315-882.5360 ________________________________ This e-mail is the property of NaviSite, Inc. It is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential, or otherwise protected from disclosure. Distribution or copying of this e-mail, or the information contained herein, to anyone other than the intended recipient is prohibited. _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
