You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2009/07/29 17:02:34 UTC
[jira] Resolved: (AMQ-2158) Raise the logging level and improve
logging for memory usage changes
[ https://issues.apache.org/activemq/browse/AMQ-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-2158.
-----------------------------
Resolution: Won't Fix
reverted the additional warn level logging as it is too verbose in a production env where memory limits are in force. We need an alternative solution to logging and I guess the JMX api gives it to us atm. It is not a warn event if a limit is reached when it is expected.
rev. 798931
> Raise the logging level and improve logging for memory usage changes
> ---------------------------------------------------------------------
>
> Key: AMQ-2158
> URL: https://issues.apache.org/activemq/browse/AMQ-2158
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.0.0, 5.1.0, 5.2.0
> Reporter: Bruce Snyder
> Assignee: Gary Tully
> Fix For: 5.3.0
>
> Attachments: AMQ-2158.patch
>
>
> Currently the logging for memory usage changes in the {{Usage.fireEvent()}} method is restricted to debug output. This should be raised to info level by default and warning level if the memory usage is over a certain threshold, say 80%.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.