|[dsdp-dd-dev] Getting "default" feedback from the executor thread when an uncaught exception occurs|
I would like to ask a question about exception handling in DSF Sequences (and, more generally, in asynchronous DSF operations).
What is the default exception handling policy that DSF uses? (We are using DSF release 1.0 maintenance.)
I am asking this because in our implementation it seems that a generic Exception thrown during the backend startup sequence can freeze the whole sequence without any visible feedback. This seems to happen only if the exception is unhandled by the sequence code, so it gets uncaught up to the sequence executor.
The only way to notice that an exception has occurred is to set an exception breakpoint: stepping through the exception return path shows that it gets to the FutureTask.run() and it is ignored there, with the executor only shifting to the next task – thus leaving the request monitor incomplete and freezing the sequence.
Does the DSF API provide a “last-resort” way of getting uncaught exceptions, at least to show that they have occurred?
Back to the top