On Admin side it is possible to limit the number of sessions user to avoid an overload done by user which are using very often
scripted access or Web Access or Web Services.
On the other hand one user could create dozens of operations.
Under unfavorable circumstances it could lead to the situation that one user could cover lot's of operations (==> DB Handles).
Examples:
- Bad configured Jenkins
- Synchronization of a rarely used project with great file sizes from an offshore location
- Temporarily bad network response time
For such cases it would be good to limit the number of allowed concurrent operations per user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.