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 thing?
The developer, within the JSPs, has a couple lines like:
<jsp:useBean id="statehsaBean" class="postgres.PostgreSQLBean" scope="page" />
And since we are still experiencing the problem (though much less), I wonder if the Servlets now have some similar global variable problem.
Thanks again!
On Mon, 10 Jan 2005, Tim Funk wrote:
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: <% ResultSet result; %>
-Tim
Brian McEntire wrote:
Looking at one of the problematic JSP pages, I see (snippets):
<%! ResultSet result; %>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
