[
https://issues.apache.org/jira/browse/AMQ-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5743.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.12.0
thanks for reporting
fix in http://git-wip-us.apache.org/repos/asf/activemq/commit/23ecbe80
> purged of 0 messages | org.apache.activemq.broker.region.Queue logged when
> clearing a temp queue
> ------------------------------------------------------------------------------------------------
>
> Key: AMQ-5743
> URL: https://issues.apache.org/jira/browse/AMQ-5743
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.11.0, 5.11.1
> Reporter: Aleksandar Ivanisevic
> Assignee: Gary Tully
> Priority: Minor
> Fix For: 5.12.0
>
>
> since upgrading to 5.11 I'm getting a lot of these in the logs
> 2015-03-10 09:50:36,212 | INFO |
> temp-queue://ID:STATS2-37496-1425976359943-3:1604:1 purged of 0 messages |
> org.apache.activemq.broker.region.Queue | ActiveMQ Transport:
> ssl:///213.198.74.90:36525
> According to Garry Tully this is an oversight, quote from the users mailing
> list
> "that is an oversight, when purge is called from a jmx op, we want to
> log the event, but it is also called to clear a temp queue when the
> temp queue is deleted and that should not generate a log message. I
> think that is your case.
> Can you open a jira to track this so that others will see the
> resolution. thanks"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
