Kepler exit when using echoGridWriter actor with the wrong xml path.
The message for the execution of the attached workflow.
[run] EcogridUtils: The time to create instance is =========== 0
[run] Exception in reading data from file: build.xml (No such file or directory)
/Users/jianwu/Kepler/repository/kepler/kepler.modules/kepler2beta1/build-area/build.xml:35: Java returned: 1
It's an obvious exception when the Kepler can not find the xml, yet kepler should give a exception message rather than not just quit.
It is reproducible at Kepler 1.x and 2.0.0 beta1.
#2 Updated by Jing Tao about 10 years ago
This issue was caused on PutServiceClient.java. Aprivate method on this class called System.exit(1) when it caught an exception, in this case, FileNotFoundException.
I fixed the bug on seek/ecogrid module.
In order to avoid the risk of introducing six new built ecogrid jar files into kepler, I modified code on Kelper side too. New code on EcogridWriter and EcogridRepository classes bypassed the method which has the bug. But the functionality hasn't been changed.
I tested both trunk and 2.0 branch, they worked for me. I am going to close the bug.
Jianwu, would you please verify that the bugs was fixed? If it doesn't work for you, please reopen the bug.