One-Way Persistence records problem

persist lookup does not make load balancing decisions, it just looks to see if there is a persist record that matches what you are using for a key. In fact the none of the persist options make any load balancing decisions, they just lookup, add, delete a "record" of persistence.

I'm fairly sure that switch is no more efficient than a single if.

One possible issue is that you set the lifetime of the persistence record to 315 seconds. So after 315 seconds of no activity from the user, the persistence record will be deleted and the next time they come in the request will be re-load balanced.

Is it possible that there are instances where there is more than 315 seconds between requests from the user?

Is it possible that there are instance where it could take longer than 315 seconds for a response?

On responses servers normally only add cookies when the cookie does not appear on the request. Meaning that the cookie on the response will only appear once, the first time the server sees a request. If a response takes longer than 315 seconds, then the F5 will delete the persistence record, the response will NOT have the JESSIONID cookie, and so the persist command will not be executed.