-
1. Servlet container did not change the session ID
ivajloip Mar 1, 2011 7:57 AM (in response to ivajloip)Just to clarify how I reproduce it: first - start jboss web server; after that - kill it and start it again (I think it is the same as reload from the manager). After that if I logout from the application and log back in, I got this warning.
-
2. Servlet container did not change the session ID
welle Mar 1, 2011 8:10 PM (in response to ivajloip)I've seen this before. From what I remember I dont think that the specification says that a new sessionid must (or should) be generated if a new one is requested when a sessionid already is "tied" to the call.
No answer.... just some input...
-
3. Servlet container did not change the session ID
jfclere Mar 2, 2011 3:31 AM (in response to welle)try org.apache.catalina.connector.Request.SESSION_ID_CHECK=true
-
4. Servlet container did not change the session ID
ivajloip Mar 2, 2011 12:25 PM (in response to ivajloip)Thank you both for your quick responses. Jean-Frederic Clere, I will try it soon and I will tell you if it worked
-
5. Servlet container did not change the session ID
ivajloip Mar 11, 2011 4:23 AM (in response to ivajloip)After I added org.apache.catalina.connector.Request.SESSION_ID_CHECK=true to CATALINA_OPTS it worked Thank you again!