[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] Tomcat - doesn't work: either enterstight loop or 404's
- Subject: Re: [cobalt-developers] Tomcat - doesn't work: either enterstight loop or 404's
- From: "Adam Thompson" <adamt@xxxxxxxxxx>
- Date: Thu Jul 12 08:43:53 2001
- Organization: Qunara
- List-id: Discussion Forum for developers on Cobalt Networks products <cobalt-developers.list.cobalt.com>
> 1) Case sensitivity - i.e. Using http://ABC.com/servlet/blahServlet
instead
> of http://abc.com/servlet/blahServlet
>
> 2) DNS aliases - if there's a DNS alias for www.abc.com that is
www.xyz.com
> and you try to access the servlet as www.xyz.com. Or, even abc.com
instead
> of www.abc.com probably won't work.
>
> To see if this is the problem, access the site by IP address. Hope
this
> helps.
OK, that took care of serving servlets off the main site
(/home/sites/home/web/WEB-INF). Thanks!
I'm still getting Tomcat-generated 404 errors for other sites, though.
I have /home/sites/site1/web/WEB-INF/classes/HelloWorld.class, the
auto-generated server.xml file has the following near the end:
<Host name="test.benmoss.com">
<Context path="" docBase="/home/sites/site1/web" debug="0"/>
<Context path="/examples" docBase="/home/sites/site1/web/examples"
reloadable="true" debug="0"/>
</Host>
<Host name="205.200.36.57">
<Context path="" docBase="/home/sites/site1/web" debug="0"/>
<Context path="/examples" docBase="/home/sites/site1/web/examples"
reloadable="true" debug="0"/>
</Host>
The second context path is present because I placed the "examples.war"
file in .../web. I can run servlets in examples.war, but I cannot run
anything at the site level.
Any more ideas?
Thanks.
-Adam Thompson
Qunara
adamt@xxxxxxxxxx
(204) 925-3256 - office
(204) 932-0069 - fax
----- Original Message -----
From: "Timothy Stonis" <timothy.stonis@xxxxxxx>
To: <cobalt-developers@xxxxxxxxxxxxxxx>
Sent: Thursday, July 12, 2001 1:35 PM
Subject: Re: [cobalt-developers] Tomcat - doesn't work: either
enterstight loop or 404's
>
> The CPU run up is a problem with Tomcat when Apache gets a request
and
> hands it off to Tomcat, but Tomcat doesn't know what to do with it.
This
> usually happens when the URL has a hostname in it that aliases to your
site,
> but Tomcat doesn't know about it. I've seen this in the following
> situations:
>
>
> _Tim
>