Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0010680 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] 01. General setup | minor | have not tried | 2009-09-21 12:37 | 2011-11-17 10:51 | |||
| Reporter | shuehner | View Status | public | |||||
| Assigned To | eduardo_Argal | |||||||
| Priority | normal | Resolution | out of date | Fixed in Version | ||||
| Status | closed | Fix in branch | pi | Fixed in SCM revision | ||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | pi | SCM revision | ||||||
| Review Assigned To | ||||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0010680: Logging in InitialClientSetup and InitialOrgSetup should use error instead of warn and have stacktrace for exceptions | |||||||
| Description | Most 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. | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0042917) eduardo_Argal (developer) 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 [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-09-21 12:37 | shuehner | New Issue | |
| 2009-09-21 12:37 | shuehner | Assigned To | => eduardo_Argal |
| 2009-09-21 12:37 | shuehner | Relationship added | related to 0010678 |
| 2009-09-29 22:56 | psarobe | Status | new => scheduled |
| 2009-09-29 22:56 | psarobe | fix_in_branch | => pi |
| 2011-11-17 10:51 | eduardo_Argal | Note Added: 0042917 | |
| 2011-11-17 10:51 | eduardo_Argal | Status | scheduled => closed |
| 2011-11-17 10:51 | eduardo_Argal | Resolution | open => out of date |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |