On Mon, 2012-04-09 at 16:10 -0400, Chris Robison wrote: > 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 <[email protected]>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?
You may want to test using the NMS.ActiveMQ v1.5.4 release candidate that you can download here: http://people.apache.org/~tabish/nms-1.5.0/ -- Tim Bish Sr Software Engineer | FuseSource Corp [email protected] | www.fusesource.com skype: tabish121 | twitter: @tabish121 blog: http://timbish.blogspot.com/
