I had a quick go at this like you probably did with something simple, and there
is certainly no web application reload in this circumstance.
The web application in question is configured with JNDI datasources and log4j.
The architecture of the application uses Struts and Tiles for JSPs. I think I
am going to have to try to take copy of the application and work it backwards
to see where/what causes the Tomcat web app reload.
We use Ant to build the web application. For development JSPs this is a simple
copy to the web app folder. For classes, they are compiled. Static resources
and config files are also copied.
I had the issue in question all day today. All I was doing was making textual
changes to a JSP. I used Ant to copy them across (which we have been doing
since April 2004) and then made a request to a Struts action (which then return
the JSP in question). A white page is shown (or partial HTML page). Looking in
stdout, you can see the web application has been reinitialised. The Ant build
output shows no compilation of classes, so the reloadable aspect of Tomcat
should not in my view be triggered.
Thinking about it harder, I can say with 85% surity that this started happening
with around 5.5.4 (since I always upgrade our test server on the day of a new
Tomcat release).
I don't know what else to add really at this point. I will perform some further
tests tomorrow to narrow it down if I can, but this is an issue with
*something*, it's just finding out where. It could be as simple as Ant is
touching class files when it should not (which it never used to so I doubt it)
or it could be something in Tomcat but I would not know what/why.
Will let you know if I find any more hard links to what causes the issue.
Allistair.
-----Original Message-----
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Tue 14/12/2004 17:07
To: Tomcat Developers List
Cc:
Subject: Re: JSP changes cause web app reload in 5.5?
Allistair Crossley wrote:
>Myself and my developers have noticed that with our new 5.5
development Tomcats changes to JSPs now cause Tomcat to reload our web
applications.
>
>
I cannot reproduce this.
>Is this expected behaviour? Perhaps the new JDT compiler? Can it be
stopped without using reloadable="false"? We don't use anti JAR locking either.
>
>
You have a vivid imagination. What else ?
RÃmy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE>
-------------------------------------------------------
QAS Ltd.
Developers of QuickAddress Software
<a href="http://www.qas.com";>www.qas.com</a>
Registered in England: No 2582055
Registered in Australia: No 082 851 474
-------------------------------------------------------
</FONT>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
