You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/01/14 18:48:03 UTC
DO NOT REPLY [Bug 5843] New: -
Web application installed with Tomcat manager is lost after shutdown when using unpackWARs = false.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5843>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5843
Web application installed with Tomcat manager is lost after shutdown when using unpackWARs = false.
Summary: Web application installed with Tomcat manager is lost
after shutdown when using unpackWARs = false.
Product: Tomcat 4
Version: 4.0.1 Final
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: jonathan_ramsey@bristol-city.gov.uk
I found this problem while I was trying to work around the bugzilla bug id =
5680. Part of the work around I was trying involved turning off unpacking of
WAR files, (unpackWARs="false") for the Host defined in my server.xml file.
I expected to be able to:
- install a web application using the Tomcat 4 manager from a local war file.
- shutdown Tomcat 4
- startup Tomcat 4
- have the web application available (running) again.
The problem is:
- I found that after startup, Tomcat 4 'forgets' that the web application was
installed.
I have repeated the procedure with 3 different web applications - each time
with the same result.
I have included full steps to reproduce this problem below.
1. Single virtual host defined in server.xml file. Set unpackWARs flag to false
so Tomcat doesn't unpack WAR files.
<Host name="localhost" debug="0" appBase="webapps" unpackWARs="false">
2. work directory contains no files before startup.
3. webapps directory contains only 1 web application (manager).
manager
-- WEB-INF
---- web.xml
4. Startup tomcat.
5. manager application (http://localhost/manager/list) shows the following web
applications.
OK - Listed applications for virtual host localhost
/manager:running:0
6. install NewW3Menu application (http://localhost/manager/install?
path=/NewW3Menu&war=jar:file:/home/user/NewW3Menu.war!/).
OK - Installed application at context path /NewW3Menu
7. work directory contains:
localhost
-- NewW3Menu
---- WEB-INF
------ classes
-------- log4j.xml
-------- uk
---------- gov
------------ bristol_city
-------------- w3menu
---------------- ControllerServlet.class
---------------- MenuGraphicsPage.class
---------------- TopGraphicsPage.class
---------------- frame_graphics.class
---------------- menu_text.class
---------------- top_touchscreen.class
---------------- FrameGraphicsPage.class
---------------- MenuTextPage.class
---------------- TopMinimisedPage.class
---------------- frame_minimised.class
---------------- menu_touchscreen.class
---------------- FrameMinimisedPage.class
---------------- MenuTouchscreenPage.class
---------------- TopTouchscreenPage.class
---------------- frame_touchscreen.class
---------------- top_graphics.class
---------------- FrameTouchscreenPage.class
---------------- Page.class
---------------- UrlOps.class
---------------- menu_graphics.class
---------------- top_minimised.class
------ lib
-------- ChainedException_classes.jar
-------- Tools_classes.jar
-------- hsql.jar
-------- log4j.jar
-------- servlet.jar
-------- xerces.jar
-------- StandardServlet_classes.jar
-------- adabasd.jar
-------- jdbc2_0-stdext.jar
-------- poolman.jar
-------- w3m_classes.jar
-------- xmlc.jar
-- manager
8. webapps directory still contains only 1 web application (manager).
manager
-- WEB-INF
---- web.xml
9. When the application is called from a web browser, it works.
10. Tomcat is shutdown.
11. In the work directory, two files have been added (SESSIONS.ser).
localhost
-- NewW3Menu
---- SESSIONS.ser
-- manager
---- SESSIONS.ser
12. Tomcat is started up.
13. Manager application (http://localhost/manager/list) shows that NewW3Menu
application is no longer running.
OK - Listed applications for virtual host localhost
/manager:running:0
13. Attempt to call NewW3Menu web application returns the following error:
HTTP Status 500 - No Context configured to process this request
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>