[rabbitmq-discuss] RabbitMQ with STOMP, messages that are requested after 10 min delay doesn't work there after
fahad007 at gmail.com
Sun Oct 6 13:56:42 BST 2013
I have a rabbitmq setup that uses STOMP as a means to talk to end user
devices (android/websockets in the browser). The situation is there is a
problem if I wait for 10 mins between messages and then try to send some
message from server -> client, the client never receives it. I tried this
in 2 systems, with different behaviors,
- Dev VM - 4 core windows server
- The issue gets reproduced very very rarely but happens after
working for an hour or so
- Test VM - 1 core windows server
- The issue gets reproduced often immediately after 10 mins.
I believe its a configuration issue, because as soon as I close my app (in
android) or refresh the browser, it works immediately. Does this mean,
rabbitmq somehow marks a STOMP queue stale after some timeout?
Some more points to add up the discussion,
- I use STOMP 1.0 definition in the header
- No headers for heart-beating (its disabled by default in the protocol,
so I dint add it in the header), just thought to mention it.
- All messages are send using UTF8 format
The server has a AMQP queue handle which is used to send messages as UTF8
format, client receives it via STOMP but listening over amqp queue by using
the standards mentioned in the documentation. This works whenever I have a
new connection or restart the app, but fails after I wait for 10-15 mins,
Is it something related to the 1-core machine? Does Erlang has to do
anything here? or rabbitmq marks the STOMP queue stale? This never happened
before when I used only AMQP queues, (point to remember is I can't use AMQP
in my end client apps as its very big to implement + I use the same
messaging layer over the web using websockets).
Any ideas or things that I need to check would be really helpful.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss