OK, first you want to untick the "Die on Error" tick box in all components that have this option. You will also need to implement some try/catch Java logic in your tJavaRow to ensure a failure in your transformation does not fail the job. Maybe have an "error" column which will output the the error in the "catch" section. After the tJavaRow you will probably need a tMap to send the output to either the DB (on success) or to send it round again if it fails.
The looping (or retry) will be the hardest part of this. This is not impossible at all, but will require some thought on how it will loop. This is one of the reasons that I questioned whether it was necessary. You will need to enable a process where the message is tried, fails up to 3 times, for each of the tries under 3 for each message you will need to send it round again. If it fails 3 times, then the message needs to be sent to your error topic. A simple try--> success vs try--> fail process which is rerun later after an alert as to what the error was, would be a lot easier to implement. But as I said, it can be done. But you may need to build the basic process first, test it, find where the errors occur, what the errors reveal themselves as, then start to implement the looping functionality once you fully understand the parameters of the problem. Then come back and show us what you have, what can happen and we can help you through that process.
