[rabbitmq-discuss] federation Issues
KGanann at kroll.com
Fri Jun 27 00:27:18 BST 2014
We just upgraded from 3.2.1 to 3.3.4 and federation died on us. Looking at the cluster, it appears some... overenthusiastic dev renamed the cluster, and now when federation creates new linkages, it creates them as clustername:vHost:queue, rather than usertoken:vHost:queue. Also, on the federation upstreams, the parameter field seems to have vanished, so I can't update the user tokens for specific vHosts. I've been going through the patch notes - is this intentional, or is something else going on? And can I just remove the cluster name? I've tried deleting the old dynamically created fed stuff so that it gets recreated, but the new stuff just doesn't seem to work. Any help is appreciated.
This communication contains information that is confidential,
proprietary in nature, and may also be attorney-client privileged
and/or work product privileged. It is for the exclusive use of the
intended recipient(s). If you are not the intended recipient(s) or
the person responsible for delivering it to the intended
recipient(s), please note that any form of dissemination,
distribution or copying of this communication is strictly
prohibited and may be unlawful. If you have received this
communication in error, please immediately notify the sender by replying
to this message and delete this email immediately. Thank you for your cooperation.
Please be advised that neither Altegrity, its affiliates, its employees
or agents accept liability for any errors, omissions or damages
caused by delays of receipt or by any virus infection in this
message or its attachments, or which may otherwise arise as a
result of this e-mail transmission.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss