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 2001/09/14 17:13:04 UTC

DO NOT REPLY [Bug 3614] New: - bug in manager webapp

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