Hi all, I've noticed the following behavior in Struts 1.2.4 and 1.2.7: if a brand new request comes in for a non-existent page, then the session information is not sent back with the response (meaning set-cookie is not set). So a second request from the user results in another session! At the end of the requests, there are 2 sessions in existence.
If I remove the sample Filter I've created, then Tomcat is able to attach the session information in the "set-cookie" cookie without a problem. I've attached the code so anyone interested can replicate the problem: http://www.nabble.com/file/p19081154/struts-beans.tar.gz struts-beans.tar.gz To replicate the problem: After deploying the app, please request for a non-existence page... e.g. http://localhost:8080/struts-beans/blah.do This should give you additional session. After this, clicking on register1 will result in a new session! I use LamdaProbe for monitoring the number of sessions, but Tomcat Manager should show that info as well... Anyone with a solution to ensure that only one session is created? Thanks. -V. -- View this message in context: http://www.nabble.com/multiple-sessions-created-in-struts-1.2.x-on-404-new-request...-bug---S1--tp19081154p19081154.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
