Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <29328525.post@talk.nabble.com>
Date: Mon, 2 Aug 2010 11:53:21 -0700 (PDT)
From: imtrick <patrick.morris@hp.com>
To: users@tomcat.apache.org
Subject: Re: Http 505
In-Reply-To: <2dfefcd21002092001i1bf36bfck5341f2ef1df63d9b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <2dfefcd21002092001i1bf36bfck5341f2ef1df63d9b@mail.gmail.com>


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