Openbravo Issue Tracking System - Modules
View Issue Details
0042179ModulesAnalyticspublic2019-11-04 11:232019-11-15 09:22
santi_lozano 
caristu 
highmajoralways
closedfixed 
5
 
 
alostale
0042179: OB Analytics Drill through error
In OB Analytics when using Drill through function an error is raised after selecting a cell, selecting a dimension and measure and clicking OK button. Showing message “IllegalArgumentException: java.sql.ResultSet referenced from a method is not visible from class loader”
*go to Openbravo livebuilds, section Retail with module click on link pgsql backend, change role to
*check if Analytics Sales Details View window is empty, in case it is empty go to Process Request window and create a new one: Client = F&B International Group, Organization = *, Process = Forward Update Analytics Fact Tables, Timing = Run Immediately. Click on button Schedule Process, wait for it to be on status Success (process selected go to Process Monitor tab to see its status). Now Analytics Sales Details View window should have content
*go to OB Analytics window select cube Sales Details Fact Cube, add into Measures “Sales” and “Discounts”, add into Columns Organization, add into Rows Month of Year (drag them from left to the right, note that for dimensions you must expand the menu).
*from the upper menu of OB Analytics (where you have buttons like Save query or Run query), click on button Drill through on cell, then select a cell of sales and january (or other cell)
*in the Drill-Through popup select product as dimension and sales as measure, click ok then the error message appears (“IllegalArgumentException: java.sql.ResultSet referenced from a method is not visible from class loader”)
No tags attached.
related to design defect 0042474 acknowledged Triage Platform Base Drill Through is showing fields by its id instead of by its name 
Issue History
2019-11-04 11:23santi_lozanoNew Issue
2019-11-04 11:23santi_lozanoAssigned To => platform
2019-11-04 11:24santi_lozanoResolution time => 1574636400
2019-11-04 11:30PracticsIssue Monitored: Practics
2019-11-12 09:54hgbotCheckin
2019-11-12 09:54hgbotNote Added: 0115549
2019-11-12 09:54hgbotStatusnew => resolved
2019-11-12 09:54hgbotResolutionopen => fixed
2019-11-12 09:54hgbotFixed in SCM revision => http://code.openbravo.com/erp/pmods/org.openbravo.client.analytics/rev/4eb4a0f39f13a94d560fb1e7409a3689dad03050 [^]
2019-11-12 09:54caristuAssigned Toplatform => caristu
2019-11-12 09:54caristuReview Assigned To => alostale
2019-11-15 09:22alostaleNote Added: 0115619
2019-11-15 09:22alostaleStatusresolved => closed
2020-01-27 12:15maiteRelationship addedrelated to 0042474

Notes
(0115549)
hgbot   
2019-11-12 09:54   
Repository: erp/pmods/org.openbravo.client.analytics
Changeset: 4eb4a0f39f13a94d560fb1e7409a3689dad03050
Author: Carlos Aristu <carlos.aristu <at> openbravo.com>
Date: Tue Nov 12 09:33:16 2019 +0100
URL: http://code.openbravo.com/erp/pmods/org.openbravo.client.analytics/rev/4eb4a0f39f13a94d560fb1e7409a3689dad03050 [^]

fixes issue 42179: OB Analytics Drill through error

  The problem was that mondrian was able to load a dynamic proxy for an SqlStatement used to calculate the "drill through". This was because being in a web application, the web application classloader should be used to create the dynamic proxy.

  See: https://github.com/alostale/mondrian/commit/69649d2c4c6e180f04ebedf3f5af34f1162bf88d [^]

---
M lib/runtime/mondrian-4.3.0.1-patched.jar
---
(0115619)
alostale   
2019-11-15 09:22   
reviewed