[rabbitmq-discuss] Default vhost and Http API

Tony Garnock-Jones tonygarnockjones+rabbitmq at gmail.com
Tue Mar 27 20:30:57 BST 2012

Hi Stone,

Sorry, I don't quite understand: how are you declaring the queue? Is it
with the Erlang client across an AMQP network link? Or some other client
across an AMQP network link? Or is it with the Erlang client in the same
Erlang cluster as the server?

If it's across an AMQP network link, perhaps you could paste in tcpdump
output showing the bytes sent on the wire during the queue.declare. That
way it's crystal clear what's happening.

If it's not across an AMQP link then yeah, perhaps the Erlang client needs
more type-assertionish things in it :-)


2012/3/27 stone <zmstone at gmail.com>

> Hi Tony,
> I didn't save the scene, didn't really look into the fault client code.
> Just had a quick test, reproduced by using term_to_binary instead of
> list_to_binary to make the queue name in Erlang client.
> Perhaps this WAS exactly the case from the other day. shame :)
> I simply though it was UTF used in that case because the crash report has
> "utf" in it.
> http://localhost:55672/#/queues
> {error,{exit,{ucs,{bad_utf8_character_code}},
>              [{xmerl_ucs,from_utf8,1},
>               {mochijson2,json_encode_string,2},
>               {mochijson2,'-json_encode_proplist/2-fun-0-',3},
>               {lists,foldl,3},
>               {mochijson2,json_encode_proplist,2},
>               {mochijson2,'-json_encode_array/2-fun-0-',3},
>               {lists,foldl,3},
>               {mochijson2,json_encode_array,2}]}}
> Anyway, perhaps  rabbit-server should have the name validated before
> allowing the declaration.
> BRs
> /stone
> 在 2012年3月27日 下午7:27,Tony Garnock-Jones <
> tonygarnockjones+rabbitmq at gmail.com>写道:
>> On 27 March 2012 12:50, stone <zmstone at gmail.com> wrote:
>>> The other day, we accidentally created queues and bindings with UTF
>>> characters in the names.
>>> Then the management web GUI crashed (on mochiweb level if i remember
>>> correctly), so we couldn't delete the queu on GUI.
>>> And there was no CLI to do it, we actually had to reset the node to get
>>> rid of the bad-naming queues.
>> A test case would be extremely useful and welcome! Can you remember the
>> exact bytes used in the names? And which GUI actions caused the crashes?
>> Regards,
>>   Tony

Tony Garnock-Jones
tonygarnockjones at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120327/2d52e851/attachment.htm>

More information about the rabbitmq-discuss mailing list