Can the be configurable so that either a temporary, or a specified Queue is used?

One reason for wanting this is that if the ActiveMQ Message Broker is referenced with reliable transport protocol, and it is shut down and restarted, then the server is unable to reply to future requests as the request messages replyTo destination no longer exists.

• Exception occured: Cannot publish to a deleted Destination: TemporaryQueue-
  Unknown macro: {TD{ID:dmpeintw5376-1842-1122422802781-1:0}TD}
  ID:dmpeintw5376-1842-1122422802781-9:0
  javax.jms.JMSException: Cannot publish to a deleted Destination: TemporaryQueue-
  Unknown macro: {TD{ID:dmpeintw5376-1842-1122422802781-1:0}TD}
  ID:dmpeintw5376-1842-1122422802781-9:0
  at org.activemq.ActiveMQConnection.validateDestination(ActiveMQConnection.java:2099)
  at org.activemq.ActiveMQSession.send(ActiveMQSession.java:1392)
  at org.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:426)
  at org.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:390)

I'm not sure if this is an ActiveMQ bug or not, but I think it would be useful to be able to specify a reply queue to use instead of using a temporary queue.

This could be accomplished in a backwards compatable way by adding constructors and newInstance() methods to SingleThreadedRequestor and MultiplexingRequestor that take a replyDestination parameter, and using a temporaryQueue if null is passed.