blocks|key|1555206|text|队列由rabbitmq管理。消费者无法管理它们。使用者可以使用这组或那组参数来创建/声明队列。其中一个参数是"排他性"，表示只有当前连接可以访问队列。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1555207|虚拟主机是在连接时指定的，而不是像您所说的在绑定时指定的，所以您需要在一个单独的线程中这样做。或者重组你们的主机。|1555208|也许您不需要这样做，只要有路由密钥，并且声明队列是排他性的，而不是'/app‘虚拟看台，就可以有一个扇出交换而不是’/公用‘vhost。|1555209|entityMap|0|LINK|mutability|MUTABLE|url|http://www.rabbitmq.com/amqp-0-9-1-reference.html#queue.declare.exclusive^0|1J|3|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

The queues are managed by rabbitmq. Consumers cannot manage them. Consumers may create/declare the queues with this or that set of parameters. One of those parameters is "<a href="http://www.rabbitmq.com/amqp-0-9-1-reference.html#queue.declare.exclusive" rel="nofollow noreferrer">exclusive</a>", indicating that only current connection may access the queue.

Virtual host is specified at connecting, not at binding as you said, so you would need to do this in a separate thread. Either that or re-organize you vhosts.

Maybe you don't need any of it and it would be sufficient to have routing keys and declare queues exclusive instead of the '/app' vhostand have a fanout exchange instead of the '/common' vhost.

blocks|key|1555215|text|在连接字符串中指定虚拟主机(vhost)。Vhost使在一个代理上分离应用程序成为可能。您可以将用户、交换、队列等隔离到一个特定的vhost。您可以将环境分开，例如，生产到一个vhost，并在同一个代理中暂存到另一个vhost，而不是设置多个代理。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1555216|https://devcenter.heroku.com/articles/cloudamqp#separate-applications|offset|length|1555217|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1X|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

You specify the Virtual Hosts (vhost) in the connection string. Vhosts makes it possible to separate applications on one broker. You can isolate users, exchanges, queues etc to one specific vhost. You can separate environments, e.g. production to one vhost and staging to another vhost within the same broker, instead of setting up multiple brokers. 

<a href="https://devcenter.heroku.com/articles/cloudamqp#separate-applications" rel="nofollow noreferrer">https://devcenter.heroku.com/articles/cloudamqp#separate-applications</a>

blocks|key|1752568|text|我想要达到你所要求的，你需要使用联邦。我也有同样的领域问题。一个交换，然后使用不同队列的不同应用程序。如果我是对的，这一步是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1752569|交换一个=>联邦到交换1/2/3/4/.这些交换有不同的交换方式。|1752570|为不同的应用程序创建不同的vhost和用户。允许访问这些vhost到不同的交换(Exchange+1/2/3/4/)|1752571|创建不同的队列来绑定不同的Exchange+1/2/3/4/|1752572|明白了吗？|1752573|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I think to achieve what you asked you need to use federation.
I have the same domain problem.
One exchange and then different application consuming from different queues.
If I am right the step are:

Exchange A => federation To Exchange 1/2/3/4/... these exchange have a different vhost each other.

create different vhost and user for different applications.
Give the access to these vhost to different exchange (Exchange 1/2/3/4/)

create different queue to bind from the different Exchange 1/2/3/4/

Is this clear?

We have an app that publishing to single exchange (using amqp). Additionally we have a number of apps interested in consuming messages from this exchange. To that end, they create queues and bindings from the queues to the exchange. 

We would like to ensure that each app's queues and bindings can only be managed by that app and the user that the app connects with. I envisaged using virtual hosts so that the exchange sat in a <code>/common</code> virtual host which each app's user had read access to and each app's queues and bindings lived in their own <code>/&lt;app&gt;</code> virtual host which the user had full access to. 

The documentation, however, suggests that a user cannot access more than one virtual host simultaneously within a channel and the API doesn't provide an option to specify virtual host as part of bindQueue(). 

Is there a way to achieve this?

How to configure RabbitMq so that multiple apps can manage their own queues and bindings to a shared exchange

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们有一个应用程序，发布到单一的交换(使用amqp)。此外，我们有许多应用程序对使用来自这个交换的消息感兴趣。为此，它们从队列创建队列和绑定到交换。我们希望确保每个应用程序的队列和绑定只能由应用程序和应用程序连接的用户来管理。我设想使用虚拟主机，这样交换机就位于一个/common虚拟主机中，每个应用程序的用户都可以读取...

问如何配置RabbitMq，以便多个应用程序可以管理自己的队列和绑定到共享交换
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何配置RabbitMq，以便多个应用程序可以管理自己的队列和绑定到共享交换EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何配置RabbitMq，以便多个应用程序可以管理自己的队列和绑定到共享交换
EN