Header x-stream-max-segment-size-bytes gets not transmitted during subscription
h0jeZvgoxFepBQ2C opened this issue · 3 comments
I really try to get my head around following issue:
I have a queue named "public" which works fine in general. Now I tried to recreate it with the keyword x-stream-max-segment-size-bytes set, but it seems that this header doesn't get sent?
In my rabbitmq dashboard I can see that the queue has been created with this keyword:
But I get the error message that stompjs value was none?
Header params:
All other header params work well?
Any ideas?
Connecting via the ruby bunny gem works fine with x-stream-max-segment-size-bytes:1048576 set.
As per the log, the library is sending the header to the broker, so, the library may not be able to help much here.
Apologies no concrete help, just a few suggestions:
- Please check https://www.rabbitmq.com/stomp.html if not checked already.
- Occasionally, RabbitMQ does not support every features via STOMP than AMQP (which Ruby Bunny uses).
- Sometimes, at our company, we will create an exchnage or a queue using Bunny and then use it with STOMP. See, if that similifies the task for you.
- Ask as a question at StackOverflow. People with knowledge of RabbitMQ might be able to help.
Thanks for your reply,
we were using bunny + stompjs successfully already, it's just not working when I add the x-stream-max-segment-size-bytes declaration. Without it everything works fine on all sides.
So my best guess would be that the rabbitmq stomp or webstomp plugin filters this header..?
Looks like this was a bug and has been fixed: rabbitmq/rabbitmq-server#7605