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 16762] New: - Can't set my app as root app without errors
Date Tue, 04 Feb 2003 16:07:54 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16762>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16762

Can't set my app as root app without errors

           Summary: Can't set my app as root app without errors
           Product: Tomcat 4
           Version: 4.1.18
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: matt@raibledesigns.com


I can't seem to set my application (cct) as the root application for Tomcat.  If
I use <Context path="" ...>, my app appears to load fine, but then Tomcat seems
to attempt to load it a second time, and I get the following error:

WARN [main] JDBCExceptionReporter.logExceptions(35) | SQL Error: 0, SQLState: null
ERROR [main] JDBCExceptionReporter.logExceptions(42) | Cannot load JDBC driver
class 'null'
WARN [main] SessionFactoryImpl.<init>(163) | Could not obtain connection metadata
java.sql.SQLException: Cannot load JDBC driver class 'null'

>From this, I assumed that Tomcat was trying to load my app both at the root
context path ("") and a context path that's the same as the directory ("/cct").
 So I created a second xml file in webapps, and named it cct2.xml and changed
the path to "/cct".  I don't get the error above, but the app does indeed load
twice.  I was hoping I could turn off this load-the-second-one behavior by
changing unpackWARs and/or autoDeploy to false on my <Host> element, but no such
luck.  Is there a way to fix this?

I can successfully use the app at http://localhost/, but I'd rather not see
these errors, and I'd rather not see it load twice.  

I'm using Tomcat 4.1.18, JDK 1.4.1_01 on Win2K and RedHat 8.0.

One workaround I found was to change the name of my app's directory to ROOT and
use that as the path for my context.  

Is this expected/anticipated behavior?

---------------------------------------------------------------------
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