| Dart Home | PowerTCP Sockets for .NET | Custom Development | Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums |
| Author | Forum: PowerTCP Sockets for .NET (Secure and Standard) Topic: 25 connection limit? |
| Jason123 fowlerjp@hotmail.com From: Pittsburgh, PA USA Posts: 5 Member Since: 04/26/03 |
posted September 3, 2003 9:54 AM I am writing an Instant message type app that is integrated into our intranet application. We had done it in VB6 using the built in Winsock but wanted to expand with VB.Net and services. Now using the TCP Server we have everything working except we cannot get over 25 connections. I have it as a WinForm app and a service on a server, both limited to 25. I am not an expert in this area so I have not modified many if any of the default settings and I followed the examples. Like I said everything runs smooth except for the 25 limit. I am using TCP and I have the clients connect to the server on port 1129. Any suggestions? Thanks |
Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted September 3, 2003 12:20 PM Do you see the same limit using our sample echo server? If so, please tell me what you did to test it. |
K M Drake From: Utica, NY USA Posts: 3406 Member Since: 07/14/00 |
posted September 3, 2003 12:34 PM Hi, The following thread may provide some help: http://support.dart.com/postings?topicid=2821&search=1 -ken |
| Jason123 fowlerjp@hotmail.com From: Pittsburgh, PA USA Posts: 5 Member Since: 04/26/03 |
posted September 3, 2003 5:16 PM I will run some tests on the echo sample because that was the original base that I followed. A quick compare of the two echo uses e.tcp.recieve.tostring, and I was using e.stream.read(blabla) I don't have the code in front of me right now. Based on what I have read it seams that async problem seams to be me. But I have not hit the 25 thread limit. I am maxing out at 25 connections with 37 threads, probably the same thing. I will see what I can do with that c# code I have had luck converting stuff in the past. I like your products and have multiple copies of most of them for the developers but isn't this a bad limit. Reality is I am probably just doing it wrong, which I would welcome another approach recommendation. Thanks |
| Jason123 fowlerjp@hotmail.com From: Pittsburgh, PA USA Posts: 5 Member Since: 04/26/03 |
posted September 4, 2003 7:55 AM Hello, Testing the included Echo server demo with small modifications (Connection counter, 0 for timeout) and I encountered the same problem. The test client was the sample TCP Client; I just opened it 30 times. With 25 connections at 32 threads the server stopped responding to additional connections. The TCP client reported that it connected above 25, it would just not echo. Then when one dropped off, one above 25 became responsive. I got the C# code for the Thread Pool Controller and gave up on the conversion to VB.Net, due to lack of inter-op knowledge. Then I remembered that I could just compile the assembly and reference it in VB.Net which then allowed me to get to work. :) It turns out that my Dev system running XP with Intel Hyper Threading had 50 worker threads and 1000 I/O, while the 2000 P3 was 25-1000. The threads may default to 25 per processor? This explains why in Dev my test group (30~40 clients) did not have a problem. For our production I will set the start max to 1000-1000 and then code a monitor to self adjust as needed. I currently have over 800 clients that will need this. I hope the server will allow that many threads. My Exchange server according to Task manager runs over 1000 threads, and this will be on it’s own server. Hope this works and it's stable :) Thanks |
| fonager From: Copenhagen, Denmark Posts: 25 Member Since: 11/18/03 |
posted December 2, 2003 6:56 AM There is a limit of 25 threads per processor built into .NET Framework. You can change these limitation using this free component, which we use ourselves : http://www.devshock.com/products/tool/ThreadPoolManager/ |
| Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|