Assuming you don't have any servlet-globals being shared between threads,
and that you otherwise have your
session stuff correct, the thing I would look at is proxy servers. These
will cache pages based on URI alone
-- ie, not taking cookies into account -- and so user 2 will get the page
sent to user 1. If you are running a public
internet site, many users connect via ISPs that have "transparent proxies"
that the users are not aware of.
The fix is to include the various no-cache HTTP header directives and
<META> tags. Examples:
response.setHeader( "Cache-Control", "no-cache" );
response.setHeader( "Pragma", "no-cache" );
<META HTTP-EQUIV="Pragma" CONTENT="no-cache">
<META HTTP-EQUIV="Expires" CONTENT="0">
<META HTTP-EQUIV="Cache-Control" CONTENT="no-cache">
- Fernando
All,
Sorry for the cross post. our environment is Apache 1.3.14/
Tomcat 3.2,
using servlets and JSP pages hitting an Oracle db, on Solaris 2.7. here is
the problem in a nutshell, and yes I have been through the news groups and
tried all the fixes I have seen, browsers one will get browser two's data
and vice versa. The more load the more frequent the problem. The code
jockeys have no idea and are blaming the environment. HELP!
Thank you all in advance for your time,
John
