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

Revise JCA MessageEndpoint exception logging and propagation [SPR-16717] #21258

Closed
spring-projects-issues opened this issue Apr 11, 2018 · 0 comments
Assignees
Labels
in: messaging Issues in messaging modules (jms, messaging) status: backported An issue that has been backported to maintenance branches type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Juergen Hoeller opened SPR-16717 and commented

As noted on the referenced pull request, JmsMessageEndpoint as well as GenericMessageEndpoint deal with exceptions in a suboptimal way... not only in the finally block but generally when propagating exceptions from onMessage without any logging. This is worth revisiting according to JCA exception handling limitations.


Affects: 4.3.16, 5.0.5

Reference URL: #1784

Backported to: 4.3.17

@spring-projects-issues spring-projects-issues added in: messaging Issues in messaging modules (jms, messaging) status: backported An issue that has been backported to maintenance branches type: enhancement A general enhancement labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 5.0.6 milestone Jan 11, 2019
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) status: backported An issue that has been backported to maintenance branches type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants