{"action":"opened","issue":{"url":"https://api.github.com/repos/spring-cloud/spring-cloud-bus/issues/21","labels_url":"https://api.github.com/repos/spring-cloud/spring-cloud-bus/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/spring-cloud/spring-cloud-bus/issues/21/comments","events_url":"https://api.github.com/repos/spring-cloud/spring-cloud-bus/issues/21/events","html_url":"https://github.com/spring-cloud/spring-cloud-bus/issues/21","id":112656736,"number":21,"title":"Problem using org.springframework.cloud.stream.binder.rabbit.RabbitMessageChannelBinder to set up the subscribers on the Spring Cloud Bus","user":{"login":"TabberGit","id":1644417,"avatar_url":"https://avatars.githubusercontent.com/u/1644417?v=3","gravatar_id":"","url":"https://api.github.com/users/TabberGit","html_url":"https://github.com/TabberGit","followers_url":"https://api.github.com/users/TabberGit/followers","following_url":"https://api.github.com/users/TabberGit/following{/other_user}","gists_url":"https://api.github.com/users/TabberGit/gists{/gist_id}","starred_url":"https://api.github.com/users/TabberGit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/TabberGit/subscriptions","organizations_url":"https://api.github.com/users/TabberGit/orgs","repos_url":"https://api.github.com/users/TabberGit/repos","events_url":"https://api.github.com/users/TabberGit/events{/privacy}","received_events_url":"https://api.github.com/users/TabberGit/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-10-21T18:59:37Z","updated_at":"2015-10-21T18:59:37Z","closed_at":null,"body":"I have a system with three components.  A ConfigServer, ServiceA, and ServiceB.  When they register against the Spring Cloud Bus, they all end up being tied as consumers to the same queue registered against the binder.springCloudBus queue.  This causes round-robining of messages, where only one service will actually be delivered a notification on the bus.\r\n\r\nIn bindPubSubConsumer(String name, MessageChannel moduleInputChannel, Properties properties), it is not possible to give each queue a different name and have it bound to the same exchange.\r\n\r\n     ConfigServer ----------------\r\n                                 |\r\n                        ------------------\r\n    ServiceA ---------- | SpringCloudBus |\r\n                        ------------------\r\n                                 |\r\n    ServiceB ---------------------\r\n\r\nExchange:  binder.topic.springCloudBus\r\nQueue: binder.springCloudBus\r\n\r\nThe SINGLE queue ends up with three consumers.\r\n\r\nThis was discovered when we were working with the /refresh capabilities of spring-cloud.  In the scenario above, the refresh message is not passed to all necessary parties."}}