Bug 22149 - Reloading with manager causes application to break
Summary: Reloading with manager causes application to break
Status: RESOLVED DUPLICATE of bug 22096
Alias: None
Product: Tomcat 4
Classification: Unclassified
Component: Webapps:Manager (show other bugs)
Version: 4.1.27
Hardware: Other other
: P3 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-05 20:28 UTC by Mike Bradford
Modified: 2004-11-16 19:05 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Bradford 2003-08-05 20:28:20 UTC 
Using the HTML Manager, Tomcat 4.1.27 on SuSE Linux (I haven't tested this on
any other OS's). When Tomcat first starts up, all the webapps (including
/examples, which I've been testing with) start up fine. When I click 'reload' to
reload the /examples webapp, the manager claims it is not running (false). When
I hit 'Start' I get:

FAIL - Application at context path /examples could not be started
FAIL - Encountered exception java.lang.IllegalStateException: standardHost.start
/examples: LifecycleException:  Container StandardContext[/examples] has already
been started

Which is quite obviously not true, since when I try to access /examples I get

HTTP Status 503 - This application is not currently available

The only way to bring /examples back is to shutdown.sh then startup.sh.

I'm posting this under the manager, although I'm not sure whether the problem
lies there or not; I tried moving the manager webapp from 4.1.24
(tomcat_home/server/webapps/manager) into 4.1.27 and had the same problem.

Using Sun JDK 1.4.1_03. I've tried this on 3 systems (different versions of
SuSE) and all three show the same problem. This problem doesn't exist in Tomcat
4.1.24.
Comment 1 Tim Funk 2003-08-05 21:13:16 UTC 
This is a duplicate and I this is fixed for the next build. 
http://www.apache.org/dist/jakarta/tomcat-4/binaries/

*** This bug has been marked as a duplicate of 22096 ***