-
Notifications
You must be signed in to change notification settings - Fork 95
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
Support RECEIPT for SUBSCRIBE operations #40
Comments
@rp42 Do you have an example using the receipt SubscribeOpt.Header? |
Here you go: The subscription channel gets closed when go-stomp receives the subscription receipt from what I can work out, so there is no way of receiving the messages from the subscription. If I remove the header then the subscription works ok, but doesn't wait for the server to process the subscribe frame. |
It was a while ago now, but I think we stuck with using a time delay to ensure that the message had been processed by the server. This was acceptable for our real world use case, but it made the test cases run a bit slow. |
okay, I see. thanks a lot for your prompt reply! |
I think I found the reason: The subscription has its own Line 174 in 123cce4
Could @thomaslee or @worg or anyone who knows the purpose of these lines comment on this? :) Thanks a lot for your help in advance. |
As far as I can tell go-stomp doesn't support receipts for subscribe operations. I haven't seen a SubscribeOpt for this. When I manually add the header using
stomp.SubscribeOpt.Header
, I do see a RECEIPT from from the server, but this looks to close the Subscription's channel in go-stomp.I'm working with a system where you subscribe to a topic and then trigger an operation that posts messages to the topic. Unless I add a sleep in, I can lose the initial messages that are posted.
The text was updated successfully, but these errors were encountered: