tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Tanner <rtan...@linfield.edu>
Subject Re: Problem deploying existing webapp in new Tomcat container
Date Thu, 17 May 2007 18:14:00 GMT
I also found this log, and I assume it's related to the problem:

WARNING: A docBase /var/apache/apache-tomcat-6.0.13/webapps/GroupAliases
inside the host appBase has been specified, and will be ignored


You can see in the dump of mailtools#aliases.xml that indeed I do
specify a docBase.  In Tomcat 4 that was correct but now that's wrong?? 
Makes no sense.

-- Rob


Rob Tanner said the following on 05/17/2007 10:09 AM:
> Since it's your favorite subject...   :-)
>
> Following the directions in the context.html doc (the fisrt URL
> below), and not changing the default values for engine and host, the
> first thing I did was to add the path
> ${CATALINA_HOME}/conf/Catalina/localhost.  I created one xml file
> named: mailtools#aliases.xml since the context path is multi-level
> (the path is "/mailtools/aliases" -- I presume that's what was meant
> by multi-level in the doc) for the first webapp and accntManager.xml
> for the seconf app.
>
> The first app (mailtools#aliases.xml) still continues to fail as below:
>
> SEVERE: Allocate exception for servlet GroupAliasManager
> javax.servlet.ServletException: Error instantiating servlet class
> GroupAliasManager
>         at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1127)
>         at
> org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
>         at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
>         at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
>         at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
>         at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>         at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
>         at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
>         at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
>         at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:595)
>
> The second app, that was working properly when I configured it's
> context in server.xml now fails to load:
>
> java.lang.IllegalArgumentException: Document base
> /var/apache/apache-tomcat-6.0.13/webapps/accntManager does not exist
> or is not a readable directory. 
>
> The specified docBase is AccountManager not accntManager.  The latter
> is the context path.  Although, when I rename the actual directory
> "accntManager" it works.  It clearly misreading something which tells
> me that I'm clearly misunderstanding something.
>
> Here are the two files:
>
> <Context crossContext="true" debug="0"
>        docBase="AccountManager" path="/accntManager" reloadable="true">
>        <Logger className="org.apache.catalina.logger.FileLogger"
>                      prefix="localhost_accntmanager_log." suffix=".txt"
>               timestamp="true"/>
> </Context>
> ::::::::::::::
> mailtools#aliases.xml
> ::::::::::::::
> <Context crossContext="true" debug="0"
>        docBase="GroupAliases" path="/mailtools/aliases" reloadable="true">
>        <Logger className="org.apache.catalina.logger.FileLogger"
>                      prefix="localhost_aliases_log." suffix=".txt"
>               timestamp="true"/>
> </Context>
>
> Thanks,
> Rob
>
>
> Caldarale, Charles R said the following on 05/16/2007 03:19 PM:
>>> From: Rob Tanner [mailto:rtanner@linfield.edu] 
>>> Subject: Re: Problem deploying existing webapp in new Tomcat container
>>>     
>>  
>>   
>>> As far as server.xml, how else does one specify the specifics, such as
>>>     
>> the path variable? 
>>  
>> (Here we go again... my favorite subject :-)
>>  
>> First, read the doc:
>> http://tomcat.apache.org/tomcat-6.0-doc/config/context.html
>>  
>> Note the following extracts from the Introduction and the description of
>> the path attribute:
>>  
>> "For Tomcat 6, unlike Tomcat 4.x, it is NOT recommended to place
>> <Context> elements directly in the server.xml file. This is because it
>> makes modifing the Context configuration more invasive since the main
>> conf/server.xml file cannot be reloaded without restarting Tomcat."
>>  
>> "The value of this field must not be set except when statically defining
>> a Context in server.xml, as it will be inferred from the filenames used
>> for either the .xml context file or the docBase."
>>  
>> Nor should you be specifying a docBase. Put the <Context> elements where
>> they belong - in META-INF/context.xml of each webapp - and remove the
>> path and docBase attributes.
>>  
>> Also, reading this part of the doc:
>> http://tomcat.apache.org/tomcat-6.0-doc/logging.html
>>  
>> would show you that the <Logger> element is no longer used.
>>  
>>  - Chuck
>>  
>>
>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
>> MATERIAL and is thus for use only by the intended recipient. If you
>> received this in error, please contact the sender and delete the e-mail
>> and its attachments from all computers.
>>
>>  
>>
>>
>>   
>
> -- 
> Rob Tanner
> UNIX Services Manager
> Linfield College, McMinnville OR


Mime
View raw message