Persistence Table and Client Connections

Thanks for the details.

I ran the stats close by to get clarity to the session table, the test user EBS timeout was 5 min -- very low to all other timeouts. Yes, the forms session is the EBS timeout while F5 is web session. I would have expected the web session to remain at the low rate of 5 min forms timeout. Maybe there is a reset flag in the web session. I figured the source remaining the same would keep account in the persistence table to continue instead of starting a new one.

We moved (thank god) from Cisco ACE to F5 and the persistence was a quick implementation after a few weeks of being live when a user in a live session would get directed to a new server for a new form breaking forms session. It's been stable for years but they recently set the EBS timeout to 30 min when it hadn't previously existed. My large timers are based on 2 main points of the working day for previous timeout of EBS values, could be adjusted now they have reduced that to 30 min.

As for running forms through F5, that would be having the F5 as the gateway for which replacement of the ACE (happy again) was not achievable to redesign to achieve. That is my understanding since the forms server generates the session separately from the web session. But at least a new EBS version is soon on our horizon so I will have a chance to start a new fresh.

Thanks again. Best to you.