Bug 1008901 - Some serious log messages don't have id to identify them
Summary: Some serious log messages don't have id to identify them
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: mod_cluster
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: DR5
: EAP 6.3.0
Assignee: Jean-frederic Clere
QA Contact: Michal Karm Babacek
Russell Dickenson
Depends On:
TreeView+ depends on / blocked
Reported: 2013-09-17 10:11 UTC by Petr Kremensky
Modified: 2014-06-28 15:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In previous versions of JBoss EAP 6, it was found that two log messages were not localized correctly. As a result users did not see a MODCLUSTER{ID} message nor a translation. In this release, two messages have been added: MODCLUSTER000044 and MODCLUSTER000045. The messages now appear as expected.
Clone Of:
Last Closed: 2014-06-28 15:37:43 UTC
Type: Bug

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat One Jira Issue Tracker MODCLUSTER-380 Major Closed Some serious log messages don't have id to identify them 2018-07-09 16:15:53 UTC

Description Petr Kremensky 2013-09-17 10:11:45 UTC
According to https://issues.jboss.org/browse/ANDIAMO-7 all serious log messages should have a unique code that can be used to identify them.
As a part of logging unification tests for EAP I found:
 - 52   logger.warnf("%s is not supported on this system and will be disabled.", this.getClass().getSimpleName());
 - 64   this.logger.warn(this.getClass().getSimpleName() + " requires com.sun.management.OperatingSystemMXBean.");

these should be moved to ModClusterLogger.java as well

version: 1.2.4.Final

Comment 1 Jean-frederic Clere 2013-12-17 07:34:44 UTC
That requires a new version of mod_cluster.

Comment 2 Michal Karm Babacek 2014-03-21 10:46:10 UTC
02:43:20,779 WARN  [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000045: AverageSystemLoadMetric is not supported on this system and will be disabled.


Note You need to log in before you can comment on or make changes to this bug.