Clarity

[color=#0712a9][size=6][font=Comic Sans]When you receive the TMA-601 error: "Timesheet could not be saved because your session expired. Please re-enter timesheet data.", logging out and back in doesn't always clear the error when accessing the timesheet again. Following the steps from TEC557570often resolve the problem.

This error can also indicate a problem with the Clarity environment. Access CSA and find out if there is such option for "Cache Distributed Session" and if it is checked. When the Cache Distributed Session option is turned on, it stores the session information in the database instead of the cache for the individual application server. The "Cache Distributed Session" option will only show on the Application page in CSA if the "Distributed" option is checked.

We recommend that customers use Session Affinity (or Sticky Sessions) in their load-balancer instead of the "cache distributed session" option. Turning on the "Cache Distributed Session" option can cause a heavy performance hit, because every request for a server will create two hits to the database (a read and a write). This performance gets worse with larger numbers of users and when users are logged in for longer periods of time.[font][size][color]

Thanks for sharing this useful bit, Connie ... :smile

NJ

Thanks for the tip Connie!

Connie_Fu wrote:

[color=#0712a9][size=6][font=Comic Sans]When you receive the TMA-601 error: "Timesheet could not be saved because your session expired. Please re-enter timesheet data.", logging out and back in doesn't always clear the error when accessing the timesheet again. Following the steps from TEC557570often resolve the problem.

This error can also indicate a problem with the Clarity environment. Access CSA and find out if there is such option for "Cache Distributed Session" and if it is checked. When the Cache Distributed Session option is turned on, it stores the session information in the database instead of the cache for the individual application server. The "Cache Distributed Session" option will only show on the Application page in CSA if the "Distributed" option is checked.

We recommend that customers use Session Affinity (or Sticky Sessions) in their load-balancer instead of the "cache distributed session" option. Turning on the "Cache Distributed Session" option can cause a heavy performance hit, because every request for a server will create two hits to the database (a read and a write). This performance gets worse with larger numbers of users and when users are logged in for longer periods of time.[font][size][color]