Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0007113 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] 03. Procurement management | major | always | 2009-01-23 16:49 | 2009-03-03 09:41 | |||
| Reporter | alostale | View Status | public | |||||
| Assigned To | rafaroda | |||||||
| Priority | high | Resolution | fixed | Fixed in Version | pi | |||
| Status | closed | Fix in branch | pi | Fixed in SCM revision | 13047 | |||
| 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 | 0007113: SQL error badly informed when printing Jasper Report | |||||||
| Description | Purchase Order Report seems not to work since when trying to execute it the following error is raised in UI: Error executing SQL statement for : ReportPurchaseOrder The log error is: 16:33:41 [http-8880-Processor21] ERROR org.openbravo.erpCommon.utility.PrintJR - Error captured: javax.servlet.ServletException: Error executing SQL statement for : ReportPurchaseOrder | |||||||
| Steps To Reproduce | -Go to Procurement Management > Analysis tools > Purchase Order Report -Execute it | |||||||
| Proposed Solution | The problem here is not in the report, which is working correctly, but in the way SQL errors of Jasper Reports are catch when printing them. What it is happening in this report is that a message is informing that there is no conversion rate for some transaction. Method renderJR is displaying a plain 'Error executing SQL statement for' + the name of the method without informing about the real cause of the problem. If the error were a SQL error, the message should look like: ERROR: column c_bpartner.tercero does not exist (see attached AfterFix.png) but now it is displaying the plain error meesage: Error executing SQL statement for : ReportPurchaseOrder (see attached BeforeFix.png) Proposed solution is to change, inside renderJR method of HttpSecureAppServlet.java [1]: throw new ServletException(e.getMessage()); by throw new ServletException(e.getCause().getMessage()); [1] https://dev.openbravo.com/websvn/openbravo/trunk/src/org/openbravo/base/secureApp/HttpSecureAppServlet.java [^] | |||||||
| Tags | commsup_sprint6 | |||||||
| Attached Files |  BeforeFix.png [^] (8,240 bytes) 2009-02-09 16:16
AfterFix.png [^] (7,565 bytes) 2009-02-09 16:17
| |||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0013340) svnbot (reporter) 2009-02-11 12:52 |
Repository: openbravo Revision: 13047 Author: rafaroda Date: 2009-02-11 12:52:52 +0100 (Wed, 11 Feb 2009) Fixes bug 0007113 Now SQL errors are correctly informed when printing Jasper Report both in the UI and the log. --- U trunk/src/org/openbravo/base/secureApp/HttpSecureAppServlet.java --- https://dev.openbravo.com/websvn/openbravo/?rev=13047&sc=1 [^] |
|
(0014268) sureshbabu (reporter) 2009-03-03 09:41 |
Retested in context http:79.125.56.185/openbravotrunk |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-01-23 16:49 | alostale | New Issue | |
| 2009-01-23 16:49 | alostale | Assigned To | => rafaroda |
| 2009-01-23 16:49 | alostale | sf_bug_id | 0 => 2531286 |
| 2009-01-23 16:49 | alostale | Regression testing | => No |
| 2009-01-23 16:49 | alostale | Issue Monitored: alostale | |
| 2009-01-28 08:45 | rafaroda | version | => trunk |
| 2009-01-30 17:12 | rafaroda | Assigned To | rafaroda => Dowid |
| 2009-01-30 17:12 | rafaroda | Priority | normal => high |
| 2009-01-30 17:12 | rafaroda | Status | new => scheduled |
| 2009-02-02 06:11 | pjuvara | Priority | high => urgent |
| 2009-02-05 15:50 | rafaroda | Relationship added | blocks 0007395 |
| 2009-02-09 15:51 | rafaroda | Relationship deleted | blocks 0007395 |
| 2009-02-09 16:03 | rafaroda | Assigned To | Dowid => rafaroda |
| 2009-02-09 16:03 | rafaroda | Priority | urgent => high |
| 2009-02-09 16:03 | rafaroda | Summary | Purchase Order Report does not work => SQL error badly informed when printing Jasper Report |
| 2009-02-09 16:03 | rafaroda | Description Updated | |
| 2009-02-09 16:03 | rafaroda | Proposed Solution updated | |
| 2009-02-09 16:03 | rafaroda | Steps to Reproduce Updated | |
| 2009-02-09 16:07 | rafaroda | Steps to Reproduce Updated | |
| 2009-02-09 16:10 | rafaroda | Status | scheduled => feedback |
| 2009-02-09 16:11 | rafaroda | Status | feedback => new |
| 2009-02-09 16:11 | rafaroda | Steps to Reproduce Updated | |
| 2009-02-09 16:16 | rafaroda | Steps to Reproduce Updated | |
| 2009-02-09 16:16 | rafaroda | File Added: BeforeFix.png | |
| 2009-02-09 16:17 | rafaroda | File Added: AfterFix.png | |
| 2009-02-10 12:58 | rafaroda | Status | new => scheduled |
| 2009-02-10 12:58 | rafaroda | fix_in_branch | => trunk |
| 2009-02-11 12:52 | svnbot | Checkin | |
| 2009-02-11 12:52 | svnbot | Note Added: 0013340 | |
| 2009-02-11 12:52 | svnbot | Status | scheduled => resolved |
| 2009-02-11 12:52 | svnbot | Resolution | open => fixed |
| 2009-02-11 12:52 | svnbot | svn_revision | => 13047 |
| 2009-02-13 09:18 | rafaroda | Tag Attached: commsup_sprint6 | |
| 2009-02-24 10:51 | alostale | Issue End Monitor: alostale | |
| 2009-03-03 09:41 | sureshbabu | Status | resolved => closed |
| 2009-03-03 09:41 | sureshbabu | Note Added: 0014268 | |
| 2009-03-03 09:41 | sureshbabu | Fixed in Version | => trunk |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |