Thanks Arie. We don't have OneConnect configured on our LTM's so I'm not familiar with that setting. Can you tell me how it would benefit us? Also, we opened a case with F5. With F5 on the WebEx the issue of the stale persistence entry went away but the issue morphed into a problem with new connections (client app restarts) not going to the pool member with the least amount of connections. The pool is set for least connections member. The F5 Engineer agreed that this is not the way the LTM should behave so he is going to dig deeper and try to figure out a resolution.