tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Kjome <>
Subject Re: Tomcat 4.1.12 unpackWARs
Date Thu, 10 Oct 2002 03:42:46 GMT

This is intended behavior based on Tomcat's documentation.  There is a bug 
on this.  Don't have the bug number handy.  Search and search for it.  I'm not sure I agree 
with the behavior either, but that's the way it is for now.


At 05:23 PM 10/9/2002 -0500, you wrote:
>I found some hint of this in past archives, and am wondering if this is a
>bug or if I am missing something.
>The following will not unpack a .war file existing in the appBase directory.
>Tomcat processes will start and then quickly die because according to the
>log messages generated, the docBase directory doesn't (yet) exist, which is
>true since the .war didn't first expand:
>   <Engine className="org.apache.catalina.connector.warp.WarpEngine"
>           name="Tomcat-Apache Engine" debug="0">
>   <Host name="localhost" debug="9" appBase="webapps" autoDeploy="true"
>      <Realm className="org.apache.catalina.realm.MemoryRealm" />
>      <Context path="/testapp" docBase="testapp" reloadable="true"
>privileged="true" debug="1" />
>   </Host>
>  </Engine>
>It will unpack correctly if no context is specified, and it will work as
>shown above if the docBase directory is already unpacked.  This will also
>work if I set unpackWARs to "false", and the docBase to the war file, but I
>really need the war to be expanded in this case.
>Is there a work-around for this behavior, other than manually unpacking?  My
>environment is SuSE Linux 8.0, Apache 1.3.26, Tomcat 4.1.12.
>To unsubscribe, e-mail:   <>
>For additional commands, e-mail: <>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message