Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Isn't 1 failure just enough? Except time outs ... File not there yet ... kinda time-based related things.
But 3 Is just planning for more failure and is 'bad' design. 3 sounds arbitraty, why not 4 or 5 ... I dont get this type of reasoning. Why please elaborate?
Possible solution:
OnComponentError / OnSubJobError ----> tJava
// check if exists
Integer cnt =(Integer) globalMap.get("error_counter");
if cnt != null {
cnt ++;
globalMap.put("error_counter", cnt );
if cnt.equals(3) {
// raise exception to make sure it dies...
throw new Exception();
}
}else { globalMap.put("error_counter", 1 ) ; }
after tJava a tDie/tWarn component to do whatever you want to do ...
Isn't 1 failure just enough? Except time outs ... File not there yet ... kinda time-based related things.
But 3 Is just planning for more failure and is 'bad' design. 3 sounds arbitraty, why not 4 or 5 ... I dont get this type of reasoning. Why please elaborate?
Possible solution:
OnComponentError / OnSubJobError ----> tJava
// check if exists
Integer cnt =(Integer) globalMap.get("error_counter");
if cnt != null {
cnt ++;
globalMap.put("error_counter", cnt );
if cnt.equals(3) {
// raise exception to make sure it dies...
throw new Exception();
}
}else { globalMap.put("error_counter", 1 ) ; }
after tJava a tDie/tWarn component to do whatever you want to do ...