Transport endpoint is already connected.

  • Follow


Hi:
So I'm not sure if this is the right place for this or not, but
here goes...

I've been working on a communications system for about 2 weeks
now, everything going (mostly) great until now. I had communication
working on a basic level (send, recieve messages that are hard
configured), but had no membership protocol. During the process of the
membership protocol, I didn't have to touch the socket setup or
anything, but something broke along the way. I'm using an API called
SocketW (http://www.digitalfanatics.org/cal/socketw/) to interface to
the socket libraries.
The problem I see now is that every time I call connect(), I get
an  "SWInetSocket::connect() error: Transport endpoint is already
connected" error (EISCONN).
I know this is extremely non-explicit, but I don't know what else
to post, short of posting my entire source code. Any suggestions would
be greatly appriciated. If seeing the source would help, I would not be
against emailing a tar or zip to anyone who is willing to help.
Thanks,
Chris Phillips

0
Reply angels__tear 7/21/2004 4:31:52 PM

Nevermind - I found a weird bug that should have caused problems
before, but for some reason didn't... all taken care of now, thanks!

0
Reply angels__tear 7/21/2004 5:43:46 PM


1 Replies
531 Views

(page loaded in 0.015 seconds)

Similiar Articles:













7/25/2012 2:55:36 AM


Reply: