Ralph, Thanks again for writing on this subject. We've checked the logs and it does indeed look like Apache is receiving the request, and passing it along to Tomcat.
Our current theory is that there is an error in compiling the revised JSP. If the .class and .java files are there from the previous revision, they are displayed. If those files are not there, then we think Tomcat tries to display a standard file error.jsp. Unfortunately, we don't have a copy of error.jsp in every directory, which the leads to the 404 - File Not Found message. That is the theory of operation we've developed, if it contradicts how Tomcat actually works, please let us know. Under this theory our corrective action is to make sure there is a copy of error.jsp in every directory. Dave Bank >>> [EMAIL PROTECTED] 04/10/02 11:34AM >>> Sorry , but if one jsp works and another not, that doesn't nessesarily mean that the one that didn't work hit the server just because the other did it. With verification i wass thinking of looking at the access log. If apache was hit, hat you should find an corresponding entry in the access.log for this request with the error code 404. If tomcat was hit you should see some messages in the logs that are produced by tomcat. (Depends on the verbosity that you defined) If apache was hit but not tomcat, I would expect an error message in the log of apache. If tomcat was hit I would expect an error message in one of the logs of tomcat. Make shure that you start apache and tomcat in way that stderr and stdout are captured in a log file. > -----Urspr�ngliche Nachricht----- > Von: David Bank [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 10. April 2002 17:21 > An: [EMAIL PROTECTED] > Betreff: Re: AW: Tomcat intermittent failures > > > Ralph, > > Thanks for writing. We've been able to reproduce the situation on > machines which were directly connected to the same LAN on which the > servers are located (and therefore no proxy was involved), > and we tried > clearing browser caches on these machines. The problem persisted. > > When the problem occurs, some .JSP files will compile and run fine, > others won't. So we know Apache is hitting Tomcat and Tomcat > is running > because some files work and some don't. It'll just change - as I said > before, we'll do the restart thing, or even reboot the whole box, and > before, FOO.JSP wouldn't work but BAR.JSP would, and after > FOO.JSP will > work and BAR.JSP won't. But a .JSP file works each time, > confirming that > we are hitting Apache and Apache is hitting Tomcat. > > David Bank > NC CATS Project Manager > Accountability Services - Testing > NC Department of Public Instruction > 301 Wilmington Street > Raleigh, NC 27601 > 919-807-3796 > > > >>> [EMAIL PROTECTED] 04/10/02 03:00AM >>> > Have you verified if your apache got hit, with the request > that caused a 'file not found'? (We have seen in the past > some obscure errors that turned out to be caching problems > of browsers and proxy caches where the server wasn't hit at > all) > > If your apache got hit, did the request hit tomcat ? > > If it hit tomcat can you find any error message that may > correspond to the failure? > (in the tomcat or the apache logs) > > > > -----Urspr�ngliche Nachricht----- > > Von: David Bank [mailto:[EMAIL PROTECTED]] > > Gesendet: Dienstag, 9. April 2002 19:56 > > An: [EMAIL PROTECTED] > > Betreff: Tomcat intermittent failures > > > > exist, but when we attempt to access that particular JSP thru > > Apache, we get 404 - File Not Found. > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
