On 27/10/06, Caldarale, Charles R [EMAIL PROTECTED] wrote:
The 5.0 and 5.5 docs are mild upgrades of the 4.1 versions, and some
areas did not get revised as much as they should have. 5.5 especially
seems to be stricter on use of unnecessary attributes when the Context
element is not in
And try adding Aliasmyhost.com/Alias, instead of changing the host
name. The latter changes expected dir locations too, which is probably
why your app is broken.
p
Caldarale, Charles R wrote:
From: Alan Burlison [mailto:[EMAIL PROTECTED]
Subject: Changing defaultHost from localhost to a
On 27/10/06, Pid [EMAIL PROTECTED] wrote:
And try adding Aliasmyhost.com/Alias, instead of changing the host
name. The latter changes expected dir locations too, which is probably
why your app is broken.
I suspect you are right - I renamed the directories under Catalina
from localhost to the
, October 27, 2006 1:57 AM
Subject: RE: Changing defaultHost from localhost to a FQDN
From: Alan Burlison [mailto:[EMAIL PROTECTED]
Subject: Changing defaultHost from localhost to a FQDN
as soon as I change the Engine defaultHost and Host name fields from
localhost to myhost.com, everything
From: Alan Burlison [mailto:[EMAIL PROTECTED]
Subject: Re: Changing defaultHost from localhost to a FQDN
The really annoying thing is the Tomcat documentation shows FQDN names
being used, yet it doesn't actually work unless you use 'localhost' -
if you need to make other changes when you
From: Alan Burlison [mailto:[EMAIL PROTECTED]
Subject: Re: Changing defaultHost from localhost to a FQDN
The odd thing is that it does appear to be serving *html* from under
the web application directory, just not JSPs. If I put an index.html
under webapps/ROOT I see the content.
I've
If your host entry is pointing to the same IP as the host= in server.xml then
that will work e.g. localhost is same as myhost.com
If your host entry points to a different IP then change the host specification
in server.xml to the new host name in your situation myhost.com
Be sure to put the
I've just tried it again with both 5.5.20 and 6.0.0, changing
localhost to myhost.com in two places in server.xml (Host and
Engine) and in the Windows hosts file. Everything works, including
JSPs and servlets.
For 5.5.20, my server.xml is the default one with the two changes noted
above. You
From: Alan Burlison [mailto:[EMAIL PROTECTED]
Subject: Re: Changing defaultHost from localhost to a FQDN
I have it working - well, kinda. If I deploy the application as ROOT,
and with ROOT as the docBase it works fine. If I move it to meshcms
(the WAR file name) and modify docRoot
The above is confusing to me. Where is the app deployed?
webapps/ROOT (works) or webapps/meshcms (doesn't)
Where is the Context element for this app located?
conf/server.xml
What are the attributes specified for this Context?
Context path= docBase=ROOT reloadable=false /
With
From: Alan Burlison [mailto:[EMAIL PROTECTED]
Subject: Re: Changing defaultHost from localhost to a FQDN
Ah, and I'm using 5.5. I've checked the 5.5 docs and I can't find
*any* of those restrictions mentioned, other than a recommendation
that Context elements aren't placed in server.xml
From: Alan Burlison [mailto:[EMAIL PROTECTED]
Subject: Changing defaultHost from localhost to a FQDN
as soon as I change the Engine defaultHost and Host name fields from
localhost to myhost.com, everything stops working.
I just tried the same change, and it all works fine - assuming you
12 matches
Mail list logo