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

org.apache.catalina.core.StandardHostDeployer.install creates webappname.xml from 
META-INF/context.xml as a _directory_ and not a file

           Summary: org.apache.catalina.core.StandardHostDeployer.install
                    creates webappname.xml from META-INF/context.xml as a
                    _directory_ and not a file
           Product: Tomcat 5
           Version: Unknown
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Webapps:Administration
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Our program is called 'SONAR' so I have a sonar.war file with META-INF/context.
xml. Upon deployment, a _directory_  is created here:

  $CATALINA_HOME/conf/Catalina/localhost/sonar.xml/
                                         ^^^^^^^^^

If I remove this directory and replace it with a file of the same name (sonar.
xml) containing what I have in META-INF/context.xml, everything works happily. 
That is, if, after deployment, I execute:

  $ rm -r $CATALINA_HOME/conf/Catalina/localhost/sonar.xml
  $ cp $CATALINA_HOME/webapps/sonar/META-INF/context.xml 
       $CATALINA_HOME/conf/Catalina/localhost/sonar.xml

(And reload the web app using the Manager page.)

Then everything works. Until I do this, I have the following error, seen in 
$CATALINA_HOME/logs/catalina.out:

Jul 22, 2004 10:31:46 AM org.apache.catalina.core.StandardHostDeployer remove
INFO: Removing web application at context path /sonar
Jul 22, 2004 10:31:46 AM org.apache.catalina.core.StandardHostDeployer install
INFO: Processing Context configuration file URL file:
/home/greg/jakarta-tomcat-5.0.27/conf/Catalina/localhost/sonar.xml
Jul 22, 2004 10:31:46 AM org.apache.catalina.startup.HostConfig 
deployDescriptors
SEVERE: Error deploying configuration descriptor sonar.xml
java.io.IOException: java.io.FileNotFoundException: /home/greg/jakarta-tomcat-5.
0.27/conf/Catalina/localhost/sonar.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:534)


This is the contents of my context.xml file:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- Context for Pooled connections to SONAR MySQL database -->
<Context path="/sonar"
    docBase=""
    debug="5"
    reloadable="true">

    <Logger className="org.apache.catalina.logger.FileLogger"
        prefix="localhost_sonar_log."
        suffix=".txt"
        timestamp="true"/>

    <Valve className="org.apache.catalina.valves.AccessLogValve"
        directory="logs"
        prefix="localhost_sonar_access_log."
        suffix=".txt"
        pattern="common"
        resolveHosts="false"/>

    <!-- The MySQL database -->

    <Resource name="jdbc/sonarDB"
        auth="Container"
        type="javax.sql.DataSource"/>

    <ResourceParams name="jdbc/sonarDB">
        <parameter>
                <name>factory</name>
                <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
        </parameter>

        <!-- Maximum number of dB connections in pool. Make sure you
             configure your mysqld max_connections large enough to handle
             all of your db connections. Set to 0 for no limit. -->
        <parameter>
            <name>maxActive</name>
            <value>100</value>
        </parameter>

        <!-- Maximum number of idle dB connections to retain in pool.
             Set to 0 for no limit. -->
        <parameter>
            <name>maxIdle</name>
            <value>30</value>
        </parameter>

        <!-- Maximum time to wait for a dB connection to become
             available in ms, in this example 10 seconds. An
             Exception is thrown if this timeout is exceeded.
             Set to -1 to wait indefinitely. -->
        <parameter>
            <name>maxWait</name>
            <value>10000</value>
        </parameter>

        <!-- MySQL dB username and password for dB connections  -->
        <parameter>
            <name>username</name>
            <value>xxx</value>
        </parameter>
        <parameter>
            <name>password</name>
            <value>xxx</value>
        </parameter>

        <!-- Class name for the official MySQL Connector/J driver -->
        <parameter>
            <name>driverClassName</name>
            <value>com.mysql.jdbc.Driver</value>
        </parameter>

        <!-- The JDBC connection url for connecting to your MySQL dB.
             The autoReconnect=true argument to the url makes sure that
             the mm.mysql JDBC Driver will automatically reconnect if
             mysqld closed the connection.  mysqld by default closes
             idle connections after 8 hours. -->
        <parameter>
            <name>url</name>
            <value>jdbc:mysql://xxx/sonar?autoReconnect=true</value>
        </parameter>

        <!-- When available db connections run low DBCP will
             recover and recyle any abandoned dB connections it
             finds. -->
        <parameter>
            <name>removeAbandoned</name>
            <value>true</value>
        </parameter>

        <!-- Use the removeAbandonedTimeout parameter to set the
             number of seconds a dB connection has been idle
             before it is considered abandoned. -->
        <parameter>
            <name>removeAbandonedTimeout</name>
            <value>60</value>
        </parameter>

        <!-- The logAbandoned parameter can be set to true if
             you want DBCP to log a stack trace of the code
             which abandoned the dB connection resources. -->
        <parameter>
            <name>logAbandoned</name>
            <value>true</value>
        </parameter>
    </ResourceParams>
</Context>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to