More on the issue. I'm noticing that if I don't attempt to reply to messages that the messages will be consumed just fine, however, as soon as I try to reply to a message, if the temp queue doesn't exist, something is causing that message to not get acknowledged. I'm catching all exception. I also started noticing that after an attempt to send to a non-existent temp queue, that the producer send() method started to hang indefinitely. The usage limits are set very high so I don't it was that because I also have the sendFailIfNoSpace set to true.
On Mon, Apr 9, 2012 at 11:41 AM, Chris Robison <chrisdrobi...@gmail.com>wrote: > I have a windows service that is long running, listening to messages from > a particular queue. This windows service replies to messages off the queue. > Right now, if there are old messages on the queue, there is a good change > the temp queue set in the message no longer exists and it appears as though > when the client tries to send a message to that temp queue, that not only > is it getting the 'destination does not exist' error, but it is also > getting disconnected from the broker. I have included the broker debug log. > Any ideas?
