title: Camel RabbitMQ creates a generated queue in addition to the routing the msg to the queue
body: <p>I have an exchange setup amq.topic and in there I have a routing key that is pointing to my key.  </p>
  
  <p>I have a route defined with a rest endpoint.  I make a call to that endpoint with a body as json {"sample" : "sample"}.</p>
  
  <pre><code>  rest("myendpoint")
                  .post()
                  .route()
                  .routeId(ROUTE_ID)
                  .log(ROUTE_ID + " started.")
                  .convertBodyTo(String.class)
                  .log("Receiving request with body=${body}")
                  .to("rabbitmq://rabbiturl:port/amq.topic?connectionFactory=rabbitmqConnectionFactory&amp;autoDelete=false&amp;routingKey=myroutingkey&amp;declare=false&amp;exchangeType=topic")                
                  .log(ROUTE_ID + " ended.")
                  .end();
  </code></pre>
  
  <p>This accomplishes what I want to: the body of my rest call will be sent to the topic exchange of which will go to my queue based on the routing key.</p>
  
  <p>The problem: It also create an auto-generated queue</p>
  
  <pre><code> [                qtp86171426-28] RabbitMQProducer               INFO  Starting reply manager service RabbitMQReplyManagerTimeoutChecker[amq.topic]
  [                qtp86171426-28] ReplyManagerSupport            INFO  Using temporary queue name: amq.gen-JGF0CKioQ6_MLA9uBNIOOQ
  [                qtp86171426-28] CorrelationTimeoutMap          INFO  in putIfAbsent with key Camel-ID-L-VC-10050-58983-1467158153454-0-3
  [nagerTimeoutChecker[amq.topic]] TemporaryQueueReplyHandler     INFO  in onTimeout with correlationId= Camel-ID-L-VC-10050-58983-1467158153454-0-3
  [nagerTimeoutChecker[amq.topic]] ReplyManagerSupport            WARN  Timeout occurred after 20000 millis waiting for reply message with correlationID [Camel-ID-L-VC-10050-58983-1467158153454-0-3] on destination amq.gen-JGF0CKioQ6_MLA9uBNIOOQ. Setting ExchangeTimedOutException on (MessageId: ID-L-VC-10050-58983-1467158153454-0-2 on ExchangeId: ID-L-VC-10050-58983-1467158153454-0-1) and continue routing.
  </code></pre>
  
  <p>I have tried skipqueuedeclare &amp; skipexchangedeclare and am running out of ideas of why it is generating the queue.  Does anyone have any ideas?</p>