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

           Summary: Cookies are not always parsed on simultaneous request
           Product: Tomcat 5
           Version: 5.0.28
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: major
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: [EMAIL PROTECTED]


I find that despite there being an incoming JSESSIONID cookie, sometimes this
doesn't make it into the requests Cookies. I've confirmed this by trapping the
case in my servlet filter, and then examining the request. In this case I can
see the cookie header, but the cookies are empty.

Some specifics - I'm using JBoss 4.0.1sp1, which has Tomcat 5.0 embedded. The
use of the session is in a servlet filter for security. I store a JAAS subject
on the session in my login form, and I test the existence in the filter.

The pages generated by the application then make many other requests. IE
correctly sends the cookie in the requests, but sometimes, perhaps one in five
or one in ten requests, the cookie is ignored as stated in the first paragraph.

I access the sessions using synchronized blocks to avoid multiple simul updates.
I tried adding a sync on the doFilter method on the off chance that there was a
session issue (although, as noted above, the issue appears to be due to the
cookies).

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