That is strange because I write messages to queues on exchanges where both are already declared and that works.
On Thu, Feb 25, 2016 at 1:43 PM, FabianChanton [via Camel] <ml-node+s465427n5778273...@n5.nabble.com> wrote: > I tried what I described without camel, by directly using the RabbitMQ Java > Client. By directly using the client I am able to declare a queue on the > default exchange. > > It seems the problem lies in the method declareExchangeAndQueue of the > RabbitMQEndpoint. This method calls channel.exchangeDeclare(...) if declare > is true. It does not check if the exchange already exists or if it is the > default exchange. > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > http://camel.465427.n5.nabble.com/RabbitMQ-Declare-queue-on-existing-exchange-tp5778263p5778273.html > To start a new topic under Camel - Users, email > ml-node+s465427n465428...@n5.nabble.com > To unsubscribe from Camel - Users, click here. > NAML -- View this message in context: http://camel.465427.n5.nabble.com/RabbitMQ-Declare-queue-on-existing-exchange-tp5778263p5778274.html Sent from the Camel - Users mailing list archive at Nabble.com.
