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=40072>.
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=40072

           Summary: New Session Created Randomly  in Tomcat 5.0.28
           Product: Tomcat 5
           Version: 5.0.28
          Platform: Other
        OS/Version: Windows 2000
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Servlet & JSP API
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: [EMAIL PROTECTED]


1.  I have a  typical  JSP-Servlet web application running on tomcat 5.0.28. 
 2.  After successful login a new session is created. (in login.jsp) and user
specific data is kept in session
 3.  User moves on through the application .   Accesses  a JSP ( e.g. 
PageWithHeavyJavascript.jsp),  JavaScript code.
 4.  After  doing some selections etc. PageWithHeavyJavascript.jsp,  user
browses another JSP ( e.g.  plain.jsp)  which *does not* have any session
related code. At this point *sometimes* a  NEW session is created. (By
implementing HttpSessionListener I observed that the sessionCreated() methos is
getting called everytime and sessionDestoryed() method is never getting called)
5. After lot of debugging I have observed that this happens when  lot of
Javascript code is called through clicks etc. new session is created. I am
unable to link lot of Javascript calls with New session getting created.
  I would appreciate if you can shed some light on this issue... any 
hint/solution?

-- 
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]

Reply via email to