Reputation: 93
Background
We provide some webservices to export and import some data to a website. Unfortunatly the programmers of that website don't seem to, or don't want to understand, that if they try three times and get three errors, the 1,000,000th time it also will give an error.
So they constantly open new requests to the webservice wich result in a constant flow of new business connector users. The problem with this is that they creating database blocks, but the database will not be able to solve this because when it will time out, there are a few 1000 new business connector users waiting to block that process all over again. This morning the whole server was inresponsive and a reboot of the AOS toke about 32 minutes to complete. (normally it would take 2 minutes)
Question
I was searching for a way to limit the number of business connector users. The only related post I found was this one: http://www.archivum.info/microsoft.public.axapta.programming/2010-01/00045/RE-.NET-business-connector-amp-Web-Services.html
Unfortunatly there is no answer to their question and I couldn't find more topics.. Does anyone have an idea how I could solve this?
Any help or pointers in the right direction would be greatly appriciated.. :)
Upvotes: 0
Views: 1200
Reputation: 796
It sounds as if the problem is with the web service. Can you rework it so that it does not cause blocking?
Meanwhile, look into the MaxConcurrenctBCSessions setting. see http://msdn.microsoft.com/en-us/library/aa569637(v=ax.10).aspx
Upvotes: 0