Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0010680Openbravo ERP01. General setuppublic2009-09-21 12:372011-11-17 10:51
Reportershuehner 
Assigned Toeduardo_Argal 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionout of date 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version 
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
Summary0010680: Logging in InitialClientSetup and InitialOrgSetup should use error instead of warn and have stacktrace for exceptions
DescriptionMost logging in these two files is done with

log4j.warn(err).

were err is some Exception. This should be changed to

log4j.error("Error in <somestep>", err)

to use error loglevel and include the stacktrace and location of the exception in the log output.
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 00106782.50MP6 closed marvintm NPE in InitialOrgSetup if the client has not BigImage logo, but has a DocumentImage logo 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-09-21 12:37shuehnerNew Issue
2009-09-21 12:37shuehnerAssigned To => eduardo_Argal
2009-09-21 12:37shuehnerOBNetwork customer => No
2009-09-21 12:37shuehnerRelationship addedrelated to 0010678
2009-09-29 22:56psarobeStatusnew => scheduled
2009-09-29 22:56psarobefix_in_branch => pi
2011-11-17 10:51eduardo_ArgalNote Added: 0042917
2011-11-17 10:51eduardo_ArgalStatusscheduled => closed
2011-11-17 10:51eduardo_ArgalResolutionopen => out of date

Notes
(0042917)
eduardo_Argal   
2011-11-17 10:51   
Openbravo provides community support only for the latest Openbravo version, which is Openbravo 3. This version has significantly improved financial flow, filtering, performance, etc and this issue is not present there. Upgrade path from Openbravo 2.50 to latest Openbravo version is available so we recommend to upgrade your instance to get this issue fixed.

Life cycle guarantee (backporting bug fixes to the previos to latest releases (Openbravo 2.40, 2.50)) is available for Professional Edition subscribers only. Please register your ticket through Openbravo Support Portal (http://support.openbravo.com/ [^]) if you have valid Professional subscription.

You can find more details about our Support policy in the following blog post
http://paolojuvara.blogspot.com/2009/12/maintenance-policy-for-openbravo-250.html [^]