Openbravo Issue Tracking System - Modules |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0038326 | Modules | External Data Integration | public | 2018-04-11 11:31 | 2018-05-31 13:53 |
|
Reporter | AugustoMauch | |
Assigned To | AugustoMauch | |
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | acknowledged | Resolution | open | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Regression date | |
Regression introduced by commit | |
Regression level | |
Review Assigned To | |
Support ticket | |
OBNetwork customer | |
Regression introduced in release | |
|
Summary | 0038326: Sometimes the exception message is not descriptive, maybe show the full stack trace in the error message field |
Description | Now when there is an error processing an EDL Request, only the exception message is saved [1].
In most cases the exception message is not enough, and the user/developer must look for more context in the Openbravo log.
It would be useful if instead of storing only the exception message, the full stack trace (that includes the exception message) were stored.
[1] https://code.openbravo.com/erp/pmods/org.openbravo.externaldata.integration/file/tip/src/org/openbravo/externaldata/integration/process/AsynchronousProcessor.java#l233 [^] |
Steps To Reproduce | In any EDL Item processor, force an exception:
Object o = null;
o.toString();
The EDL Request Line will show only "java.lang.NullPointerException", it would be much more useful for developers if the full stacktrace were shown. |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | defect | 0038235 | | closed | AugustoMauch | SERQA 3916: Errors while reprocessing an EDL Request are not logged |
|
Attached Files | stackTraceRequestLine.png (71,967) 2018-04-16 16:44 https://issues.openbravo.com/file_download.php?file_id=11739&type=bug
|
|
Issue History |
Date Modified | Username | Field | Change |
2018-04-11 11:31 | AugustoMauch | New Issue | |
2018-04-11 11:31 | AugustoMauch | Assigned To | => AugustoMauch |
2018-04-11 11:31 | AugustoMauch | Modules | => Core |
2018-04-11 11:31 | AugustoMauch | Triggers an Emergency Pack | => No |
2018-04-11 11:39 | hgbot | Checkin | |
2018-04-11 11:39 | hgbot | Note Added: 0103806 | |
2018-04-11 11:39 | hgbot | Status | new => resolved |
2018-04-11 11:39 | hgbot | Resolution | open => fixed |
2018-04-11 11:39 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/pmods/org.openbravo.externaldata.integration/rev/31f65ae0a799f2f1cd43be05617aef558faac378 [^] |
2018-04-11 11:40 | AugustoMauch | Review Assigned To | => caristu |
2018-04-11 18:06 | hgbot | Checkin | |
2018-04-11 18:06 | hgbot | Note Added: 0103830 | |
2018-04-16 08:39 | caristu | Project | Openbravo ERP => Modules |
2018-04-16 08:40 | caristu | Category | A. Platform => External Data Integration |
2018-04-16 08:48 | caristu | Relationship added | related to 0038325 |
2018-04-16 08:51 | caristu | Relationship deleted | related to 0038325 |
2018-04-16 08:51 | caristu | Relationship added | related to 0038235 |
2018-04-16 13:52 | naiaramartinez | Issue Monitored: naiaramartinez | |
2018-04-16 16:43 | caristu | Note Added: 0103908 | |
2018-04-16 16:44 | caristu | File Added: stackTraceRequestLine.png | |
2018-04-16 16:46 | AugustoMauch | Note Added: 0103911 | |
2018-04-16 16:46 | AugustoMauch | Status | resolved => new |
2018-04-16 16:46 | AugustoMauch | Resolution | fixed => open |
2018-04-16 16:49 | hgbot | Checkin | |
2018-04-16 16:49 | hgbot | Note Added: 0103912 | |
2018-04-16 16:50 | hgbot | Checkin | |
2018-04-16 16:50 | hgbot | Note Added: 0103913 | |
2018-04-16 16:52 | AugustoMauch | Summary | When there is an Exception when processing an EDL Request, show the full stack trace in the error message field => Sometimes the exception message is not descriptive, maybe show the full stack trace in the error message field |
2018-04-16 16:52 | AugustoMauch | Status | new => acknowledged |
2018-05-31 13:53 | caristu | Review Assigned To | caristu => |
Notes |
|
(0103806)
|
hgbot
|
2018-04-11 11:39
|
|
|
|
(0103830)
|
hgbot
|
2018-04-11 18:06
|
|
|
|
|
Note that when the error message assigned to the request line is informative enough, including the stack trace could be confusing to the user. See attached image as an example. |
|
|
|
Carlos is right. In most cases the stack trace will add noise, instead of making the error message more clear.
It is better to leave it as it was before this fix. |
|
|
(0103912)
|
hgbot
|
2018-04-16 16:49
|
|
|
|
(0103913)
|
hgbot
|
2018-04-16 16:50
|
|
|