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
element is not in server.xml; w
> 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 ele
The above is confusing to me. Where is the app deployed?
webapps/ROOT (works) or webapps/meshcms (doesn't)
Where is the element for this app located?
conf/server.xml
What are the attributes specified for this ?
With Tomcat 5 and above, elements should not go in server.xml,
the p
> 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"
> (t
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 ( and
) 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 might wa
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 corr
> 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
> 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 yo
Friday, 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
> &quo
On 27/10/06, Pid <[EMAIL PROTECTED]> wrote:
And try adding myhost.com, 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 FQDN when
I just tried the same change, and it all works fine - assuming you have
made an entry for myhost.com in your hosts file, restarted Tomcat, and
cleared your browser's cache.
That occured to me just after I sent mail ;-) I've just tried that
and it didn't help, unfortunately :-(
>
I reali
And try adding myhost.com, 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 localho
> 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
I'm sure this must be a FAQ, but I can't find the answer anywhere. I
have a simple standalone tomcat install that works just fine, but as
soon as I change the Engine defaultHost and Host name fields from
"localhost" to "myhost.com", everything stops working. As well as
changing the entries in se
14 matches
Mail list logo
