Bug 1343526 - DV Dashboard "Export to MS Excel" utility errors with NoSuchMethodError
Summary: DV Dashboard "Export to MS Excel" utility errors with NoSuchMethodError
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Dashboard Builder
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Alex Szczuczko
QA Contact: Filip Elias
URL:
Whiteboard:
Depends On:
Blocks: 1347836
TreeView+ depends on / blocked
 
Reported: 2016-06-07 12:16 UTC by dsteigne
Modified: 2019-11-14 08:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-24 11:50:22 UTC
Type: Support Patch
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIIDDSHB-16 0 Major Closed "Export to MS Excel" utility errors with: java.lang.NoSuchMethodError 2017-04-18 08:05:34 UTC
Red Hat Knowledge Base (Solution) 2357031 0 None None None 2016-06-07 12:17:15 UTC

Description dsteigne 2016-06-07 12:16:45 UTC
Description of problem:
DV Dashboard "Export to MS Excel" utility errors with:
java.lang.NoSuchMethodError: org.apache.poi.xssf.streaming.SXSSFWorkbook.createSheet(Ljava/lang/String;)Lorg/apache/poi/xssf/streaming/SXSSFSheet;
	at org.jboss.dashboard.displayer.table.ExportTool.exportExcel(ExportTool.java:105)
	at org.jboss.dashboard.ui.components.table.TableHandler.actionExportData(TableHandler.java:341)
	at org.jboss.dashboard.ui.components.table.TableViewer.actionExportData(TableViewer.java:59)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.dashboard.ui.components.BeanHandler.handle(BeanHandler.java:152)
	at org.jboss.dashboard.ui.components.BeanDispatcher.handle(BeanDispatcher.java:133)
	at org.jboss.dashboard.ui.components.BeanDispatcher.performRequestHandling(BeanDispatcher.java:124)
	at org.jboss.dashboard.ui.components.BeanDispatcher.handleRequest(BeanDispatcher.java:46)
	at org.jboss.dashboard.ui.components.BeanDispatcher$Proxy$_$$_WeldClientProxy.handleRequest(BeanDispatcher$Proxy$_$$_WeldClientProxy.java)
	at org.jboss.dashboard.ui.panel.PanelDriver.panelActionFactory(PanelDriver.java:1237)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.jboss.dashboard.ui.panel.PanelDriver._execute(PanelDriver.java:817)
	at org.jboss.dashboard.ui.panel.PanelDriver.execute(PanelDriver.java:780)
	at org.jboss.dashboard.ui.panel.kpi.KPIDriver$Proxy$_$$_WeldClientProxy.execute(KPIDriver$Proxy$_$$_WeldClientProxy.java)
	at org.jboss.dashboard.ui.controller.requestChain.RequestDispatcher.processRequest(RequestDispatcher.java:93)
	at org.jboss.dashboard.ui.controller.requestChain.RequestDispatcher$Proxy$_$$_WeldClientProxy.processRequest(RequestDispatcher$Proxy$_$$_WeldClientProxy.java)
	at org.jboss.dashboard.ui.controller.RequestProcessor.run(RequestProcessor.java:68)
	at org.jboss.dashboard.ui.controller.RequestProcessor$Proxy$_$$_WeldClientProxy.run(RequestProcessor$Proxy$_$$_WeldClientProxy.java)
	at org.jboss.dashboard.ui.controller.ControllerServlet$1.txFragment(ControllerServlet.java:174)
	at org.jboss.dashboard.database.hibernate.HibernateTransaction.executeFragment(HibernateTransaction.java:252)
	at org.jboss.dashboard.database.hibernate.HibernateTxFragment.executeInitiator(HibernateTxFragment.java:179)
	at org.jboss.dashboard.database.hibernate.HibernateTxFragment.execute(HibernateTxFragment.java:167)
	at org.jboss.dashboard.ui.controller.ControllerServlet.processTheRequest(ControllerServlet.java:170)
	at org.jboss.dashboard.ui.controller.ControllerServlet.service(ControllerServlet.java:135)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512)
	at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926)
	at java.lang.Thread.run(Thread.java:744)


Version-Release number of selected component (if applicable):
6.2.5

How reproducible:
Always

Steps to Reproduce:
1. Open the Dashboard 
2. Navigate to a report, such as the Audit Logging
3. Click on the icon to "Export to MS Excel"
4. It will error with "An unexpected exception has occurred which has generated the following error log."  Click on the "View Error Log" to display the full stack trace.

Actual results:
Errors

Expected results:
Exports to XLS format file

Additional info:

Comment 1 jolee 2016-06-16 18:28:57 UTC
Created TEIIDDSHB-16 and assigning to Van.  Removed from DV 6.2.6,  can be considered for an Update release once upstream fix is accomplished.  Workaround exists and customer was told "to be fixed in a future release of the DV Dashboard.",  so no not promised with a particular update.

Comment 2 Van Halbert 2016-06-21 16:41:20 UTC
I tested this in DV 6.3 and it worked.  Couple of notes:

DV 6.3 version
-  dashboard version 6.3.0.Final-redhat-4
-  poi 3.13



What is in the 6.2.5 patch is:

-  dashboard version 6.2.0.Final-redhat-9
-  poi 3.11 (upgraded from 3.10)

Comment 3 JBoss JIRA Server 2016-06-21 16:44:18 UTC
Van Halbert <vhalbert> updated the status of jira TEIIDDSHB-16 to Closed

Comment 5 Alex Szczuczko 2016-06-21 16:57:52 UTC
I think this can be fixed with a change in the build config. I can configure POI 3.13 just for teiid-dashboard, and leave everything else at 3.11.

If we want to fix this in DV 6.2.6, I would need to rebuild.

Comment 7 jolee 2016-06-21 17:47:03 UTC
I have already dropped this as a blocker for 6.2.6,  so no rebuild should be needed here.  I'm moving to 1347836

Comment 8 Alex Szczuczko 2016-07-08 13:52:15 UTC
The teiid-dashboard build should now use poi 3.13 instead of 3.11.

Comment 9 Filip Elias 2016-08-16 09:45:50 UTC
Verified using 6.2.7


Note You need to log in before you can comment on or make changes to this bug.