G
Guest
I am working on a .Net Web Service which will be used by thousands of users
at a time. It does lot of file operations (Creating, deleting, enumerating,
reading attributes etc) and Ldap queries to AD using .Net APIs. Under stress
test, service machine runs out of Sockets and we start seeing weird errors. I
created MaxUserPort entry in registry on service machine toa llow 65,500 max
no. of sockets to be created. It runs fine now. It could be a problem later
during more stress in production. Is there a way in .Net to minimize socket
usage during file and ldap AD operations? Is there a way i can force the
machine to recycle the sockets so it never runs out of socket.
Thanks,
Salim Ansari
at a time. It does lot of file operations (Creating, deleting, enumerating,
reading attributes etc) and Ldap queries to AD using .Net APIs. Under stress
test, service machine runs out of Sockets and we start seeing weird errors. I
created MaxUserPort entry in registry on service machine toa llow 65,500 max
no. of sockets to be created. It runs fine now. It could be a problem later
during more stress in production. Is there a way in .Net to minimize socket
usage during file and ldap AD operations? Is there a way i can force the
machine to recycle the sockets so it never runs out of socket.
Thanks,
Salim Ansari