I have found the problem. Simple typo... The line "session.CreateConsumer(destination))" was assigning the wrong destination, it should have been the temporary queue which was created earlier.
-- View this message in context: http://activemq.2283324.n4.nabble.com/No-response-being-received-consumer-Receive-always-timeout-tp3653090p3653259.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
