I did try to connect with the ?jms.watchTopicAdvisories=false in the uri. That didn't fix it. I ran my example with activemqcpp code. I found that that on the consumer side when I call
MessageProducer->send(replyTodestination, message) ultimately it ends up calling ActiveMQSessionKernel::send() in which it checks for isDeleted(). IsDeleted checks the mValue map inside the options object in the producers connection object. That map is empty which causes the "Cannot publish to deleted destination message". I dug a little further. The only way destinations can be added to the map is by calling addTemporaryDestination() function on the option class. That function is only called with advisory message or when creating a temporaryQueue. As per my understanding TempQueue will never work on the client side without advisory messages. Am I missing something? If I am wrong please help understand what I need to do to fix the message. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
