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

StompSubProtocolHandler makes the same assumption about header accessor as SimpleBrokerMessageHandler used to [SPR-14791] #19357

Closed
spring-projects-issues opened this issue Oct 10, 2016 · 1 comment

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Oct 10, 2016

Dave Syer opened SPR-14791 and commented

Just like in #18851, StompSubProtocolHandler.getStompHeaderAccessor() makes an assumption about the content of the Message it is processing. In particular, it assumes that there is a MessageHeaderAccessor, but that isn't necessarily the case, for instance if the user has added a ChannelInterceptor that rebuilds the message and adds some headers by calling MessageBuilder.fromMessage(...).build().


Affects: 4.2.8, 4.3.3

Issue Links:

  • #18851 SimpleBrokerMessageHandler makes an assertion about the type of the MessageHeaderAccessor, but doesn't seem to care

Referenced from: commits f5cd538, aff5d21, 66722af

Backported to: 4.2.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants