Affects Version/s: 5.6.4, 6.2.4
Fix Version/s: 6.4.0
My HPCC version is:
- HPCC Cluster 5.6.4-1
- HPCCClientTools 5.6.4-1
I have this "advanced" ECL code:
WaitingTime:=65*60*1000;// 65 mins
OUTPUT ('ETL Start...');
OUTPUT ('ETL End...');
If I run it from ECLIDE it works ok. If I run it from HPCCClientTools I find problems. Exact Command is:
PS C:\CODE\odin\HPCC> ecl run thor ".\BWR\OscarFoley\BWR_FakeRunETL1h.ecl" --username="Oscar.Foley" --password=" " -legacy --server="HPCC.Server" --port="8010" -I "."
1- Code starts to run correctly.
2- After 65 mins you can see in ECLWatch it finishes.
3- HPPCClientTools (ecl.exe) fails to detect that it finished.
4- After two hours, HPPCClientTools (ecl.exe) launches following error:
SOAP rpc error[errorCode = -6 message = timeout expired
Target: C!10.53.56.31, Raised in: D:\jenkins2\workspace\CE-Candidate-Clienttools-Win32-5.6.4-1\CE\Windows_2k8_Servers\HP
CC-Platform\system\jlib\jsocket.cpp, line 1600
Seems that in long ECL queries HPCC fails to report back successful execution.
- Same code with less time (58 mins) works ok. Seems a time related problem in HPCC.
- Different long code also fails. This code is a simplification of my RunETL.ecl code. This proves is not related with STD.system.Debug.Sleep code. So it is not a code problem*.
- It happens with two different environments so it is not an installation problem.
- Both environments have the same version and I don't have access to a newer HPCC server so it might be a bug in HPCC 5.6.4-1. Ideally someone with the latest version could try this...
- It happens both from my Windows7 laptop and from Jenkins Linux server, so it is not OS related
|Document new "ecl run" option --poll||Resolved|