tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 30462] New: - deploying war with META-INF/context.xml included results in error
Date Wed, 04 Aug 2004 12:39:16 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30462>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30462

deploying war with META-INF/context.xml included results in error

           Summary: deploying war with META-INF/context.xml included results
                    in error
           Product: Tomcat 5
           Version: 5.0.27
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: rbetjes@ecomsulting.nl


Deploying a war file (by dropping it in de webapps dir) called test.war witch
includes an context.xml file in a dir called META-INF, results in directory
called test.xml created in the conf/Catalina/localhost/ directory.
The war file is correctly unpacked in the webapps dir.

Next the server reports an error in the catalina.out log like:

Aug 4, 2004 1:16:46 PM org.apache.catalina.startup.HostConfig deployDescriptors
SEVERE: Error deploying configuration descriptor test.xml
java.io.IOException: java.io.FileNotFoundException:
/usr2/app/apache/jakarta-tomcat-5.0.27/conf/Catalina/localhost/test.xml (Is a
directory)
        at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:494)
        at org.apache.catalina.core.StandardHost.install(StandardHost.java:863)
        at
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:482)
        at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:427)
        at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1068)
        at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:327)
        at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
        at
org.apache.catalina.core.StandardHost.backgroundProcess(StandardHost.java:800)
        at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1619)
        at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1628)
        at
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1608)
        at java.lang.Thread.run(Thread.java:536)

A workaround forr the moment is to remove the faulty directory and manually
copying the correct context.xml file from de unpacked webapp to the
conf/Catalina/localhost/ directory and calling it test.xml

success,

Robin Betjes, 
Ecomsulting B.V.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message