DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=44257>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44257 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2008-01-26 07:54 ------- Having looked at bug 25792 and tested it on the latest TC4 code, it appears to have been caused by some early TC5 refactoring and so is not an issue for TC4. The obvious thing for you to try is to upgrade to 4.1.36. I checked the release notes and I don't see any obvious changes that might be a fix for this issue but there are plenty of other fixes worth having. Your deduction that the user's session ID is being set to null is not consistent with the way sessions are managed by Tomcat. For whatever reason, the session the user requests does not exist. It could be that the session has expired (rightly or wrongly) or the client could be requesting an invalid session ID. At the minute, this looks more like an application or configuration issue rather than a Tomcat bug. My recommendation is that you implement a combination of session listener, request logging and some application logging to confirm: - when sessions are created and destroyed - the session requested in each request - the session being used in each request This should help get to the root of this issue. Bugzilla is not meant to be used as a support forum. Therefore, I suggest you use the users list to seek help in tracking down the source of this issue. For now, I am closing this as invalid. If the users list discussion concludes there is a bug here then the issue can be re-opened and the steps to reproduce the issue added. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
