Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0002524
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformminoralways2008-01-17 10:352008-06-18 19:59
ReporterjpabloaeView Statuspublic 
Assigned Toiperdomo 
PrioritynormalResolutionfixedFixed in Version2.40alpha-r3
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0002524: XmlEngine: too many log4j info messages

DescriptionThere are too many (23) "log4jXmlEngine.info" lines in src-core/src/org/openbravo/xmlEngine/XmlEngine.java. Due to the continuous usage of XmlEngine this results in a very large and unequally verbose log file.

A possibility would be to make them "log4jXmlEngine.debug".
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0003049)
iperdomo (viewer)
2008-01-30 12:48
edited on: 2008-06-12 09:24

Logged In: YES
user_id=1820699
Originator: NO

If you don't have a proper log4j.lcf the log messages goes to catalina.out, and with INFO level. That's why is too verbose.
With a well configured log4j.lcf you should not have problems.
(0003050)
psarobe (viewer)
2008-06-01 23:50
edited on: 2008-06-12 09:24

Logged In: YES
user_id=1500703
Originator: NO

QA team need a clarification. The bug was Closed and Fixed but reading iperdomo explanation seems that the bug should had closed as rejected
(0003051)
iperdomo (viewer)
2008-06-02 10:25
edited on: 2008-06-12 09:24

Logged In: YES
user_id=1820699
Originator: NO

The bug was closed as fixed because several .info() statements were changed to .debug()
Note that if you have the log4j.lcf properly configured there is no problem with the "verbosity"
(0006113)
user71
2005-06-01 00:00
edited on: 2008-06-12 09:43

This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1873542 [^]

- Issue History
Date Modified Username Field Change
2008-06-18 19:59 plujan Status resolved => closed


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker