Yogesh-
I'm not sure a selector would be the best fit, since that has a pretty
defined syntax per the spec (although, ActiveMQ 5.x has precedence for
extending it in the past w/ XPath-based selector). This use case feels
narrow for something spec-breaking like that.
You could achieve gathering the information you need by writing a
customer broker-side interceptor, or looking at the LoggingInterceptor
to see if it meets your needs:
http://activemq.apache.org/logging-interceptor.html without having to
wait/hope for a JIRA to get worked out.
-Matt
On 12/2/16 12:23 PM, yogu13 wrote:
Hello Christopher,
Just incase you missed my reply
Usecase
"We recently moved away from Application Server specific JMS
(Weblogic/JBoss) to ActiveMQ. We have a usecase to determine messages which
have not been consumed from queue beyond a time limit (to make sure we
achieve our SLA) and we started noticing messages which are currently being
processed are also picked up and an alert is triggered. "
Regards,
-Yogesh
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-5-14-1-QueueBrowser-can-view-messages-being-processed-by-consumers-which-are-not-yet-unacknd-tp4719662p4719708.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
