Web Service Problem !!! Help !!!
-
I have problem with calling websevice method Asyncronously using WebService behavior. I can not make more than two request simultaneously to webservice. If I call webservice method 3rd time, it won't event go to web service until response of 1st or 2nd is received. But if I use the same web service in a windows application using Proxy. I can invoke web service method any number of times Asyncronously without waiting for response for the pervious calls. Does anyone know why its behaving like this? Is there any way to solve this problem? Thanks in advance. Sanjeev
-
I have problem with calling websevice method Asyncronously using WebService behavior. I can not make more than two request simultaneously to webservice. If I call webservice method 3rd time, it won't event go to web service until response of 1st or 2nd is received. But if I use the same web service in a windows application using Proxy. I can invoke web service method any number of times Asyncronously without waiting for response for the pervious calls. Does anyone know why its behaving like this? Is there any way to solve this problem? Thanks in advance. Sanjeev
-
I have problem with calling websevice method Asyncronously using WebService behavior. I can not make more than two request simultaneously to webservice. If I call webservice method 3rd time, it won't event go to web service until response of 1st or 2nd is received. But if I use the same web service in a windows application using Proxy. I can invoke web service method any number of times Asyncronously without waiting for response for the pervious calls. Does anyone know why its behaving like this? Is there any way to solve this problem? Thanks in advance. Sanjeev
The problem is not on the WebService, it's on the client. On the client, check the System.Net.ServicePoint.ConnectionLimit, it defaults to 2. Does this number raises an "A-HA" on you? :)
It's not the fall that kills you: it's the sudden stop - Down by Law, Jim Jamursch (1986)
-
The problem is not on the WebService, it's on the client. On the client, check the System.Net.ServicePoint.ConnectionLimit, it defaults to 2. Does this number raises an "A-HA" on you? :)
It's not the fall that kills you: it's the sudden stop - Down by Law, Jim Jamursch (1986)
Then, why it works with windows application? How to check ServicePoint.ConnectionLimit in ASP Application ? Thanks sanjeev
-
Then, why it works with windows application? How to check ServicePoint.ConnectionLimit in ASP Application ? Thanks sanjeev
Sanjeev Kumar wrote: Then, why it works with windows application? Because probably you are passing through a proxy, which only supports HTTP/1.0 forwarding, and in this case, the default connection limit is 4. Check the documentation for ServicePointManager.DefaultPersistentConnectionLimit and ServicePointManager.DefaultNonPersistentConnectionLimit to see this difference. Sanjeev Kumar wrote: How to check ServicePoint.ConnectionLimit in ASP Application ? Just print the damn thing! :)
It's not the fall that kills you: it's the sudden stop - Down by Law, Jim Jamursch (1986)