DO NOT REPLY [Bug 4422] New: - Warp connector and non existing WebApps

[bugzilla]

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

Warp connector and non existing WebApps

           Summary: Warp connector and non existing WebApps
           Product: Tomcat 4
           Version: 4.0.1 Final
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Connectors
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


I am not exactly sure whether this belongs under Catalina or Connectors but 
connectors seem as a better choice:

Apache web server:
Stock RH7.1 install
Server version: Apache/1.3.19 (Unix)  (Red-Hat/Linux)
Server built:   Mar 29 2001 12:52:37

With mod_webapp.so compiled from sources for 4.0.1 release of tomcat:

WebAppConnection catalina1 warp localhost:8008
WebAppDeploy portal catalina1 /portal

When trying to access /portal through apache it inifinatly tries to connect to 
portal application.

Apache's log file gets filled with many lines of the following text:
[Thu Oct 25 10:54:36 2001] [error] Cannot deploy application portal

And tomcat's log for Warp connector is being filled with many lines like: 

2001-10-25 10:54:36 
[org.apache.catalina.connector.warp.WarpConfigurationHandler] Cannot 
find "/usr/local/tomcat/production/webapps/portal" for appl. "portal" 
host "edas1"
2001-10-25 10:54:36 
[org.apache.catalina.connector.warp.WarpConfigurationHandler] Error deploying 
web application "portal" under <http://edas1:80/portal/>
2001-10-25 10:54:36 [org.apache.catalina.connector.warp.WarpConnection] 
Exception on socket
java.io.IOException: Broken pipe
        at java.net.SocketOutputStream.socketWrite(Native Method)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:62)
        at org.apache.catalina.connector.warp.WarpConnection.send
(WarpConnection.java:220)
        at org.apache.catalina.connector.warp.WarpConfigurationHandler.handle
(WarpConfigurationHandler.java:127)
        at org.apache.catalina.connector.warp.WarpConnection.run
(WarpConnection.java:189)
        at java.lang.Thread.run(Thread.java:484)

Although this is caused by user configuration error, I still think it can be 
handled more gracefully.

Thank you,
Vlad B.