RE: Not able to accept more than 60 connections
RE: Not able to accept more than 60 connections
- Subject: RE: Not able to accept more than 60 connections
- From: Mahesh Vyas <email@hidden>
- Date: Thu, 1 Apr 2004 12:28:45 +0530
Can we increase the "Descriptor Table"size ?
Have you even faced this problem with IPLIb (networking library)provided by
Common Components ?
It was working fine in OS 9.x, is their any limitation in OS X.
-----Original Message-----
From: Pranav Kumar Sahu
Sent: Thursday, April 01, 2004 12:21 PM
To: Mahesh Vyas; Kaza Sudheer
Cc: Rama Swamy Yeleswarapu; Abhishek Jain; Kabir Khanna; G Krishnamurthy
Subject: RE: Not able to accept more than 60 connections
Each implementation may have a maximum number of socket handles available,
either globally, per process, or per thread.
So you have it with Multithreaded as well.
If it's going to continue, Pls remove "email@hidden" from
your CC field.
-----Original Message-----
From: Mahesh Vyas
Sent: Thursday, April 01, 2004 12:06 PM
To: Kaza Sudheer; Pranav Kumar Sahu
Cc: Rama Swamy Yeleswarapu; Abhishek Jain; Kabir Khanna; G
Krishnamurthy; email@hidden; Mahesh Vyas
Subject: RE: Not able to accept more than 60 connections
24 EMFILE Too many open files. <As released, the limit on the number of open
files per process is 64.> Getdtablesize(2) will obtain the current limit.
Is it applicable for Multithreaded also ?
-----Original Message-----
From: Kaza Sudheer
Sent: Thursday, April 01, 2004 11:59 AM
To: Mahesh Vyas; Pranav Kumar Sahu
Cc: Rama Swamy Yeleswarapu; Abhishek Jain; Kabir Khanna; G Krishnamurthy
Subject: RE: Not able to accept more than 60 connections
Hi All,
As per the description, After processing the request, the new socket need to
be closed. other wise sid's will be opened in the process. And per process
descriptors are limited. May be you exceeding the limit.
Regards
KSudheer.
-----Original Message-----
From: Mahesh Vyas
Sent: Thursday, April 01, 2004 11:55 AM
To: Pranav Kumar Sahu
Cc: Rama Swamy Yeleswarapu; Abhishek Jain; Kabir Khanna; G
Krishnamurthy; 'email@hidden'; Kaza Sudheer
Subject: RE: Not able to accept more than 60 connections
Introduction of Delay couldnt solve the problem
The accept fails and returns EMFILE i.e.
[EMFILE] The per-process descriptor table is full.
Thanx
Mahesh Vyas
-----Original Message-----
From: Pranav Kumar Sahu
Sent: Thursday, April 01, 2004 10:18 AM
To: Mahesh Vyas; email@hidden
Cc: Rama Swamy Yeleswarapu; Abhishek Jain; Kabir Khanna
Subject: RE: Not able to accept more than 60 connections
It depends on the backlog parameter that you have mentioned with your listen
call. And I think default is 128.
If you are not happy with the performance you can go for multithreaded.
--Pranav Sahu
-----Original Message-----
From: email@hidden
[
mailto:email@hidden]On Behalf Of Mahesh Vyas
Sent: Wednesday, March 31, 2004 5:06 PM
To: email@hidden
Cc: Rama Swamy Yeleswarapu; Abhishek Jain
Subject: Not able to accept more than 60 connections
In MACOSX(Jaguar and Panther), we are using BSD socket calls in our
client-server application.
The server is handling each client in the asynchronous way, i.e, one
function takes care of all client the requests(not creating thread for each
client).
After the number of client(connect call from client) reaches approx. 60, the
server stops accepting new connection, i.e., successive calls to accept()
fails.
1. Is there any limit to the number of connections that can be established
in MACOSX.
2. If yes, is it configurable.
3. Is this architecture(single-threaded) advisable over the multithreaded
one.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.