I have had a similar problem today (for the first time).
After modifying a .jsp page, I couldn't see the new version on the browser, so I
deleted the entire work directory for that wepapp, and I was still watching the
old version of the page (of course the .java and .class files re-generated).
When I finally restarted tomcat I could see the new version of the page.
Config: Tomcat 3.1 (standalone) / WinNT 4 sp6
bye.
diego.
____________________Reply Separator____________________
Subject: RE: BIZZAR Caching Problem !!
Author: [EMAIL PROTECTED]
Date: 26/01/2001 6:51 PM
What happens if you rm -rf all directories under tomcat/work? Just to
make sure that nothing wacky is going on because of your <host> tag.
Also, do you have a
<%@ include file= ... %>
or a
<jsp: include page= ... />
directive? Sounds like you have <%@, but just want to make sure.
And the content of a.inc and b.inc is distinct, correct? :)
j\s
-----Original Message-----
From: Shahed Ali [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 26, 2001 12:21 PM
To: [EMAIL PROTECTED]
Subject: Re: BIZZAR Caching Problem !!
Yes,
Your sequence of events is correct.
The .jsp and work directories are local.
And restarting tomcat solved the problem.
There are a few things though.
The server.xml is configured with my app setup under a <host> tag.
the directory refered to by server.xml as docBase is a symbolic link to
aonther dir on the same server.
Regards
Shahed
>>Now, you are saying that the newly generated .java file refers to
a.inc?
>>Perhaps tomcat is de-compiling the .java from the class in memory :)
>>Are your .jsp files mounted over NFS or any other remote file system?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
