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

STOMP 1.1 protocol support for client [SPR-14391] #18964

Closed
spring-projects-issues opened this issue Jun 23, 2016 · 2 comments
Closed

STOMP 1.1 protocol support for client [SPR-14391] #18964

spring-projects-issues opened this issue Jun 23, 2016 · 2 comments

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Jun 23, 2016

Achmad Nasirudin Sandi opened SPR-14391 and commented

I am working with spring spring-boot-starter-websocket 1.4.0.M3 and using stomp over websocket client to ack my message. Yet, when I tried to connect the broker to Apache ActiveMQ 5.13.3, I got this:

: org.apache.activemq.transport.stomp.ProtocolException: Unexpected ACK received for message-id [null]
 WARN | Exception occurred processing:
ACK
id:ID:moi-laptop-2-34547-1466655368399-10:1:1:1:1

When I checked the supported version in ActiveMQ https://stomp.github.io/implementations.html, it only support version up to 1.1. Could you please add suport for previous version also for STOMP client?

Thank you.


Affects: 4.3 GA

Referenced from: commits ebdc770

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jun 23, 2016

Rossen Stoyanchev commented

Okay it looks like in STOMP 1.2 the message-id header for the ACK frame was renamed to just id so we have to check the STOMP version in the CONNECTED frame.

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jun 27, 2016

Rossen Stoyanchev commented

I've made a change for 4.3.1.

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