xpher
asked on
IdFtp 10 and Threads and Abort problem
I'm using D7 and Indy 10. I am attempting the use of threads for
uploading files but I can't work out how to abort part way through
upload. Basically this is some code
type
TFtpUpThread = class(TThread)
private
FFtp: TIdFtp;
protected
constructor Create(CreateSuspended: boolean);
procedure Execute(); override;
end;
type
TForm1 = class(TForm)
//other usual gumph
var
Form1: TForm1;
implementation
{$R *.dfm}
constructor TFtpUpThread.Create(Create Suspended: boolean);
begin
inherited Create(CreateSuspended);
FFtp := Form1.IdFtp1;
FreeOnTerminate := true;
end;
procedure TFtpUpThread.Execute();
begin
FFtp.Put(FLocalName, FRemoteName, true);
Terminate();
end;
procedure TForm1.btnUploadClick(Send er: TObject);
var
ftd: TFtpUpThread;
begin
ftd := TFtpUpThread.Create(false) ;
end;
procedure TForm1.btnAbortClick(Sende r: TObject);
begin
IdFtp1.Abort;
IdFtp1.KillDataChannel;
end;
Trying various ways I get EAccessViolations or other various Id errors.
And the ftp is still working and cannot log in to server again even
with another ftp program. Any assistance especially including code
would be greatly appreciated. My brain hurts with this ;-)
uploading files but I can't work out how to abort part way through
upload. Basically this is some code
type
TFtpUpThread = class(TThread)
private
FFtp: TIdFtp;
protected
constructor Create(CreateSuspended: boolean);
procedure Execute(); override;
end;
type
TForm1 = class(TForm)
//other usual gumph
var
Form1: TForm1;
implementation
{$R *.dfm}
constructor TFtpUpThread.Create(Create
begin
inherited Create(CreateSuspended);
FFtp := Form1.IdFtp1;
FreeOnTerminate := true;
end;
procedure TFtpUpThread.Execute();
begin
FFtp.Put(FLocalName, FRemoteName, true);
Terminate();
end;
procedure TForm1.btnUploadClick(Send
var
ftd: TFtpUpThread;
begin
ftd := TFtpUpThread.Create(false)
end;
procedure TForm1.btnAbortClick(Sende
begin
IdFtp1.Abort;
IdFtp1.KillDataChannel;
end;
Trying various ways I get EAccessViolations or other various Id errors.
And the ftp is still working and cannot log in to server again even
with another ftp program. Any assistance especially including code
would be greatly appreciated. My brain hurts with this ;-)
xpher
fyi, you don't need the
terminate;
line at all, since this is in your thread's "execute" method, when that method ends, it will terminate anyway.
-unrelated-
gotta agree with your comments re indy there ciuly.
my latest question to the indy team about our production release having an indy 10.052 ("stable" release) bug, was to use the latest indy 10 development snapshot... the changes between that release and the snapshot were huge. Not to mention the risks involved in using a build that has this big warning saying "hey we might be writing and making changes to these .pas files as you copy them, so warranty void m'kay".
fyi, you don't need the
terminate;
line at all, since this is in your thread's "execute" method, when that method ends, it will terminate anyway.
-unrelated-
gotta agree with your comments re indy there ciuly.
my latest question to the indy team about our production release having an indy 10.052 ("stable" release) bug, was to use the latest indy 10 development snapshot... the changes between that release and the snapshot were huge. Not to mention the risks involved in using a build that has this big warning saying "hey we might be writing and making changes to these .pas files as you copy them, so warranty void m'kay".
ASKER
Ciuly
Thanks for response. Obviously that idea won't work for aborting part way through as my original post. But it is interesting in the fact that yes it does work. The drawback is it only works once. If I run the project again the form does not show and my connection is constantly alive as in my original problem. If I disable my connection then re-enable it the project again only works once. I'm wondering if it's because the thread has to be aborted also?
TheRealLoki
Thanks for response. Don't you have to terminate it somewhere so it knows to free it?
I must admit I was wondering whether it would just be better to revert to Indy 9. But I must admit the connection seems faster with Indy 10.
Regards
Thanks for response. Obviously that idea won't work for aborting part way through as my original post. But it is interesting in the fact that yes it does work. The drawback is it only works once. If I run the project again the form does not show and my connection is constantly alive as in my original problem. If I disable my connection then re-enable it the project again only works once. I'm wondering if it's because the thread has to be aborted also?
TheRealLoki
Thanks for response. Don't you have to terminate it somewhere so it knows to free it?
I must admit I was wondering whether it would just be better to revert to Indy 9. But I must admit the connection seems faster with Indy 10.
Regards
weird again. my code worked for me fine every single time I run it. of course, I run it from the ide, but that doesn't make much difference in this case. I know that because I kept modifying the slep period to see that indeed it works. and yes, I had to manually delete the chunks of file that were left in a temporary form by the server
ASKER
I ran it from ide and out of ide got same problems.
yeah, but I run it with inde 9, not 10 ;)
you know, you could try installing another delphi instance with indy 9. I don't know if it's possible to install 2 different instances of the same version. you can try :)
you know, you could try installing another delphi instance with indy 9. I don't know if it's possible to install 2 different instances of the same version. you can try :)
ASKER
It might be worth trying. Wont get chance for a day or two cos working.
Using ciuly's code above on Delphi 7, Indy 9, I do not get any errors, but you have to close the socket like this after the abort command
procedure TForm1.Button1Click(Sender : TObject);
begin
IdFTP1.Connect();
ftd := TFtpUpThread.Create(false) ;
sleep(1000);
IdFTP1.Abort;
IdFTP1.DisconnectSocket;
end;
Using ciuly's code above on Delphi 5, Indy 10.052, I have to close the socket like this
begin
IdFTP1.Connect();
ftd := TFtpUpThread.Create(false) ;
sleep(1000);
IdFTP1.Abort;
IdFTP1.Socket.Close;
end;
The FTP Server reports a successful "ABOR" command for each version of Indy
procedure TForm1.Button1Click(Sender
begin
IdFTP1.Connect();
ftd := TFtpUpThread.Create(false)
sleep(1000);
IdFTP1.Abort;
IdFTP1.DisconnectSocket;
end;
Using ciuly's code above on Delphi 5, Indy 10.052, I have to close the socket like this
begin
IdFTP1.Connect();
ftd := TFtpUpThread.Create(false)
sleep(1000);
IdFTP1.Abort;
IdFTP1.Socket.Close;
end;
The FTP Server reports a successful "ABOR" command for each version of Indy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
IdFtp1.Socket.Close disconnects IdFtp1 which is no good if have to reconnect to do anything else.
If I add another button and set its OnClick event to IdFtp1.Abort (removing abort from proc above) the program stops responding and connection stays alive.
Just out of interest what do you have in your uses clause (for version Indy 10.052)? Am I missing something?
My entries to do with IdFtp are
IdAntiFreezeBase, IdAntiFreeze, IdBaseComponent, IdComponent,
IdTCPConnection, IdTCPClient, IdExplicitTLSClientServerB ase, IdFTP
If I add another button and set its OnClick event to IdFtp1.Abort (removing abort from proc above) the program stops responding and connection stays alive.
Just out of interest what do you have in your uses clause (for version Indy 10.052)? Am I missing something?
My entries to do with IdFtp are
IdAntiFreezeBase, IdAntiFreeze, IdBaseComponent, IdComponent,
IdTCPConnection, IdTCPClient, IdExplicitTLSClientServerB
ASKER
Well just downloaded Development Snapshot and everything works fine. Don't have to add IdFtp1.Socket.Close. I just use IdFtp1.Abort and it works everytime without leaving connection open. Also as a p.o.i the LogEvent is much easier to use just as in Indy9.
To thank you both for your input I'm feeling I should split points. Please both post feelings on this.
Cheers
Chris
To thank you both for your input I'm feeling I should split points. Please both post feelings on this.
Cheers
Chris
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hope point share worked Ok never done it before. It was helpful that both of you tried things and let me know the outcome allowing me to test if it was my error.
Many thenks both.
Many thenks both.
second, abort method by itself should do the trick.
here is my test case (delphi 7 + indy 9):
unit Unit1;
interface
uses
Windows, Messages, SysUtils, Variants, Classes, Graphics, Controls, Forms,
Dialogs, IdBaseComponent, IdComponent, IdTCPConnection, IdTCPClient,
IdFTP, IdAntiFreezeBase, IdAntiFreeze;
type
TForm1 = class(TForm)
IdFTP1: TIdFTP;
IdAntiFreeze1: TIdAntiFreeze;
procedure FormCreate(Sender: TObject);
private
{ Private declarations }
public
{ Public declarations }
end;
TFtpUpThread = class(TThread)
private
FFtp: TIdFtp;
protected
constructor Create(CreateSuspended: boolean);
procedure Execute(); override;
end;
var
Form1: TForm1;
implementation
{$R *.dfm}
procedure TForm1.FormCreate(Sender: TObject);
var
ftd: TFtpUpThread;
begin
IdFTP1.Connect();
ftd := TFtpUpThread.Create(false)
sleep(1000);
IdFTP1.Abort;
end;
{ TFtpUpThread }
constructor TFtpUpThread.Create(Create
begin
inherited Create(CreateSuspended);
FFtp := Form1.IdFtp1;
FreeOnTerminate := true;
end;
procedure TFtpUpThread.Execute;
begin
FFTP.Put('s:\DSS-win-5.1.1.0127-jre142_07-Daily.zip');
terminate;
end;
end.
works like a charm.
The main reason for which I stick with indy 9 and did not switch to indy 10 (though I tryied once), is exactly this: some stuff just stopped working. in my opinion, indy 9 is the most stable. I didn't try the latest releases of indy 10 (last time I tried was over a year back when it was in beta) so I can't say if they fixed their problems, but if my code (the way it is) does not work compied with indy 10, then it means they still have serious issues.