Not sure why. I never try twisted experiments like this. :-)

I typically remove the context using the admin application, rather than the manager application. If I remove the .war file from the web apps folder, I also delete the unpacked war folder in both the webapps and _work folders. Subsequently deploying a .war file to the webapps folder has always worked fine.

At 17:51 2003-02-04 -0600, you wrote:
No one is going to byte ha?

-----Original Message-----
From: Jim Henderson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 3:47 PM
To: [EMAIL PROTECTED]
Subject: Tomcat Manager/Administrator and server.xml file.


Can someone confirm the following observations (Tomcat 4.1.18 under Win2K
and JDK 1.4.1)?

Given: an application is deployed by copying is WAR file to the webapps
directory and Tomcat is started. (server.xml file is out-of-the-box content,
no modifications.)

Then, by using Tomcat Administrator to interrogate the application
environment and resources, Tomcat Administrator will insert the application
items into the server.xml file where a context for the application had not
existed before (must click on commit changes).

When using Tomcat Manager to �remove� the application, the application is
stopped and removed from Tomcats Administrator and Manager WEB pages.
However, the application war file is not deleted from the webapps directory,
the application is not removed from the work directory, nor is the
application�s context removed from the server.xml file. In fact, if Tomcat
is shutdown and restated, the application is alive and well.

If you re-deploy the application (when Tomcat is not running) by copying the
WAR file to the webapps directory and deleting the work directory, then
starting Tomcat, the application will fail. This is due to the server.xml
file still having a context entry from above. One must stop Tomcat, edit
the server.xml file and remove the context entry, delete the work file for
the application to successfully restart.

And, one more question, why does the application fail if the server.xml file
have a context entry when the application is re-deployed (failure snippet
below)?


2003-02-04 15:36:32 StandardContext[/mfnettags]: Resources start failed:
2003-02-04 15:36:32 StandardContext[/mfnettags]: Context startup failed due
to previous errors
2003-02-04 15:36:32 StandardContext[/mfnettags]: Exception during cleanup
after start failed
LifecycleException: Container StandardContext[/mfnettags] has not been
started
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643)



Am I correct in the above?

Thanks.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Sean Dockery
[EMAIL PROTECTED]
Certified Java Web Component Developer
Certified Delphi Programmer
SBD Consultants
http://www.sbdconsultants.com



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to