JNDI datasource context LifeCycleException

Question

Any help with this would be greatly appreciated. I'm trying to set up connection pooling in Tomcat 4.1.27 on Linux using MySQL. I followed the directions from Jakarta here http://jakarta.apache.org/tomcat/tomcat-4.1-doc/printer/jndi-datasource-examples-howto.html
And I put the mysql connector .jar file in Tomcat's common/lib directory.
However, when I start up Tomcat, my webapp doesn't load. There is no error message in the logs or on the console at startup. It just silently fails. Then when I shutdown Tomcat this error appears:
2003-10-17 11:31:12 StandardHost[localhost]: Removing web application at context path /budgetchallenge
2003-10-17 11:31:12 StandardHost[localhost]: ContainerBase.removeChild: stop:
LifecycleException:  Container StandardContext[/budgetchallenge] has not been started
        at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3644)
        at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036)
        at org.apache.catalina.core.StandardHostDeployer.remove(StandardHostDeployer.java:470)
etc...Here is the node in my web.xml per the directions...
    <resource-ref>
        <description>DB Connection</description>
        <res-ref-name>jdbc/budgetchallenge</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <res-auth>Container</res-auth>
    </resource-ref>Here is the setup in the server.xml...
<Context path="/budgetchallenge" docBase="budgetchallenge"
        debug="5" reloadable="true" crossContext="true">
  <Logger className="org.apache.catalina.logger.FileLogger"
             prefix="localhost_budgetchallenge_log." suffix=".txt"
             timestamp="true"/>
  <Resource name="jdbc/budgetchallenge"
               auth="Container"
               type="javax.sql.DataSource"/>
  <ResourceParams name="jdbc/budgetchallenge">
    <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>...</value>
    </parameter>
    <parameter>
     <name>password</name>
     <value>...</value>
    </parameter>
    <!-- Class name for mm.mysql JDBC 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://10.1.1.45:3306/budgetsurvey_02</value>
    </parameter>
  </ResourceParams>
</Context>

Answer 1

Yeah, I've got those all set up.
However, now the application is working, connecting to the DB and everything. The problem was that the deployed .war file was not expanding. The JNDI context specifies and directory with the app name, but there was none because the .war file was not expanded as it usually is automatically in Tomcat.
So I manually expanded it and now the app works. However, I'd like to know why the .war archive was not being automatically expanded.
Ethan