tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert L Sowders" <rsowd...@usgs.gov>
Subject Re: New context in server.xml prevents war unpacking (TC 4.1.12)
Date Fri, 25 Oct 2002 04:27:32 GMT
I believe the reloadable="true" statement refers to reloading currently 
deployed webapps that have changed in some way and not to "deploying" 
webapps.

So if you want to customize your context for your database you can either 
auto-deploy in the webapp directory then customize your context and 
restart Tomcat or make your own context and deploy your webapp yourself 
into the docbase you specified.  In either case the docbase will have to 
exist when Tomcat reads the server.xml file.  If not you get the error.

rls





Ken Pelletier <ken@nika.com>
10/24/2002 07:40 PM
Please respond to "Tomcat Users List"

 
        To:     Tomcat List <tomcat-user@jakarta.apache.org>
        cc: 
        Subject:        New context in server.xml prevents war unpacking (TC 4.1.12)

I recently added a new context to server.xml so that I can set up a 
database
connection pool resource for my webapp.

The webapp was deploying/running well prior to adding this context.

With the context added, starting Tomcat produces an error for that app 
context:

java.lang.IllegalArgumentException: Document base 
/usr/local/tomcat/webapps/myapp does not exist or is not a readable 
directory
         at 
org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.jav 
a:193)

This suggests that docBase directory is expected to exist at start. 
Without that context in server.xml, the war unpacks and
creates its directory.

The context looks like this:

                 <Context path="/myapp" docBase="myapp"
                   reloadable="true" crossContext="true>
                 ... resources here ...
                 </Context>

If I change the docBase to "myapp.war", the application loads and runs 
properly, db conn pooling works a treat, BUT
the war isn't unpacked at all.

The behavior I want is to have the war get unpacked ( as it was before 
) so that I can serve some of the static content
directly from Apache httpd, but still package/deliver/deploy the webapp 
as a war to Tomcat.

Any thoughts as to why this is happening / how to solve?

Thanks.

- Ken


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>





--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message