I'm currently having problems setting up the max concurrent user
allowed to a server with a web service. I have a asmx file that
basically makes sql calls to a database and generates a XML file and
sends it back to the user. The user can select multiple items at once.
For each that they selected, a new thread is created and makes a call
to the asmx file. The first problem I had was that only two threads
where running at any given time. If I started 10 the first two would
connect, after the first finished the third would go, and so on and so
on.
I fixed this problem after reading a bunch of topics here by change the
<connectionManagement> node the machine.config file on the local system
to:
<connectionManagement>
<add address="*" maxconnection="10"/>
</connectionManagement>
This works fine. If I start 10 all 10 will connect at the same time and
everything is good. I then tried editing these files on my server to
limit the connections per user.
The problem I ran into is that the server settings didn't seem to limit
the connections. If I set the maxconnections to 2 on the server and 20
on the client the client could still open 20 connects.
This to me seemed like a big problem. Anyone wanting to do a DOS attack
on my sever could change the maxconnection to 100+ and keep hitting the
same asmx file.
Is there a way to make this change only on the server side?????? For
instance, is there a way I can leave the machine.config file alone on
the client side at maxconnection = "2" and only make the changes on
the server by setting maxconnections = "10" ???? I tried this and it
doesn't work the way it's supposed to where I've read articles on.
Or, is there away to make the changes in both places so that a DOS
attack would not be possible??
Any help would be greatly appreciated.
