Return-Path: 
 <tomcat-dev-return-27687-apmail-jakarta-tomcat-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org
Received: (qmail 17079 invoked by uid 500); 14 Sep 2001 15:13:03 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:tomcat-dev-help@jakarta.apache.org>
list-unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
list-post: <mailto:tomcat-dev@jakarta.apache.org>
Reply-To: tomcat-dev@jakarta.apache.org
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 17070 invoked from network); 14 Sep 2001 15:13:02 -0000
Date: 14 Sep 2001 15:13:04 -0000
Message-ID: <20010914151304.2786.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 3614] New:  -
    bug in manager webapp
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

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=3614>.
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=3614

           Summary: bug in manager webapp
           Product: Tomcat 4
           Version: 4.0 Release Candidate 1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: account.consult-smi@airbus.fr


As long as a webapplication behaves well, the manager application does so too.
If however I try to reload a webapp and this operation doesn't succeed due to 
some error then the webapp is marked as unavailable (which is correct), but the 
manager application confuses the webapp-lifecycle-state: 

On the HTML page I would then have the following situation:
- the reload link is not shown
- the webapp state is displayed as "stopped"
- the "start" link is active

I can therefore only choose "start", but if I do, then the manager reports the 
following lifecycle exception:
FAIL - Encountered exception java.lang.IllegalStateException: 
standardHost.start /<webapp-path>: LifecycleException: Container StandardContext
[/<webapp-path>] has already been started