Maybe you can give me some insight into why I am having problems with the
tomcat.sh stop command.  When I do "./tomcat.sh stop -host localhost" the
ajp12 connector returns "Error stopping Tomcat with Ajp12 on
localhost.localdomain/127.0.0.1:8007 java.net.ConnectException: Connection
Refused".  

Jeremy Davis
Senior Support Analyst
BPI Marketplace Integration
614.760.8941
1.800.436.8726 - Support Line


-----Original Message-----
From: John Turner [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2003 4:00 PM
To: Tomcat Users List
Subject: Re: tomcat responds with localhost, but refuses the connection
w/ mach inename



Cool.  Tomcat still has its own resolution rules, though.

John

On Fri, 21 Mar 2003 15:53:40 -0500, Davis, Jeremy 
<[EMAIL PROTECTED]> wrote:

> Thanks, I have found that it was not tomcat at all, the issue is a
> networking mismatch between the dns name, and the real ip address are
> completely different.  Using the machinename was having dns point me to a
> box that was not mine, so of course the connection was refused.  Thanks 
> for
> the help though.
>
> Jeremy Davis
> Senior Support Analyst
> BPI Marketplace Integration
> 614.760.8941
> 1.800.436.8726 - Support Line
>
>
> -----Original Message-----
> From: John Turner [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 21, 2003 2:52 PM
> To: Tomcat Users List
> Subject: Re: tomcat responds with localhost, but refuses the connection
> w/ mach inename
>
>
>
> That's one way.  It pretty much comes down to how you want to handle 
> Contexts.  If you want a particular Context to be available for a 
> particular domain/host and that domain/host only, you would use a 
> separate Host container.
>
> John
>
> On Fri, 21 Mar 2003 14:39:39 -0500, Davis, Jeremy 
> <[EMAIL PROTECTED]> wrote:
>
>> I was wondering, I saw the virtual host configuration documentation, and 
>> was
>> about to attempt such a thing.  So I should add an Alias tag, under a 
>> host
>> tag in the server.xml?
>>
>> Jeremy Davis
>> Senior Support Analyst
>> BPI Marketplace Integration
>> 614.760.8941
>> 1.800.436.8726 - Support Line
>>
>>
>> -----Original Message-----
>> From: John Turner [mailto:[EMAIL PROTECTED]
>> Sent: Friday, March 21, 2003 2:37 PM
>> To: Tomcat Users List
>> Subject: Re: tomcat responds with localhost, but refuses the connection
>> w/mach inename
>>
>>
>>
>> Did you configure a virtual host for machinename in server.xml, or just 
>> leave it with localhost?  Tomcat is literal, there is no catch-all like 
>> there is with Apache.  That is, unless you have a Host container for 
>> your hostname or an Alias directive for an already existing virtual 
>> host, Tomcat will not answer the request.
>>
>> <Host name="localhost"..../> - will only take requests for localhost and 
>> none other
>>
>> <Host name="localhost"..../>
>> <Alias>machinename</Alias> - will take requests for localhost + 
>> machinename
>>
>> <Host name="machinename"... /> - will take requests for machinename but 
>> not localhost
>>
>> John
>>
>> On Fri, 21 Mar 2003 14:32:17 -0500, Davis, Jeremy 
>> <[EMAIL PROTECTED]> wrote:
>>
>>> I got red hat 8.0, jdk 1.3.1_07, and tomcat 3.3.1a installed.  If on 
>>> the
>>> server, I do localhost:8080, it works ok and comes up with the welcome 
>>> page,
>>> but when I do machinename:8080 it comes back telling me the connection 
>>> was
>>> refused?
>>>
>>> Thanks,
>>>
>>> Jeremy Davis
>>> Senior Support Analyst
>>> BPI Marketplace Integration
>>> 614.760.8941
>>> 1.800.436.8726 - Support Line
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>>
>
>
>



-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to