Ouch. ;)
That was it. We searched through all the JSPs and fixed that in several
places. The problems are greatly reduced now. Thank you very much!
Is there any analog to this in Servlets? Is there a clearly incorrect
way variables could be scoped in the a Servlet that could lead to the same
%! String myVar =;%
creates an instance myVar in the servlet. Only 1 instance of a given servlet
is loaded at a time and many requests all execute the service() method
concurrently.
%String myVar=;%
would create a variable in the scope of the _jspService() method. Which is
thread safe.
On Fri, 7 Jan 2005, Caldarale, Charles R wrote:
My browser requested listByOwner.jsp but received
decodedDataChartContents.jsp. I expected listByOwner
but saw decodedDataChartContents.
One of the more common causes of this is inadvertent data sharing due to
applications that aren't thread-safe.
The code below is a disaster. It creates a variable called result at the
servlet instance level. This means that 2 concurrent requests to that JSP
page will cause the page to fail. I didn't read the reast of the code -
because that line is so evil - that ... well I'm speechless.
Change it to:
This is a follow-up to my question. I hope someone might have seen this
before. I don't know if this is a Tomcat, or mod_jk, or Apache issue, but
since I've only seen it with JSPs, I think Tomcat or mod_jk factor in.
Here are entries from Apache's combined access log when the problem
occurs:
From: Brian McEntire [mailto:[EMAIL PROTECTED]
Subject: Apache returning different sizes for same request [was Re:
Controlling caching / session collision]
My browser requested listByOwner.jsp but received
decodedDataChartContents.jsp. I expected listByOwner
but saw
