[rabbitmq-discuss] Null messages in RabbitMq 2.6.1. Can't recover
alfonso.pantoja at gmail.com
Tue Nov 29 11:08:58 GMT 2011
You were right, the problem was not related with the headers.
In our custom ejabberd module we were not sending the messages in binary
format to RabbitMq.
Thank you very much
El 29 de noviembre de 2011 10:42, Alexandru Scvorţov <alexandru at rabbitmq.com
> Hi Alfonso,
> > I've noticed that the messages created in that
> > module can't be recovered using the .NET API (2.6.1 and 126.96.36.199)
> > because all messages are received as "null"
> > (using subscription.Next(millisecondsTimeout, out message))
> From the docs:
> "Returns false only if the timeout expires before either a delivery
> appears or the end-of-stream is reached. If false is returned, the out
> parameter "result" is set to null, but LatestEvent is not updated."
> What value are you using for the timeout? Does that function return
> true when the message is set to null?
> > It seems is the
> > way they are sent (maybe AMQP header properties?)...
> It's probably not related to the headers.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss