Forum Discussion
Persistence Table and Client Connections
For the testing that we did with the one user, yes it was consistent. While the connection was running, would run 'b persist show all' and find the age from the table. They would refresh the app from the timeout (browser F5) and then when looking at the table, the age had reset. They were ~3k seconds when the F5 is set on this VIP for 14.4k. It seemed that it would continue to persistence and leads to speculation that the F5 may be apart of it by having a reset session.
Sometime this week, will dig some more, check at the stages between and see what the table and session/connection shows before refresh to log back in. I felt that it should have maintained the persistence entry until the 14.4k seconds was reached, this is what I need as well.
Thanks.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com