Re: #10054 Connection reset by peer

Giganews Newsgroups
Subject: Re: #10054 Connection reset by peer
Posted by:  Pascal (coene…@gmaildotcom)
Date: Sun, 07 Mar 2010

Ok, I found some changes in IdFtp "DisconnectNotifyPeer":

- r4103:

procedure TIdFTP.DisconnectNotifyPeer;
begin
  if IOHandler.Connected then begin
    IOHandler.WriteLn('QUIT');      {do not localize}
    IOHandler.CheckForDataOnSource(100);
    if not IOHandler.InputBufferIsEmpty then begin
      GetInternalResponse;
    end;
  end;
end;

- r3830:

procedure TIdFTP.DisconnectNotifyPeer;
begin
  if IOHandler.Connected then begin
    IOHandler.WriteLn('QUIT');      {do not localize}
  end;
  if IOHandler.Connected then begin
    if IOHandler.Readable(10) then begin
      GetInternalResponse;
    end;
  end;
end;

If I change IOHandler.CheckForDataOnSource(100) to
IOHandler.CheckForDataOnSource(10) in r4103 then there is no #100054
exception message anymore.

Op 6/03/2010 19:09, Pascal schreef:
> Hi,
>
> I upgraded from Indy 10 r3830 to r4103. Now I (very) often get this
> #10054 exception after I disconnect. The same application using r3830
> doesn't have this problem. In the status event of IdFtp: Disconnecting
> then Disconnected but then this exception (#100054). Did something
> change in this release (r4103).
>
> Pascal

Replies

In response to

#10054 Connection reset by peer posted by Pascal on Sat, 06 Mar 2010