Socket operation on a non-socket (wodSmtp)
I've developed a (quite complex) application which uses two wodSmtp components in non-blocking mode simultaneously. Each one of the two components sends a message, disconects, reconnects, sends another one, etc.
Some of my users are experiencing a socket operation on a non-socket error ; this occur at random (sometimes the problem disappear, then reappears) without any recognizable path. And it is very hard to be reproduced on other machines.
My application does not deal with sockets directly; all operations are demanded to wodSmtp, which is accessing the socket.
What can be causing this error? What should I suggest to my users? Are there any best-pratictes , or things to be avoided, in order to solve the error?
Since reproducing the error is hard, what I need is an explanation of which situations (or wodSmtp programming pratcices) could lead to that error.
Thank you
Re: Socket operation on a non-socket
Luca,
It would be great if you could trace the error, or put enable DebugFile Property in your application, and once the error occures, send it over to us. That way we could try to locate the error.
Can you try to handle an error, and ignore it? Does everything work as expected after that? Since it's Winsock error, there is great chance that this doesn't only happen only on your application.
The discription for this error is: Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.
It would be great if you could duplicate this and send us a sample, something we could run on our side and duplicate the behaviour.
Regards,
Damba
