Charles,

Compare an unused port and an active Tomcat, and there is a difference. Tomcat will clear the screen and wait for input. An unused port will appear to hang there and eventually time out.

For our production server, after Tomcat installation the Telnet session appears like its communicating with an unused port (no listener).


At 10:32 PM 12/21/2005, you wrote:
> From: Caldarale, Charles R
> Subject: RE: DNS error, no reply from Tomcat and no clues in the log
>
> > From: William Claxton [mailto:[EMAIL PROTECTED]
> > Subject: DNS error, no reply from Tomcat and no clues in the log
>
> > But if I telnet to the machine's IP address and connect to
> > port 8080 there is no reply.
>
> Firewall, perhaps?

I just tried this on two different platforms and get no response to a
telnet open on an active, verified functional Tomcat port, so the no
reply behavior appears to be normal.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

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


Regards, Bill Claxton ([EMAIL PROTECTED])
MSN: [EMAIL PROTECTED]
Skype: [EMAIL PROTECTED]
Blog: http://learningweb.blogspot.com


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

Reply via email to