"Tim Funk" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Me thinks this is your problem. You have some variables being shared which > are not thread safe. >
Most common reason why, but intermediate caching proxies can do this too. > > -All JSP pages extend a common class which writes the header and footer > > using the JspWriter. > > > -Tim > > Florian wrote: >> Hi. >> >> I have a group of developers that are experiencing an intermitent problem >> with some of the their JSP pages when concurrent users are using the >> application. >> They have had a hard time reproducing the issue in the development >> environement >> so the details are still sketchy. I wanted to post this anyway hoping >> someone would recognize this as a know issue. >> >> The scenario: >> User A is requesting JSP page X and User B is requesting JSP page Y. >> >> The symptoms: >> User A: instead of seeing Page X, user X sees the header of page X and >> then Page Y with the date from user B's session. >> >> User B: sees a blank page. >> >> Additional clues: >> -The user session are unaffected by the event described above. A simple >> refresh allows the user to recover. >> -A "stream has already been closed" exception is thrown by the code for >> Page X >> when an attempt is made to write to it. >> -All JSP pages extend a common class which writes the header and footer >> using the JspWriter. >> -No static or instance variables are used. >> -Using Tomcat 5.5.17 >> -Using 1.4 on Solaris 10. > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
