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

4.x speaks STOMP 1.2 with 1.1 selected #1

Closed
bra-fsn opened this issue Nov 21, 2013 · 1 comment
Closed

4.x speaks STOMP 1.2 with 1.1 selected #1

bra-fsn opened this issue Nov 21, 2013 · 1 comment
Labels

Comments

@bra-fsn
Copy link

bra-fsn commented Nov 21, 2013

Hi,

Installed stomp.py via pip and now all of my previously working programs are broken... I've adapted one of them to the new API, but I can't even do an ACK (ActiveMQ 5.9), I get the following error:
"ACK received without a message-id to acknowledge!"
Indeed, this version sends the message-id as id, which is not valid in STOMP 1.[01].

Overriding the default version (1.1) to 1.2, I get the following:
"Unexpected ACK received for message-id [null]"
while stomp.py sent the following ACK:
INFO:stomp.py:Sending frame ['ACK', '\n', 'id:ID\cmq00d-57544-1385032044164-5\c486\c-1\c1\c3\n', '\n', '\x00']

Also, <1.2 needs the subscription header, while there is no way to specify that with the current version if I'm right (passing a headers structure to ack and other calls is not possible).

Could you please test and fix these issues?

Thanks,

@jasonrbriggs
Copy link
Owner

I couldn't get activemq working on my test server, but I've fixed the code and tested with apollo. Seems to work okay for me. Try it out (version 4.0.4) and let me know how it goes.

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

No branches or pull requests

2 participants