Error paths for scheduled asynchronous methods #30718
Labels
Milestone
Comments
njr-11
added
the
Epic
njr-11
added a commit
to njr-11/open-liberty
that referenced
this issue
Feb 4, 2025
njr-11
added a commit
to njr-11/open-liberty
that referenced
this issue
Feb 4, 2025
…c method and exception completion of future
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When an execution of a scheduled asynchronous method fails with an exception, error, or other exceptional completion, no further executions should be scheduled, and the application needs the correct exception or error reported back when invoking get or join to obtain the status or result of the scheduled asynchronous method. This allows the application to properly react to the error, possibly by retrying/rescheduling.
We also need better trace on these paths to figure out what has gone wrong.
The text was updated successfully, but these errors were encountered: