10.2.3 Persistence Profile inconsistencies

I went back and forth over which option would suit me best....match across services or match across vs. In production, since we've had this problem, I've tried both match across virtual servers and match across services. I'm see the error using either one. As for the timeout....I did have that set to 13 hours so it would last the length of a work-day. Then in reading, I found that keep-alives are supposed to extend the timeout, so if they're logged in, it should never be an issue. With it set to 3 minutes (1800 seconds), I can go back 20 minutes later and it still works for me... I'm able to see that I'm still getting these errors in the web server logs.

 

 

What's kept me from moving to all HTTPS content is that I don't control the content we're service. The site is a portal app with iFrames. Everything that needs to be encrypted is https....but there is a lot of http content as well. I was afraid to tangle with the workings of the site too much since it's based on decade-old practices... The next version of this app will be using similar tactics, but won't give us the session problems we're having now. I'm kind of waiting it out until we deploy the new version to hopefully "clean up" the way it works.

 

 

I'm tempted to try setting a cookie from an iRule as you suggested. It doesn't look like the persistence profile works well enough by itself. I was hoping the persistence tables would be able to track sessions, etc....but at this point, I just want this working.

 

 

Thanks for your suggestions.