"Morgan Cheng" <morgan.chengmo@gmail.com> wrote in message
news:1182520362.731954.186760@m37g2000prh.googlegroups.com...
> There are multiple clients to invoke a web service deployed in a
> cluster of server. Each client is using SoapHttpClientProtocol
> instance. I found that if the invocation is continuous,
> SoapHttpClientProtocol doesn't close TCP connection. It just reuse one
> single TCP connection to call target web service.
>
> Now, there are BigIP added between client and server to do load
> balancing. If the TCP connection doesn't close, LB is meaningless.

trizetto.com> wrote:
> "MorganCheng" <morgan.chen...@gmail.com> wrote in message
>
> news:1182520362.731954.186760@m37g2000prh.googlegroups.com...
>
> > There are multiple clients to invoke a web service deployed in a
> > cluster of server. Each client is usingSoapHttpClientProtocol
> > instance. I found that if the invocation is continuous,
> >SoapHttpClientProtocoldoesn't close TCP connection. It just reuse one
> > single TCP connection to call target web service.
>
> > Now, there are BigIP added between client and server to do load
> > balancing. If the TCP connection doesn't close, LB is meaningless.
>
> Is load balancing truly meaningless in this case, or does it simply mean
> something a little different from what you expect? Does the BigIP not
> distribute connections across the nodes? That is, if you had five servers
> and five clients, wouldn't it tend to distribute them one per server?
> Wouldn't the next five clients also be distributed?
>

> I haven't used that particular device, so I don't know.
> --
> John Saunders [MVP]