"Sekar, Vasanth" <vasanth.se...@supervalu.com> wrote:
> >> All evidence at the moment indicates that your JSP code is the most >> likely suspect. >Okay, I will scan through the logic in the code once again very >closely. A better idea would be to create the simplest possible JSP that reproduces the issue and then show us the JSP source code. >Like I said before the same code works fine in JRUN and also in Tomcat >for the first time. This problem occurs only in Tomcat upon subsequent >access. If I get rid of the jsp_java then in work/catalina then it >would >start working again properly. So, I was under the impression that some >kind of a cache problem. That sounds more like a JSP source code problem where something is resolved at compile time rather than run time. >> And again, at least trying it on a current version would either >> confirm or eliminate the possibility that the problem has been fixed sometime >> in the past four years (if it is a Tomcat problem). >Sure, I will try to download the latest version and give it a shot to >see if the problem manifests in there. Sorry, did not interpret from >your original response that you want me to try in latest Tomcat >version. >I have no problems in doing so and am not against it. It is just that I >was trying to explain the reasons for this particular version usage. >PS: Hoping that I am not asking any questions on a version that is EOL. No, 6.0.x is still supported but if this is a Tomcat bug it will be fixed by another 6.0.x release so you'd have to upgrade anyway. >Lastly, I am not trying to be irresponsible or willing to post >ill-described questions:( Just thought of getting some experts advise >here and no other intentions:) Then you need to provide the information requests - such as the JSP source code. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
