Bug 1008906 - Some serious log messages don't have id to identify them - JBoss Web
Summary: Some serious log messages don't have id to identify them - JBoss Web
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: DR1
: EAP 6.4.0
Assignee: Rémy Maucherat
QA Contact: Nikoleta Hlavickova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-17 10:21 UTC by Petr Kremensky
Modified: 2019-08-19 12:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Petr Kremensky 2013-09-17 10:21:52 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:
jboss-web/src/main/java/org/apache/catalina/valves/PersistentValve.java
 - 118   container.getLogger().error("deserializeError")
jboss-web/src/main/java/org/apache/catalina/session/StoreBase.java
 - 181   manager.getContainer().getLogger().error("Error getting keys", e);
jboss-web/src/main/java/org/jboss/web/php/ScriptEnvironment.java
 - 366   log.error("Invalid script names");

version: JBOSSWEB_7_2_2_FINAL
Comment 1 Rémy Maucherat 2014-01-10 15:09:59 UTC 
r2337
Comment 2 Kabir Khan 2014-12-05 13:04:01 UTC 
Since this appears to have been part of 6.3.0, I am setting to ON_QA for 6.4.0
Comment 3 Nikoleta Hlavickova 2014-12-09 14:30:13 UTC 
There are some suspicious logs, but they all seem OK:

src/main/java/org/apache/catalina/core/ApplicationContext.java
 - 687   context.getLogger().error(message, exception);
 - 700   context.getLogger().error(message, throwable);
src/main/java/org/apache/catalina/authenticator/FormAuthenticator.java
 - 381   CatalinaLogger.AUTH_LOGGER.warn(msg, t);
 - 411   CatalinaLogger.AUTH_LOGGER.warn(msg, t);

Verified with EAP 6.4.0.DR12.
Note You need to log in before you can comment on or make changes to this bug.