The I O operation has been aborted because of either a thread exit or an application request

Question

My application is working as a client application for a bank server. The application is sending a request and getting a response from the bank. This application is normally working fine, but sometimes

The I/O operation has been aborted because of either a thread exit or an application request

error with error code as 995 comes through.

public void OnDataReceived(IAsyncResult asyn)
{
    BLCommonFunctions.WriteLogger(0, "In :- OnDataReceived", 
                                        ref swReceivedLogWriter, strLogPath, 0);
    try
    {
        SocketPacket theSockId = (SocketPacket)asyn.AsyncState;

        int iRx = theSockId.thisSocket.EndReceive(asyn); //Here error is coming
        string strHEX = BLCommonFunctions.ByteArrToHex(theSockId.dataBuffer);                    

    }
}

Once this error starts to come for all transactions after that same error begin to appear, so please help me to sort out this problem. If possible then with some sample code

Regards, Ashish Khandelwal

User · Answer

I had the same issue with RS232 communication. The reason, is that your program executes much faster than the comport (or slow serial communication).

To fix it, I had to check if the IAsyncResult.IsCompleted==true. If not completed, then IAsyncResult.AsyncWaitHandle.WaitOne()

Like this :

Stream s = this.GetStream();
IAsyncResult ar = s.BeginWrite(data, 0, data.Length, SendAsync, state);
if (!ar.IsCompleted)
    ar.AsyncWaitHandle.WaitOne();

Most of the time, ar.IsCompleted will be true.

User · Answer

995 is an error reported by the IO Completion Port  The error comes since you try to continue read from the socket when it has most likely been closed   Receiving 0 bytes from EndRecieve means that the socket has been closed  as does most exceptions that EndRecieve will  throw    You need to start dealing with those situations    Never ever ignore exceptions  they are thrown for a reason   Update  There is nothing that says that the server does anything wrong  A connection can be lost for a lot of reasons such as idle connection being closed by a switch router firewall  shaky network  bad cables etc   What I m saying is that you MUST handle disconnections  The proper way of doing so is to dispose the socket and try to connect a new one at certain intervals   As for the receive callback a more proper way of handling it is something like this  semi pseudo code    public void OnDataReceived IAsyncResult asyn        BLCommonFunctions WriteLogger 0   In  - OnDataReceived   ref swReceivedLogWriter  strLogPath  0        try               SocketPacket client    SocketPacket asyn AsyncState           int bytesReceived   client thisSocket EndReceive asyn     Here error is coming         if  bytesReceived    0                      HandleDisconnect client             return                      catch  Exception err               HandleDisconnect client              try               string strHEX   BLCommonFunctions ByteArrToHex theSockId dataBuffer                                  do your handling here           catch  Exception err                   Your logic threw an exception  handle it accordinhly            try              client thisSocket BeginRecieve    all parameters                catch  Exception err               HandleDisconnect client             the reason to why I m using three catch blocks is simply because the logic for the middle one is different from the other two  Exceptions from BeginReceive EndReceive usually indicates socket disconnection while exceptions from your logic should not stop the socket receiving

User · Answer

I had this problem  I think that it was caused by the socket getting opened and no data arriving within a short time after the open  I was reading from a serial to ethernet box called a Devicemaster  I changed the Devicemaster port setting from  connect always  to  connect on data  and the problem disappeared  I have great respect for Hans Passant but I do not agree that this is an error code that you can easily solve by scrutinizing code

User · Answer

In my case  the request was getting timed out  So all you need to do is to increase the time out while creating the HttpClient   HttpClient client   new HttpClient     client Timeout   TimeSpan FromMinutes 5

User · Answer

What I do when it happens is Disable the COM port into the Device Manager and Enable it again   It stop the communications with another program or thread and become free for you   I hope this works for you  Regards

[c#] The I/O operation has been aborted because of either a thread exit or an application request

The answer is

Examples related to c#

Examples related to sockets

Examples related to exception

Tags