For statistics - can you should be able to use wildcards - if you use '>' as the destination name - what do you get ?
On 10 Dec 2010, at 22:23, watcher wrote: > > An update so far. > > We stilll cant seem to find a resolution to this issue. We have noticed > similar user having problems. > See here. > http://activemq.2283324.n4.nabble.com/Workaround-for-messages-stuck-in-a-queue-td2343453.html > http://activemq.2283324.n4.nabble.com/Workaround-for-messages-stuck-in-a-queue-td2343453.html > > > We implemented a similar workaround. Whenever we get to the end on the queue > and a message is stuck we purge the queue a republish the message. This is > not a perfect solution as you can imagine. > > We tried upgrading to 5.4.1 but the error still exists. Since then 5.4.2 has > been released but we're not convinced that this will solve the issue but we > will try soon. > > Just another bit of info, we use the statisics plugin via camel to determine > the queue size however I've not been able to implement a wildcard scan of > queues so we ended up hardcoding a route for each queue that may or may not > exist up to a max of 60 queues. The only errors we see in activemq logs are > related to timeout when trying to get queue stats for queues that do not > exist. > > http://activemq.2283324.n4.nabble.com/statisticsBrokerPlugin-error-td2716123.html > > http://activemq.2283324.n4.nabble.com/statisticsBrokerPlugin-error-td2716123.html > > > Is there any logging we could enable to understand why a message will not > get processed? > > We getting to the stage of replacing activemq with another messaging > provider but I like to think this could be solved. Any advise would be very > helpful. > > Thanks. > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Message-stuck-on-queue-tp3076607p3082780.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
