Here are entries from Apache's combined access log when the problem occurs:
192.168.1.1 - - [07/Jan/2005:18:01:36 -0500] "GET /jsp/dipper/listByOwner.jsp HTTP/1.1" 200 5601 "-" "Java/1.4.2_06"
192.168.1.1 - - [07/Jan/2005:18:01:36 -0500] "GET /jsp/dipper/decodedDataChartContents.jsp HTTP/1.1" 200 8503 "-" "Java/1.4.2_06"
192.168.1.1 - - [07/Jan/2005:18:02:09 -0500] "GET /jsp/dipper/listByOwner.jsp HTTP/1.1" 200 8503 "http://server-obscurred.gov/dipper/contents.html"; "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5"
Those entries are slightly sanitized. The point is, in the first entry, the size of the response sent by Apache back to the client for listByOwner.jsp is correct at 5601. The correct size is sent back for decodedDataChartContents.jsp in the second entry at 8503.
The problem presented with the third request: Apache sent back the wrong response. My browser requested listByOwner.jsp but received decodedDataChartContents.jsp. I expected listByOwner but saw decodedDataChartContents. Apache's log shows that the response it served was the same size as decodedDataChartContents.jsp even though the request was for listByOwner.jsp.
Has anyone seen this before? Any ideas what would cause that or how to prevent it?
Thanks! Brian
On Fri, 7 Jan 2005, Brian McEntire wrote:
I am running Tomcat 5.0.28, mod_jk 1.2.8, and Apache/2.0.46 on Redhat Enterprise Linux WS 3.0.
We have an HTML page that is a frame: top (banner), left hand (menu), and right hand (main content). There are 6 hyperlinks in the LH pane that point to *.jsp pages that load in the RH pane via a
<BASE TARGET="displayContents"> tag. Usually, these links work. But occasionally when clicking one link, content that belongs to another link appears in the main/RH pane. This problem seems to get worse the longer Tomcat is up.
The JSPs that we are using don't make use of sessions as far as I can tell. Logins are not required. The JSPs are only used to generate dynamic content and forms for submission.
I have tried setting the following in workers.properties: worker.workerHADS.socket_keepalive=FALSE worker.workerHADS.cache_timeout=60 worker.workerHADS.cachesize=1 worker.workerHADS.reclycle_timeout=30
I added this within the <head></head> section of each JSP: <META HTTP-EQUIV="Pragma" CONTENT="no-cache"> <META HTTP-EQUIV="Expires" CONTENT="-1">
But the problem still presents occasionally. It happens on Mozilla and IE browsers, and probably others. It looks like a server side issue. It is not 100% reproducible. It cannot be reproduced immediately after Tomcat is started. But after several hours (or possibly some number of visitors to the page) it starts to happen and gets more frequent over time.
Any suggestions would be greatly appreciated! Thanks, Brian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
