>From what it looks like in the log, after I attempt send to a non-existent temp queue, the transport mechanism gets shutdown, which would probably explain why the send() method is hanging. Is there any other way to check if a temp queue exists other than try to send to it?
Chris On Mon, Apr 9, 2012 at 2:38 PM, Chris Robison <chrisdrobi...@gmail.com>wrote: > I tried the release candidate. Still exhibits the same behavior. > > > On Mon, Apr 9, 2012 at 2:25 PM, Chris Robison <chrisdrobi...@gmail.com>wrote: > >> Just in case this helps you further, I implemented a tracer. Attached is >> the log output from that. >> >> Chris >> >> >> On Mon, Apr 9, 2012 at 2:21 PM, Timothy Bish <tabish...@gmail.com> wrote: >> >>> 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 < >>> 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? >>> >>> 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 >>> tim.b...@fusesource.com | www.fusesource.com >>> skype: tabish121 | twitter: @tabish121 >>> blog: http://timbish.blogspot.com/ >>> >>> >> >
