Underlying Connection Was Closed on a Send

[Jeff_Lav]

I have a problem when the HTTP keep alive is set to true on a server. When a
other server call a web service to that server (the one with the HTTP keep
alive is at true) I receive randomly a "Underlying connection was closed on a
send" if I retry a few second after, everything works well. This can append
10 times a day in a production environnement. I do not want to disable the
HTTP Keep alive and I do not want to code a retry on error in my application.
Is there a way to prevent the lost of connection?

Thanks!

[Bruce Barker]

you should not use keepalive with a webservice. also as webservice calls are
not reliable, you should always have retry logic.

-- bruce (sqlwork.com)

"Jeff_Lav" <Je*****@discussions.microsoft.com> wrote in message
news:18**********************************@microsof t.com...

I have a problem when the HTTP keep alive is set to true on a server. When
a
other server call a web service to that server (the one with the HTTP keep
alive is at true) I receive randomly a "Underlying connection was closed
on a
send" if I retry a few second after, everything works well. This can
append
10 times a day in a production environnement. I do not want to disable the
HTTP Keep alive and I do not want to code a retry on error in my
application.
Is there a way to prevent the lost of connection?

Thanks!

[Jeff_Lav]

Thanks Bruce,

But I really need to use the "HTTP Keep Alive" for 2 reasons :
- For performance. There is some performance issues when the HTTP Keep
Alive is not acitve.
- For integrated security. When the HTTP Keep alive is not active you
cannot call on the same server another web service using integrated security
(I don't understand why but it's like that...)

We have a lot of applications and open the code for doing some retry will be
a lot of job. Also I find that strange that we have to worried about that
kind of stuff at that level. What I meen is the level of abstraction with the
proxy class is pretty high, when we call a web service we do not code TCP/IP
socket opening and other network stuff like that everyting is handle by
framework and that thing should be to... This is what I think...

Jeff

"Bruce Barker" wrote:

you should not use keepalive with a webservice. also as webservice calls are
not reliable, you should always have retry logic.

-- bruce (sqlwork.com)

"Jeff_Lav" <Je*****@discussions.microsoft.com> wrote in message
news:18**********************************@microsof t.com...

I have a problem when the HTTP keep alive is set to true on a server. When
a
other server call a web service to that server (the one with the HTTP keep
alive is at true) I receive randomly a "Underlying connection was closed
on a
send" if I retry a few second after, everything works well. This can
append
10 times a day in a production environnement. I do not want to disable the
HTTP Keep alive and I do not want to code a retry on error in my
application.
Is there a way to prevent the lost of connection?

Thanks!