Hi Allard,
Thanks for the pointers. I implemented the solution you suggested but unfortunately it seems that NoHandlerForCommandException is not even considered for retries. I added a breakpoint inside isExplicityNonTransient(....) which is never reached when NoHandlerForCommandException is raised. As mentioned before I'm not that familiar with the framework but was hoping that somehow that the commandRouter (spring cloud in my case) would be able to delegate down to eureka retries somehow. Any other ideas or am I missing something?
Apart from the unresolved issue above I just want to point out the following to other interested parties.
* As a side-benefit of overriding isExplicityNonTransient(....) and checking out expected business type exceptions of type RuntimeException, it no longer retries our "known" exceptions unnecessary, which is great!
* As an improvement to IntervalRetryScheduler it would be good if log levels could be downgraded to debug level as it's polluting our logs with unnecessary info with regards to retrying. Even better would be to not include the entire stacktrace as part of the log.
Regards,
Dylan