Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Populate Text(58) field when rejectMessageOnUnhandledException=true #851

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mgatny
Copy link

@mgatny mgatny commented Aug 2, 2024

Supersedes #667
refs #639

If rejectMessageOnUnhandledException=true and an unhandled exception is thrown from the fromCallback(), include the exception message in the Text(58) field of the resulting Reject or BusinessMessageReject.

@chrjohn chrjohn changed the title Populate Text(58) field when rejectMessageOnUnhandledException=true Populate Text(58) field when rejectMessageOnUnhandledException=true Aug 5, 2024
@chrjohn
Copy link
Member

chrjohn commented Aug 5, 2024

@mgatny thanks for the PR.
The only thing that troubles me is that it might reveal internal information about the application e.g. "Out of memory" or similar. What do you think about adding a prefix like "error: " or "problem: " to the Text field so that users could possibly filter out such messages in their toAdmin() or toApp() callbacks?

If rejectMessageOnUnhandledException=true and an unhandled exception is
thrown from the fromCallback(), include the exception message in the
Text(58) field of the resulting Reject or BusinessMessageReject.
@mgatny mgatny force-pushed the add-reason-to-unhandled-exception-reject branch from ca0e9d8 to c635430 Compare September 26, 2024 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants