threadpooling problem?

[Guest]

I am programming a asyncronous server with .NET using ThreadPool..
Basicly Client connected to server using TCP sockets
When I test the program until 25 client server can respond all clients.but
after 25. client connected server cant respond other clients!where is the
problem?

when a client connected i want to check socket if data avaible..

ThreadPool.QueueUserWorkItem(new WaitCallback(CheckSocket),_socket);
.....
the CheckSocket callback:
private void CheckSocket(object state)
{
while(_connected)
{
if(_socket.Poll(-1, SelectMode.SelectRead))
{
if(_socket.Connected)
{
....
}
}
}

 

[Sriram Krishnan]

The ThreadPool has a limit of 25 threads - there is your problem.

 

[Guest]

but when a thread must exit from threadpool?why a thread dont exists from
threadpool?thanks

 

[Sriram Krishnan]

A thread in the pool becomes free when a task is completed. However, in your
code,CheckSocket never returns - so no thread becomes free. If you're using
Whidbey, you have an option of increasing the maximum no. of threads to a
higher number

 

[William Stacey [MVP]]

With respect, that is not a good way to do an async server. Instead of
going down a list, I would instead point you to the following for your
review. If still questions, please post back. Cheers!
http://www.c-sharpcenter.com/Tutorial/Socket/socket02.htm
http://www.devhood.com/tutorials/tutorial_details.aspx?tutorial_id=709
http://msdn.microsoft.com/library/d...html/cpconnon-blockingserversocketexample.asp

 

[Richard Blewett [DevelopMentor]]

One small detail: its 25 threads *per processor* and it can be altered just not from managed code. Mike Woodring wrote a sample that used interop to reach out into native code and tweak the size of the threadpool.

http://www.bearcanyon.com/dotnet/#tpcontrol

Regards

Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog

The ThreadPool has a limit of 25 threads - there is your problem.