[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference jamin::pathworks32

Title:	Digital PATHWORKS 32

Moderator:	SPELNK::curless

Created:	Fri Nov 01 1996
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	337
Total number of notes:	1612

168.0. "WSARecv(): any limits on the no. of pending I/Os ?" by EDSCLU::JAYAKUMAR () Mon Mar 17 1997 14:17

Alpha, WNT V4.0
Pathworks V??
Winsock2/DECnet APIs

My application server accepts DECnet connections from VMS clients and sends
and receives using Overlapped socket I/O.

I am posting a WSARecv() with an overlapped socket and passing in an 
lpOverlapped structure and a completion routine, and I get this:

	- WSARecv() returns SOCKET_ERROR, as expected
	- WSAGetLastError() return 0 instead of WSA_IO_PENDING.
	- The completion routine never gets called.

This does not happen in the first connection or the first WSARecv(), but after 
30+ connections have been established. i.e this happens when there are already
30+ outstanding WSARecv()'s pending in overlapped/callback mode (in the same
thread).

I haven't seen if the behaviour is the same for TCP too. Any thoughts as
to why this might happen. Are there any limits to the number of pending I/Os
in a thread or a process ..?

Thanks
-Jay

T.R	Title	User	Date	Lines
168.1		JAMIN::MAJEWSKI	`Tue Mar 18 1997 08:38`	2
	you need to include what versions of components you are running!
168.2		EDSCLU::JAYAKUMAR	`Tue Mar 18 1997 11:31`	8
	re: .-1 Pathworks SSB [7.0] Winsock2/DECnet stack NT 4.0 Any other components?
168.3		JAMIN::MAJEWSKI	`Wed Mar 19 1997 13:07`	7
	what are the version numbers of the specific PATHWORKS 32 components? (check pwlog and/or properties on the files) was this a clean installation (no PATHWORKS on the system ever)?
168.4	version info of "components"	EDSCLU::JAYAKUMAR	`Thu Mar 20 1997 10:37`	25
	>> was this a clean installation (no PATHWORKS on the system ever)? The previous version eft2c was uninstalled/removed before this SSB kit was installed. Thats as clean as I can get, unless you want me to reformat the disk, reinstall NT and then Pathworks. I do that only if I suspect my machine has sustained a virus attack :-) >> what are the version numbers of the specific PATHWORKS 32 components? >> (check pwlog and/or properties on the files) Again, I don't understand what components you are referring to. Its the latest (SSB) kit that was installed and would it be fair to guess all the "PATHWORKS 32 components" would be the ones that go along with this kit? Anyway from the properties on all pw32.dll files on my system: filename version creation date ------------------------------------------------------ pwel32.dll 1.0.003 Feb 26, 1997 pwiocb32.dll 1.0.011 Feb 26, 1997 pwsock32.dll 1.00.123 Feb 26, 1997 pws2dnet.wsp 7.0.40 Feb 26, 1997 From Pathworks Eventlogger: DECLOG Version 1.0.007
168.5	more interesting info	EDSCLU::JAYAKUMAR	`Thu Mar 20 1997 10:42`	19
	From the PW event log: --------------------- PWIO0003E: Out of internal resource (iocbinfo contexts) Severity: Error Explanation: There were too many outstanding IOCB calls. User Action: The code making so many simultaneous calls should be modified to have a smaller number outstanding at one time. ========================================================================= The above message which I just happened to notice gives me a suspicion that there is a limit on the number of pending asynch calls at any time. As low as <40 ? Please tell me I am wrong. -Jayakumar
168.6	is this a bug? or a feature?	EDSCLU::JAYAKUMAR	`Tue Mar 25 1997 09:53`	6
	Any thoughts as to what I may be doing wrong? .. or is it QAR material? Thanks -Jayakumar
168.7	Number of outstanding IOCBs	JAMIN::KROBINSON	`Mon Apr 07 1997 09:59`	3
	DECnet should support 1023 outstanding IOCBs. Please QAR this problem. Ken Robinson