Forum Discussion
Persistence Table and Client Connections
We went through with the test user set to a lower timeout value and here is the update. When timed out by the application, initiating a new session resets and gives a new age rather than continuing to could up the configured 14,400 seconds on the VIP.
Timed out by Oracle right now:
| Mode source addr Value 10.10.10.207 | virtual 10.51.0.101:teradataordbms node 10.50.1.201:teradataordbms age 539sec
Makes a new session:
| Mode source addr Value 10.10.10.207 | virtual 10.51.0.101:teradataordbms node 10.50.1.201:teradataordbms age 77sec | Mode source addr Value 10.10.10.207
Let the timeout ride from last update.
Current value:
| Mode source addr Value 10.10.10.207 | virtual 10.51.0.101:teradataordbms node 10.50.1.201:teradataordbms age 610sec
Without logging in, taking action that asks for a new login, the session is:
| Mode source addr Value 10.10.10.207 | virtual 10.51.0.101:teradataordbms node 10.50.1.201:teradataordbms age 4sec
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
