On 8/24/06, Roland Weber <[EMAIL PROTECTED]> wrote:
Do they send a header for the expect-continue-handshake?
They don't appear to. That was my first thought too, because following through the HttpClient code this is one of the only ways in which it's possible to send a content length for a POST request with no parameters, which appears to be what's happening.
> Once the problem has occurred once, it then persists until the server > is restarted.
This sounds very strange. I would suspect a problem with connection keep-alive that should be resolved by closing the connection. Try sending a connection: close header with each request. That will cost some performance because keep-alive is the disabled completely, but if it makes your application stable, it's probably worth it.
That is the strangest bit, but it strikes me that I've explained it incredibly badly - it's the server on which HttpClient is running that needs to be restarted to resolve the problem, not the target server for the query (it's a setup with a web application making HTTP requests using HttpClient to the back end). Will try adding connection: close and see if that helps things.
Also, investigate what software is running on the server. A bug there can not be ruled out.
Not entirely, but it's being accessed by a number of clients and is working fine for all the ones that *haven't* exhibited this behaviour, even running exactly the same codebase. The code on the target server is a number of Java web applications, and requests to all of them cause the same issues. The app server for both sides of the connection is Weblogic 8.1, if that makes a difference... Adrian -- [EMAIL PROTECTED] http://www.veryshortpier.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
