session.getId() vs JSESSIONID in Wildfly 8.1 final (standalone cluster httpd with mod_proxy)

maderhan Nov 11, 2014 6:00 AM

I have a 2 node cluster with httpd + mod_proxy in AS 7.2.

After migration to wf8.1final we got problems with invalid sessions.

Now my question: Why is the "instance-id" attribute from the undertow subsystem only attached to the JSESSIONID cookie and not the the SESSIONID as well?

Thank you for any help!!

1. Re: session.getId() vs JSESSIONID in Wildfly 8.1 final (standalone cluster httpd with mod_proxy)

rhusar Nov 11, 2014 9:20 AM (in response to maderhan)

The result of session.getId() is correct - this is the actual Id. Load-balancers employ the cookie to append information about session routing to do session stickiness. When you are requesting session.getId() the instance-id/jvmRoute name is already stripped.
1 of 1 people found this helpful
Actions
2. Re: session.getId() vs JSESSIONID in Wildfly 8.1 final (standalone cluster httpd with mod_proxy)

maderhan Nov 11, 2014 9:26 AM (in response to rhusar)

I just was wondering about that, because in AS7.2 the instance-id has been appended to the sessionid.
Actions

Go to original post