I wrote a utility that take a message off the queue based on JMSMessageId, copy its contents but update its header information. That is why i look up by JMSMessageId only to ensure uniqueness.
After further investigation, I realized that my problem happens only when I stop my Jboss. My Jboss instance runs a MessageListener that I can start or stop (which has no effect on message consumption). When JBOSS is up and running and has MessageListener connected to this same queue, then I have no problem. I also stopped the MessageListener while JBOSS still running and I still had no issue. Once I stopped JBOSS running on my local machine, I could not longer find the new Messages. So my problem occurs only after I START and STOP my JBOSS server which has a configured connection to the same Queue. Hope this sheds some more light on the issues. -- View this message in context: http://activemq.2283324.n4.nabble.com/Issue-with-MessageConsumer-and-MessageSelector-tp4704870p4704904.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
