Re: Calling Web Service Asynchronously
- From: "Mike C#" <xyz@xxxxxxx>
- Date: Wed, 15 Nov 2006 19:24:47 -0500
"John Saunders" <john.saunders at trizetto.com> wrote in message
news:uI3xnG$BHHA.3836@xxxxxxxxxxxxxxxxxxxxxxx
"Mike C#" <xyz@xxxxxxx> wrote in message
news:VIa6h.784$ra3.761@xxxxxxxxxxxxxxx
"John Saunders" <john.saunders at trizetto.com> wrote in message
news:e%23tgOv5BHHA.4992@xxxxxxxxxxxxxxxxxxxxxxx
You can get this error when you have too many connections open in IIS.
That appears to be the problem :( Is it too many connections from one
client? What's the best way to perform multiple asynchronous calls from
ASP.NET? Or is it even possible?
If you're running IIS on Windows XP, then it's meant to be an upper limit.
It's a license thing.
Are you calling Dispose on your proxy objects? If not, then you're leaving
the connections open.
John
Actually running it on Windows Server 2003, and properly disposing of all
IDisposable objects. I've been told there may be a registry setting that
needs to be modified and I'm trying to find info. on that to give it a
shot... We'll see... Thanks.
.
- References:
- Calling Web Service Asynchronously
- From: Mike C#
- Re: Calling Web Service Asynchronously
- From: Mike C#
- Re: Calling Web Service Asynchronously
- From: Mike C#
- Re: Calling Web Service Asynchronously
- From: John Saunders
- Re: Calling Web Service Asynchronously
- From: Mike C#
- Re: Calling Web Service Asynchronously
- From: John Saunders
- Calling Web Service Asynchronously
- Prev by Date: Re: use SOAP header for asp.net session state
- Next by Date: Re: use SOAP header for asp.net session state
- Previous by thread: Re: Calling Web Service Asynchronously
- Next by thread: Allitcertkiller.com exams are now more cheaper than Testking.co.uk
- Index(es):
Relevant Pages
|
Loading