Noticed that the same queues/bindings where being created twice because of the issue in the title. This happens because first SpringAMQPExecutor.execute(final Runnable task) is called and then SpringAMQPExecutor.execute(final Runnable task, long startTimeout). If comment out the second method the problem goes away. Was there a reason for adding it in the first place?
Noticed that the same queues/bindings where being created twice because of the issue in the title. This happens because first SpringAMQPExecutor.execute(final Runnable task) is called and then SpringAMQPExecutor.execute(final Runnable task, long startTimeout). If comment out the second method the problem goes away. Was there a reason for adding it in the first place?