Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0045653 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
design defect | [Openbravo ERP] A. Platform | major | always | 2020-12-28 09:44 | 2021-08-09 14:50 | |||||||
Reporter | Leyre | View Status | public | |||||||||
Assigned To | Leyre | |||||||||||
Priority | high | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | 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 | 0045653: "NullPointerException" in update.database when the log is at debug level or higher | |||||||||||
Description | "NullPointerException" in update.database when the log is at debug level or higher | |||||||||||
Steps To Reproduce | 1. Change in the file config/log4j2.xml: <Loggers> <Root level="info"> <AppenderRef ref="Console"/> For <Loggers> <Root level="debug"> <AppenderRef ref="Console"/> 2. Execute: ant update.database Result: see attached file with the error. | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | error.txt [^] (9,166 bytes) 2020-12-28 09:44 [Show Content] | |||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0125236) AugustoMauch (administrator) 2021-01-04 10:35 |
Leyre, I fixed the NullPointerException, but after that update.database does not finish, it seems that the XML parser it uses enters in an infinite loop when the log root is in debug mode. If the original purpose of changing the log root to debug was to check some problem in the update.database project, you might achieve the same result adding this line instead: <Logger name="org.apache.ddlutils" level="debug"/> Was that the purpose of changing the log level? Can you check if adding the line I mentioned achieves the same? |
(0131041) plujan (manager) 2021-08-09 14:50 |
Updated as a design defect and moved back to New status |
Issue History | |||
Date Modified | Username | Field | Change |
2020-12-28 09:44 | Leyre | New Issue | |
2020-12-28 09:44 | Leyre | Assigned To | => platform |
2020-12-28 09:44 | Leyre | File Added: error.txt | |
2020-12-28 09:44 | Leyre | Modules | => Core |
2020-12-28 09:44 | Leyre | Resolution time | => 1610924400 |
2020-12-28 09:44 | Leyre | Triggers an Emergency Pack | => No |
2020-12-29 11:57 | cberner | Summary | "NullPointerException" in update.database when the log is at warning level or higher => "NullPointerException" in update.database when the log is at debug level or higher |
2020-12-29 11:57 | cberner | Description Updated | View Revisions |
2021-01-04 10:35 | AugustoMauch | Note Added: 0125236 | |
2021-01-04 10:35 | AugustoMauch | Assigned To | platform => Leyre |
2021-01-04 10:35 | AugustoMauch | Status | new => feedback |
2021-08-09 14:50 | plujan | Note Added: 0131041 | |
2021-08-09 14:50 | plujan | Status | feedback => new |
2021-08-09 14:50 | plujan | Type | defect => design defect |
Copyright © 2000 - 2009 MantisBT Group |