Skip to content

NullPointerException possible in DefaultSubscriptionRegistry [SPR-13204] #17796

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.

Sign up for GitHub

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

Jump to bottom
Closed
spring-projects-issues opened this issue Jul 6, 2015 · 0 comments
Closed

NullPointerException possible in DefaultSubscriptionRegistry [SPR-13204] #17796

spring-projects-issues opened this issue Jul 6, 2015 · 0 comments
Assignees
@rstoyanchev
Labels
in: messaging Issues in messaging modules (jms, messaging) type: bug A general bug
Milestone
4.2 RC3

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Jul 6, 2015 •
edited
Loading

Rossen Stoyanchev opened SPR-13204 and commented

#17482 introduced support for a selector header expression on SUBSCRIBE frames so that messages from the destination cache are further filtered based on that selector expression. During that additional filtering a NullPointerException is possible if unsubscribe takes place concurrently and the session subscription has been removed.

Affects: 4.2 RC1

Issue Links:

Referenced from: commits 0b43e4e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rstoyanchev rstoyanchev

Labels
in: messaging Issues in messaging modules (jms, messaging) type: bug A general bug
Projects
None yet
Milestone
4.2 RC3
Development

No branches or pull requests
2 participants
@rstoyanchev @spring-projects-issues