nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Preprocessor exception handling

TeamsiteUser

Is there any way in which we can stop datadeploy process from getting executed if there is an exception in data deploy preprocessor?

preProcessTuple() does not have exception handling in its signature..

TS ver : 6.5

Regards,

Find more posts tagged with

Comments

Bill Klish

We still throw a general RuntimeException inside our code which is picked up by OpenDeploy and stops the deployment, signalling failure. This was only tested as a standalone data deployment, not part of any dbloader component, but I assume it would still work in that case to.

TeamsiteUser

I tried using RuntimeException, it gives me an error in data deploy logs but it does not stop data deploy from continuing.

I am also attaching the log with error statement in bold.

Actually we have just migrated from 5.5 to 6.5, so all the data deploy scripts are still the same as they were for 5.5. Do we need to change some configuration or something like that??

Also the code written to test this runtime exception is as follows:

public Hashtable PreProcessTuple(Hashtable input, String area, String basearea) {
try{
return ProcessTuple(input, area);
} catch ( RuntimeException e) {
throw e;
}
}

private Hashtable ProcessTuple(Hashtable input, String area) {
try {

input = processIndexFlagForDelayedDeploy(input);
System.out.println("<<111>>");
int i = 1/0;

dbHandle.close();
} catch (Exception exc) {
exc.printStackTrace();
throw new RuntimeException();
}
return input;
}

Adam Stoller

I'm not a java expert in any way, shape, or form, but perhaps if your original try form set a variable to the return value of ProcessTupple and then returned the value, instead of doing it all in one statement, it might do what you want?

I tried using RuntimeException, it gives me an error in data deploy logs but it does not stop data deploy from continuing.

Also the code written to test this runtime exception is as follows:

public Hashtable PreProcessTuple(Hashtable input, String area, String basearea) {
try{
return ProcessTuple(input, area);
} catch ( RuntimeException e) {
throw e;
}
}
...

Bill Klish

don't have a try catch block in your code. Throw the RuntimeException up all the way. I think that is what we have, but I am not in front of it at the moment.

I will see if I can find what the log output looked like when we experienced issues, but I believe we didn't try and handle the exception at all in our code. We just logged the error and then threw the RuntimeException.