Hi:
Are you creating the ".WAR" on one machine then copying it to a server on
another machine? If so, then check that the clocks on the two machines are
set to the same time. I've had problems where my compile-machine's clock
was running a little slow, which made the ".WAR" file appear to be older
than the already-unpacked directory. In this case, Tomcat figures you've
modified the existing directory, so it doesn't unpack the new one.
Greg Trasuk, President
StratusCom Manufacturing Systems Inc. - We use information technology to
solve business problems on your plant floor.
http://stratuscom.ca
> -----Original Message-----
> From: Sergey V. Udaltsov [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 22, 2001 5:31 PM
> To: [EMAIL PROTECTED]
> Subject: Tomcat 4.0.1 not updating the webapp
>
>
> Hi all
>
> I took 4.0.1 and have the same problem with the updating of webapps. I
> install my webapp using the manager/install?... and remove using
> manager/remove?... Everything is fine. Then I install the new version
> from the same war file (definitely, new version of it), get
> "OK", and in
> the browser I still see the same _old_ content. It's not browser's
> fault, I am sure (checked with lynx and "telnet localhost
> 80"). It seems
> that tomcat keeps in memory the old content of classes and jsps. Is
> there a way to overcome this?
> BTW, in the webapps directory the content is old too.:( Any help would
> be appreciated.
>
> Thanks is advance,
>
> Sergey
>
>