JSESSIONID Cookie failover

Hi Brett,

 

 

If the ID's are true one way hashes, it actually wouldn't actually help to see examples.

 

 

I wonder if the server which sets the cookie always lists itself as the first node in the jsessionid cookie value? If so, you could keep a mapping of the current hashes and work out which server IP:port a secondary hash corresponds to once that server had set a cookie.

 

 

 

Load Balancers and the WebLogic Session Cookie

 

http://download.oracle.com/docs/cd/E11035_01/wls100/cluster/load_balancing.htmlwp1028843

 

 

The format of a session cookie is:

 

 

sessionid!primary_server_id!secondary_server_id

 

 

where:

 

 

* sessionid is a randomly generated identifier of the HTTP session. The length of the value is configured by the IDLength parameter in the element in the weblogic.xml file for an application. By default, the sessionid length is 52 bytes.

 

* primary_server_id and secondary_server_id are 10 character identifiers of the primary and secondary hosts for the session.

 

 

Note: For sessions using non-replicated memory, cookie, JDBC, or file-based session persistence, the secondary_server_id is not present. For sessions that use in-memory replication, if the secondary session does not exist, the secondary_server_id is “NONE”.

 

 

 

 

If that seems plausible, let me know and I'll try to come up with a rough version for you to try testing. Also, can you confirm which LTM version you're running?

 

 

Thanks,

 

Aaron