If you want to truly rule out Tomcat as the source you should use tcpdump or wireshark to capture
the raw network traffic.
Thanks
Sam
------Original Message------
From: imtrick
To: users@tomcat.apache.org
ReplyTo: Tomcat Users List
Subject: Re: Http 505
Sent: 2 Aug 2010 19:53
jgroups wrote:
>
> Tomcat 6
>
> Our application non-java client (C/Java) are occassionally seeing
> Http 505. But there is no such error being logged in the tomcat access
> log. Clients are for sure seeing 505 but we are not so I am wondering
> if someone can help me understand why that might be occuring? In the
> response header they see:
>
> Response header: Apache-Coyote/1.1
> Response header: connection close
>
I'm curious if you ever found a solution to your problem.
Since upgrading from Tomcat 6.0.20 to 6.0.28, we're seeing a similar issue,
where URLs that worked fine before the upgrade are throwing 505's to
clients. If we revert back to 5.0.30, the problem goes away.
--
View this message in context: http://old.nabble.com/Http-505-tp27525965p29328525.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Sent from my BlackBerry® wireless device |