No, queue names can still have periods in.
ISTR the only way you can get a not-found when declaring a queue is in a
clustering situation, if the queue exists on a node which is not
running. Does that sound like it could be a possibility?
Staff Engineer, RabbitMQ
SpringSource, a division of VMware
rabbitmq-discuss mailing list
It means pretty much what it says. rabbitmqctl cluster is used to set up
a cluster, and should only be used when the rabbit application has been
stopped (which stops mnesia too). See:
The command you're looking for is:
By the way, it's a good idea to keep the mailing list CCed so that if
other people have the same problem they can find the thread...
> (class_id, method_id))amqplib.client_0_8.exceptions.AMQPChannelException:
(404, u"NOT_FOUND - no queue 'st.test-o.com_q' in vhost '/'", (50, 10),
'Channel.queue_declare')----------------------I've changed st.test-o.com_q to
st_test-o_com_q and had no problem... periods are not allowed in queue names
now? Nico Césarhttp://blog.nicocesar.com
We just had the same problem, which apparently was due to having some residues
of the old (durable) queues from the previous install present; in particular,
the old queues were visible, whereas
showed no queues present. It was then possible to declare new queues, but not
queues with the same name as the ones that existed before.
The problem was fixable by
after which the old bindings were gone and the queueus could be declared again.
Iver Odin Kvello