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=13833>. 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=13833 Webapp install/start failures not reported by Deployer install operation Summary: Webapp install/start failures not reported by Deployer install operation Product: Tomcat 4 Version: 4.0.4 Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] To programmatically install a webapp at runtime, the Deployer interface is used. StandardHost implements this interface. According to its install() documentation, "if this application is successfully installed, a ContainerEvent of type INSTALL_EVENT will be sent to all registered listeners." If a webapp tries to get installed/started that is invalid (e.g., contains a malformed web.xml file), during the StandardContext Lifecycle start() operation, Tomcat knows that it cannot configure the context. In such a case, it automatically tries to stop the context and marks it unavailable. However, the problem is that StandardContext start() fails to alert the caller that the operation failed. Thus, the install operation succeeds and the caller is notified with a [successful] INSTALL_EVENT. Furthermore, the unavailable/invalid context object gets added to the container hierarchy leading to invalid state if/when it tries to get uninstalled. To fix this problem, StandardContext start() should throw a LifecycleException when it marks the context as unavailable. (I haven't checked whether or not this bug also exists in Tomcat 4.1.x.) -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
