TrackWise Timeout Error
There are few reasons for Timeout error but most of the time application filter counting the ideal time of the user if application found ideal time more than mentions at deployment descriptor then through timeout error.
When I say ideal time means user may be logged in to TrackWise but not generating any event, maybe just typing in a flex field, so there is no action from the user site and no event generated so the filter does not get trigger and think no user present that’s why for application security, session killed automatically by the system.
Now let’s understand what I mean application filter counting and from where it's counting, like many application TrackWise, is a java based application which has designed by JSF architect.
Deployment descriptor or web.XML, where session expires timeout parameter, has set by the administrator by default it's 30.
You may want to take into consideration the following: -Timeout parameter in the Tomcat web.xml -What happens when you cannot find the parameter in the TrackWise web.xml -Where these .xml files can be found and which of the two takes precedence over the other if the parameter is seen in both files. Contacts who have been granted access to Sparta Systems Customer Community Portal can search the Knowledgebase for additional detail or contact Customer Support: https://spartasystems.force.com/customercommunity
Really helpful sir👍