kEADDRINUSEErr and OTConnect() confusion...
kEADDRINUSEErr and OTConnect() confusion...
- Subject: kEADDRINUSEErr and OTConnect() confusion...
- From: Alin Pilkington <email@hidden>
- Date: Sat, 1 Nov 2003 14:00:47 -0800
Hi,
This is probably a real simple thing to resolve but I seem unable to
find out the answer from my own bumbling around...
Here is what I have:
1) OT based application developed on OS 9, ported to Carbon and is now
running on OS X
2) All endpoints are running asynchronously
3) Listener endpoint is bound to 33500 and has a qLen of 60 (made it
this large to try and eliminate my problem...)
The problem is that occasionally (how I wish it were consistently...it
would be much easier to debug) when I issue an OTConnect() call in the
Notifier in response to a T_BINDCOMPLETE event, I immediately get back
an error of kEADDRINUSEErr (-3247). Why?
Some more specific questions:
1) I don't understand this situation at all since in the OT docs, it
says that if the endpoints are async (and using a notifier to handle
events), the call to OTConnect() should return a KOTNoDataErr and then
upon the T_CONNECT event, the result of the previously issued
OTConnect() can be determined. Why do I get the kEADDRINUSEErr right
away? I don't think it behaved this way on OS 9...
2) I'm in need of an education here...which address is it complaining
about as being in use? It can't be the active endpoint since it is
already bound to a port (I used kOTAnyAddress) and got back no errors
in the T_BINDCOMPLETE event. Is it the listener port on the remote
computer that it is complaining about as being in use?? That is why I
tried to increase the qLen of the listener port thinking that the queue
might be full...
Any help is greatly appreciated in this matter!
Many thanks...
Alin Pilkington
MitoSystems, Inc.
email@hidden
_______________________________________________
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.