So the socket doesn't fall down after 10 seconds (which would
indicate a timeout problem) but when the request is sent and
a response would be expected. This indicates that either the
server or (more likely) some firewall inbetween doesn't like
the request you are sending and simply drops the connection.
A server would be expected to send a 4xx response, that's why
I suspect a firewall. We had one case where a firewall didn't
like the "User-Agent" header that HttpClient sends by default.
Replacing that with the User-Agent of some well-known browser
solved the problem.
the post is an xml post of data, quite heavy...
646213 bytes of data, is too heavy ?
The size of the data is not the problem.
a) Can you test with smaller or larger XML data?
That would help to verify that it is not a timeout problem
but occurs always after the full request is sent.
with smaller data, there is no pb !!!
that's why t thought about kind of timeout on the socket...
i have my web server on one side, started in debug way with breakpoint.
i have my small httpclient on the other side, making a simple post request.
i start the small client
i see the server stopped at the breakpoint.
i just do nothing, every body is waiting.
and after 10 seconds, the connection dropped !!
mays be because i started the web server with jetty....
i am lost.
thank to try helping me !
b) Do you have another application that successfully
communicates with that server?
Then you could compare a request sent by that application
with the request sent by your application.
hope that helps,
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Sébastien Geindre
DPREVI/AERO/DEV
sebastien.geindre __at__ meteo.fr
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
