S
Scott Baierl
I've got a web application that makes web service calls to a J2EE back-end
server farm. It appears that the .NET runtime is setting up a single
connection to one of the J2EE servers on the back-end, and sends all the web
service calls over this connection. We have a CISCO CSM between the .NET
server and the J2EE back-end server farm to network load balance the .NET
calls between 1 of 4 nodes in the server farm. The problem is that the CSM
balances at the connection level, and since my .NET application is only
opening a single connection and keeps that connection open, no load
balancing occurs. I noticed that the .NET runtime will create a maximum of
2 connections by default, but I'm only getting a single connection. That
indicates to me that the amount of traffic I'm generating on the .NET
machine isn't enough to cause .NET to create more than one connection. Is
there a way to force the .NET runtime to create and use more than a single
connection, or is there a way to time that connection out and cause it to
close between web service calls to the back-end, so I can use the full
horsepower of my back-end server farm?
server farm. It appears that the .NET runtime is setting up a single
connection to one of the J2EE servers on the back-end, and sends all the web
service calls over this connection. We have a CISCO CSM between the .NET
server and the J2EE back-end server farm to network load balance the .NET
calls between 1 of 4 nodes in the server farm. The problem is that the CSM
balances at the connection level, and since my .NET application is only
opening a single connection and keeps that connection open, no load
balancing occurs. I noticed that the .NET runtime will create a maximum of
2 connections by default, but I'm only getting a single connection. That
indicates to me that the amount of traffic I'm generating on the .NET
machine isn't enough to cause .NET to create more than one connection. Is
there a way to force the .NET runtime to create and use more than a single
connection, or is there a way to time that connection out and cause it to
close between web service calls to the back-end, so I can use the full
horsepower of my back-end server farm?