Question

我是Spring云流和rabbitmq的新手。最近我在开始我的一个微服务后得到了一个例外。它声明无法注册对象，因为它已经注册，我认为这是因为为每个通道分配的组名，请检查异常，

 2018-05-28 10:01:38.420 ERROR 10244 --- [ask-scheduler-2] o.s.cloud.stream.binding.BindingService  : Failed to create consumer binding; retrying in 30 seconds
 org.springframework.cloud.stream.binder.BinderException: Exception thrown while starting consumer: 
     at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder.doBindConsumer(AbstractMessageChannelBinder.java:326) ~[spring-cloud-stream-2.0.0.RC3.jar:2.0.0.RC3]
     at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder.doBindConsumer(AbstractMessageChannelBinder.java:77) ~[spring-cloud-stream-2.0.0.RC3.jar:2.0.0.RC3]
     at org.springframework.cloud.stream.binder.AbstractBinder.bindConsumer(AbstractBinder.java:129) ~[spring-cloud-stream-2.0.0.RC3.jar:2.0.0.RC3]
     at org.springframework.cloud.stream.binding.BindingService.lambda$rescheduleConsumerBinding$0(BindingService.java:154) ~[spring-cloud-stream-2.0.0.RC3.jar:2.0.0.RC3]
     at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[spring-context-5.0.5.RELEASE.jar:5.0.5.RELEASE]
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[na:1.8.0_101]
     at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_101]
     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) ~[na:1.8.0_101]
     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) ~[na:1.8.0_101]
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_101]
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_101]
     at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_101]
 Caused by: java.lang.IllegalStateException: Could not register object [org.springframework.integration.handler.advice.ErrorMessageSendingRecoverer@70a0362b] under bean name 'org.nets.ups.alertService.errors.recoverer': there is already object [org.springframework.integration.handler.advice.ErrorMessageSendingRecoverer@cfd5cd2] bound
     at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.registerSingleton(DefaultSingletonBeanRegistry.java:126) ~[spring-beans-5.0.5.RELEASE.jar:5.0.5.RELEASE]
     at org.springframework.beans.factory.support.DefaultListableBeanFactory.registerSingleton(DefaultListableBeanFactory.java:932) ~[spring-beans-5.0.5.RELEASE.jar:5.0.5.RELEASE]
     at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder.registerErrorInfrastructure(AbstractMessageChannelBinder.java:519) ~[spring-cloud-stream-2.0.0.RC3.jar:2.0.0.RC3]
     at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder.registerErrorInfrastructure(AbstractMessageChannelBinder.java:478) ~[spring-cloud-stream-2.0.0.RC3.jar:2.0.0.RC3]
     at org.springframework.cloud.stream.binder.rabbit.RabbitMessageChannelBinder.createConsumerEndpoint(RabbitMessageChannelBinder.java:391) ~[spring-cloud-stream-binder-rabbit-2.0.0.RC3.jar:2.0.0.RC3]
     at org.springframework.cloud.stream.binder.rabbit.RabbitMessageChannelBinder.createConsumerEndpoint(RabbitMessageChannelBinder.java:104) ~[spring-cloud-stream-binder-rabbit-2.0.0.RC3.jar:2.0.0.RC3]
     at org.springframework.cloud.stream.binder.AbstractMessageChannelBinder.doBindConsumer(AbstractMessageChannelBinder.java:279) ~[spring-cloud-stream-2.0.0.RC3.jar:2.0.0.RC3]
     ... 11 common frames omitted

当我在这个微服务中为每个频道分配相同的组名时，就会发生这种情况。像这样的东西，

 spring:
   cloud:
     stream:
       bindings:
         useroperation:
           destination: org.nets.ups
           content-type: application/json
           group: alertService
         departmentoperation:
           destination: org.nets.ups
           content-type: application/json
           group: alertService
         roleoperation:
           destination: org.nets.ups
           content-type: application/json
           group: alertService
         rabbit:
           bindings:
             useroperation:
               consumer:
                 bindingRoutingKey: 'adminservice.user.#'
             departmentoperation:
                consumer:
                  bindingRoutingKey: 'adminservice.department.#'
             roleoperation:
               consumer:
                 bindingRoutingKey: 'adminservice.role.#'

我可以通过删除组名来删除此例外，但组名将始终是获得已知队列名称和更好负载平衡的完美选择。如果我做错了或者你需要java代码（它只是每个频道的流监听器），请告诉我。

谢谢。

Answer 1

~~你的YAML表现不佳。它应该是......~~

spring: cloud: stream: bindings: useroperation: destination: org.nets.ups content-type: application/json group: alertService departmentoperation: destination: org.nets.ups content-type: application/json group: alertService roleoperation: destination: org.nets.ups content-type: application/json group: alertService rabbit: bindings: useroperation: consumer: bindingRoutingKey: 'adminservice.user.#' departmentoperation: consumer: bindingRoutingKey: 'adminservice.department.#' roleoperation: consumer: bindingRoutingKey: 'adminservice.role.#'

修改

哦，我明白了。是的，看起来像一个bug;如果多个绑定使用相同的目标和组，我们无法注册错误基础结构。请打开针对spring-cloud-stream的github问题。我们应该添加另一个属性以允许使用同一个组。

解决方法是在每个地方使用不同的小组。

启动使用者时抛出异常 - （无法为微服务中的不同通道分配相同的组名）

1 个答案: