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=37356>. 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=37356 ------- Additional Comments From [EMAIL PROTECTED] 2006-02-07 09:26 ------- (In reply to comment #6) > > This problem mostly ocurred when two browser access the same page. > Do you mean that wo browsers use the same session to access a page, or just the ( quite usual ) case that two people use the web application? > And the web application will do following things: > 1. APP A will include some pages in other applications. > 2. There is a request wrapper. when include the page in other applications > and > try to get the session object using request.getSession(), it will get the > session which is generated in App A. That means in the included application B and C you get the session from application A? Application != context for you? > 3. The session objects generated in A, will be managed by our system. (of > cuase , there is one listener to remove the session when it timeout) > Sorry, I can only provide these info for you. So it seems that the common ground for all of us here is, that we have some objects in the session that implement the HttpSessionBindingListener or HttpSessionActivationListener. Maybe the cause lies within these? -- 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]
