Our server only has one appdomain, and it works great. Another thing you really need to be careful about is the whole callback thing. Assume that your callbacks will be coming back on multiple IO threads. This will definitely be the case when running on a multi-processor box (or hyperthreaded), even if your callback code is non-blocking. With multiple CPU's there will be one IO completion port per CPU, and each IO completion port will have at least one IO thread associated with it.
lock lock lock, and lock some more. SyncRoot is good too. Garry Barclay <[EMAIL PROTECTED]> wrote: This problem is happening on a fresh installation of .Net Server 2003. There's no virus checker running. There's no explicit pinning in our code - the framework Socket implementation pins the buffers before issuing the IOs to winsock. Our application is a fairly big one, with multiple appdomains and heavy CPU/memory usage. We're working on a small demo program to reproduce the problem. I'll post this if and when we can isolate the situation. Thanks for the suggestions/ideas so far. =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com --------------------------------- Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
