Load Balancing based off TCP Payload entity

Two thoughts:

1. Only attempt to persist if the entityID value is there. In your capture, when the entityID doesn't exist, is it within the same TCP session (same source port) as an original packet that did contain the entityID?

    

2. Try using standard SSL sessionID persistence. Assuming this is not an HTTP/browser-based application, does the client initiate SSL renegotiations? If not, and the initial SSL session is maintained for the life of the application session, then the sessionID should remain consistent.