Good point - when using this type of selector scenario, using message TTLs or some other means of making sure messages are consumed is important.
As mentioned earlier, grabbing a stack trace may be telling, although it may be a little more difficult to understand since the DMLC is involved. Impacts of closing the session that was created by the DMLC is a good question as well. Unless there is some documentation from the Spring DMLC that shows it is safe to do, or the code has been read to ensure so, I would avoid doing so. Also, closing the session seems odd to me -- if there is a problem with the connection, closing the connection would be necessary and closing the session would be unlikely to fix it. If there is a problem within the single session, that is odd. One thing to note - having producers and consumers sharing the same connection can lead to a deadlock when producer-flow-control kicks in, depending on the messaging pattern of the clients involved. -- View this message in context: http://activemq.2283324.n4.nabble.com/Consumer-not-able-to-consume-messages-from-queue-tp4689594p4689811.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
