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

Unhandled JMS exceptions are not always recorded as observation errors #32458

Closed
bclozel opened this issue Mar 15, 2024 · 0 comments
Closed

Unhandled JMS exceptions are not always recorded as observation errors #32458

bclozel opened this issue Mar 15, 2024 · 0 comments
Assignees
Labels
in: messaging Issues in messaging modules (jms, messaging) theme: observability An issue related to observability and tracing type: bug A general bug
Milestone

Comments

@bclozel
Copy link
Member

bclozel commented Mar 15, 2024

When using the DefaultMessageListenerContainer implementation, JMS exceptions that are rethrown by configured ErrorHandler are not recorded as errors by the JMS observation.

@bclozel bclozel added in: messaging Issues in messaging modules (jms, messaging) type: bug A general bug theme: observability An issue related to observability and tracing labels Mar 15, 2024
@bclozel bclozel self-assigned this Mar 15, 2024
@bclozel bclozel added this to the 6.1.6 milestone Mar 15, 2024
bclozel added a commit that referenced this issue Mar 18, 2024
bclozel added a commit that referenced this issue Mar 18, 2024
There is no way to consistently test this use case because listener
container implementations have different behavior for unhandled errors
and might retry or close the container altogether.

See gh-32458
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: messaging Issues in messaging modules (jms, messaging) theme: observability An issue related to observability and tracing type: bug A general bug
Projects
None yet
Development

No branches or pull requests

1 participant