I am sending messages through a Camel route in ActiveMQ. My message reaches the end of the processing chain, and at the last processor I call exchange.setOut( newly created DefaultMessage ). When I look at the admin page for ActiveMQ, the topic shows that there is a message to be dequeued. It even says that there is a consumer connected to that topic, which is a GUI tool I wrote. The GUI tool makes a call to Consumer.setMessageListener. So why are the messages not making their way to my GUI tool? I am stumped as to why the messages sit in the topic and never leave if there is a listener for that topic.
Of course the first thought is, is the Connection started? Yeah I verified that. In fact I can send messages to the topic via the web-based admin tool for ActiveMQ and the GUI receives them. Thanks for any help you have, Mark
