I upgraded to Tomcat 4.1.9 beta to see if that made a difference. I also changed my JDK from 1.4.1beta to 1.3.1. This didn't change anything. Then I found a post in the mailing list archives:
http://marc.theaimsgroup.com/?l=tomcat-user&m=102278697817471&w=2 Which suggested creating a temp directory in my catalina.base directory. So I tried this. Now I am past the JAR file errors. In fact, in the logfile there are no errors at all: 2002-08-21 15:04:33 StandardContext[/oemserver]: Starting filters 2002-08-21 15:04:33 timerservlet: init 2002-08-21 15:04:33 action: init 2002-08-21 15:04:33 StandardContext[/oemserver]: Starting completed 2002-08-21 15:04:33 HostConfig[localhost]: HostConfig: Processing START 2002-08-21 15:04:33 HostConfig[localhost]: Deploying discovered web applications 2002-08-21 15:04:33 HostConfig[localhost]: Starting background thread 2002-08-21 15:04:34 HostConfig[localhost]: BACKGROUND THREAD Starting 2002-08-21 15:04:49 HostConfig[localhost]: Deploying discovered web applications I see the output in console from my timerservlet so I know everything is OK there. I then try to access the URL: HTTP Status 404 - /oemserver/login.jsp ------------------------------------------------------------------------ -------- type Status report message /oemserver/login.jsp description The requested resource (/oemserver/login.jsp) is not available. ------------------------------------------------------------------------ -------- Apache Tomcat/4.1.9 I look in the log file: 2002-08-21 15:01:18 StandardHost[localhost]: Mapping request URI '/oemserver/login.jsp' 2002-08-21 15:01:18 StandardHost[localhost]: Trying the longest context path prefix 2002-08-21 15:01:18 StandardHost[localhost]: Mapped to context '/oemserver' 2002-08-21 15:01:18 Authenticator[/oemserver]: Security checking request GET /oemserver/login.jsp 2002-08-21 15:01:18 Authenticator[/oemserver]: Checking constraint 'SecurityConstraint[Test 1]' against GET /login.jsp --> false 2002-08-21 15:01:18 Authenticator[/oemserver]: No applicable constraint located 2002-08-21 15:01:18 Authenticator[/oemserver]: Not subject to any constraint 2002-08-21 15:01:18 StandardContext[/oemserver]: Mapping contextPath='/oemserver' with requestURI='/oemserver/login.jsp' and relativeURI='/login.jsp' 2002-08-21 15:01:18 StandardContext[/oemserver]: Trying exact match 2002-08-21 15:01:18 StandardContext[/oemserver]: Trying prefix match 2002-08-21 15:01:18 StandardContext[/oemserver]: Trying extension match 2002-08-21 15:01:18 StandardContext[/oemserver]: Trying default match2002-08-21 15:01:20 HostConfig[localhost]: Deploying discovered web applications This part is confusing: 2002-08-21 15:01:18 StandardContext[/oemserver]: Trying exact match 2002-08-21 15:01:18 StandardContext[/oemserver]: Trying prefix match 2002-08-21 15:01:18 StandardContext[/oemserver]: Trying extension match 2002-08-21 15:01:18 StandardContext[/oemserver]: Trying default match I don't know what that means. But overall, there are no errors and it does not work. At this point I'm convinced I've stumbled upon a bug. I appreciate any help you may have. Michael > -----Original Message----- > From: Michael [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, August 21, 2002 12:31 PM > To: 'Tomcat Users List' > Subject: RE : RE : Can someone explain catalina.home & catalina.base? > > > My web app directory is physically residing in > c:\idtect\projects\oemserver\web, which is what i defined in > the server.xml for the context docBase. I think the > catalina.base is set properly, because it is finding my > server.xml and tomcat-users.xml files, as well as it's > logging to the appropriate directory. It's just a problem > with the webapp context. > > And again, if I put catalina.base back to the tomcat install > directory and use the -config command line parameter to > specify my server.xml, it works fine. The reason this isn't > acceptable is because then it loads tomcat-users.xml from the > tomcat install directory. I suppose if I switch to JDBC > security I won't have this problem. ;) > > I think this may be a bug in Tomcat but it seems to be a > common thing to do so I'm suprised I'm the only one having > this problem. > > Michael > > > > -----Original Message----- > > From: Jhair Tocancipa Triana [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, August 21, 2002 11:52 AM > > To: Tomcat Users List > > Subject: Re: RE : Can someone explain catalina.home & catalina.base? > > > > > > -> Server.xml contains: > > > > -> <Context reloadable="true" debug="10" > > -> docBase="c:\idtect\projects\oemserver\web" > path="/oemserver" /> > > > > -> I then go to DOS and type: > > > > -> C:\>%CATALINA_HOME%\bin\startup Using CATALINA_BASE: > > -> c:\idtect\projects\oemserver\conf\tomcat Using CATALINA_HOME: > > -> c:\devapps\tomcat Using CATALINA_TMPDIR: > > -> c:\idtect\projects\oemserver\conf\tomcat\temp Using > JAVA_HOME: > > -> C:\devapps\j2sdk1.4.1 C:\> > > > > The documentation says ($CATALINA_HOME/Running.txt): > > > > " > > When you do this, Tomcat 4 will calculate all relative > > references for files in the following directories based on > > the value for CATALINA_BASE instead of > > CATALINA_HOME: > > * conf - Server configuration files (including server.xml) > > * logs - Log and output files > > * webapps - Automatically loaded web applications > > * work - Temporary working directories for web applications > > " > > > > Does your webapp reside on: > > "c:\idtect\projects\oemserver\conf\tomcat"? > > > > In your Context, docbase is defined as: > > > > "c:\idtect\projects\oemserver\web" > > > > Seems like CATALINA_BASE was not properly defined. > > > > Regards, > > > > -- > > --Jhair -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>