Hello,
Actually I'm using jms:outbound-gateway to create a request-reply service with spring integration (2.0.5) ; it works fine. But when I've decided to monitor with JConsole my active-mq broker, I've noticed tempQueues are increasing for ever.

Code:
<beans:bean id="queue.myService.entry" class="org.apache.activemq.command.ActiveMQQueue">
  <beans:constructor-arg value="queue.myService.entry"/>
</beans:bean>

<beans:bean id="queue.myService.exit" class="org.apache.activemq.command.ActiveMQQueue">
  <beans:constructor-arg value="queue.myService.exit/>
</beans:bean>

<jms:inbound-gateway id="myService" connection-factory="brokerDMZ"
  request-destination="queue.myService.entry"
  request-channel="myService.channel"
  reply-timeout="15000" 
  reply-time-to-live="15000"
  request-timeout="15000" 
  concurrent-consumers="100"
  max-concurrent-consumers="100"
  max-messages-per-task="100" />
                           
 <channel id="myService.channel"  />

 <jms:outbound-gateway id="myServiceExit" connection-factory="brokerIntranet"
   request-destination="queue.myService.exit"  
   request-channel="myService.channel"
   reply-timeout="15000"   
   request-timeout="15000" 
   time-to-live="15000" 
   receive-timeout="15000" />
It seems that jms:outbound-gateway creates temporary queues in order to get the reply, but then doesn't delete them.
I can see it in Jconsole in the tempQueues list.