[#3299] - SEVERE: JasperXmlaServlet: Failed to initialize XMLA handler

Posted by ivit on November 29, 2013 - 5:38am
Category:
Bug report
 Priority:
Normal
 Status:
New
Project:
JasperReports® Server
 Severity:
Minor
 Resolution:
Open
Component: Reproducibility:
Always
 Assigned to:
Subscribe

I have upgraded JasperReports server 4.0 to 5.5
There was no error during the upgrade process.

However, whenever I start tomcat, I receive the following error in apache-tomcat/logs/localhost.yyyy-mm-dd.log:

Nov 29, 2013 3:26:09 PM org.apache.catalina.core.ApplicationContext log
SEVERE: JasperXmlaServlet: Failed to initialize XMLA handler
java.lang.NullPointerException
at mondrian.xmla.XmlaHandler.<init>(XmlaHandler.java:512)
at com.jaspersoft.jasperserver.war.xmla.XmlaHandlerImpl.<init>(XmlaHandlerImpl.java:73)
at com.jaspersoft.jasperserver.war.xmla.XmlaServletImpl.getXmlaHandler(XmlaServletImpl.java:295)
at com.jaspersoft.jasperserver.war.xmla.XmlaServletImpl.initHandlerAndSuper(XmlaServletImpl.java:416)
at com.jaspersoft.jasperserver.war.xmla.XmlaServletImpl.init(XmlaServletImpl.java:125)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4187)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4496)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:637)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:563)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:498)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:519)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

New JasperServer 5.5 runs in tomcat 6 which was part of the jasperreports-server-cp-4.0.0 (bundle) installation, i.e. I have upgraded existing 4.0 version.

v5.5
ivit's picture
ivit
148
Joined: Jan 20 2011 - 4:50am
Last seen: 7 years 1 month ago

6 Comments:

#1Posted by tgarrido on January 6, 2014 - 2:05pm
  • Assigned:nobody»

Have you found a workaround or solution for this? I'm getting same error. Thanks.

#2Posted by di.cao on January 7, 2014 - 11:33am
  • Assigned:» anonymous

I have the same problem (upgrade Jasperserver 5.2 to 5.5), but seems that this error won't break anything...

Waiting for solution/instructions... Thanks!

#3Posted by Ectomorph on February 4, 2014 - 4:08pm

Same problem here. Apart from that the server appears to work. One solution is to comment out the JasperXmlaServlet loading from /web.xml - its only used for data analysis so if you can live without that then all's well.

#4Posted by gaston.martin on February 13, 2014 - 3:56pm

Having same issue
I Just upgraded from 5.2.0 to 5.5.0. So I'm using tomcat 6 (which has been bundled with 5.2.0). It's community edition.

#5Posted by bruno.fs.antunes on March 5, 2014 - 3:59am

Hi have this same error on a clean installation of JasperReports Server 5.5.0 (Pro) without samples on WebLogic Server 10.3.6 with Java 7 Update 51

This seems to happen after debug log message "getOlapManagementService" when configuring the following log4j loggers:
log4j.logger.mondrian=debug
log4j.logger.logger.com.jaspersoft.ji=debug
log4j.logger.com.jaspersoft.jasperserver.war.xmla=debug

Extract from JasperReports Server log:
2014-03-05 11:52:33,407 INFO MondrianProperties,[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)':288 - Mondrian: properties loaded from 'file:/domains/mydomain/deployments/jasperserver-pro/WEB-INF/classes/mondrian.properties'
2014-03-05 11:52:33,426 INFO MondrianProperties,[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)':257 - Mondrian: loaded 0 system properties
2014-03-05 11:52:33,488 DEBUG XmlaServletImpl,[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)':92 - XmlaServletImpl:init
2014-03-05 11:52:33,495 WARN XmlaServlet,[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)':615 - Use default character encoding from HTTP client
2014-03-05 11:52:33,502 DEBUG XmlaServletImpl,[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)':205 - makeDataSources
2014-03-05 11:52:33,506 DEBUG XmlaServletImpl,[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)':310 - getRepository
2014-03-05 11:52:33,534 DEBUG XmlaServletImpl,[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)':215 - No XML/A Connections available
2014-03-05 11:52:33,576 DEBUG XmlaServletImpl,[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)':205 - makeDataSources
2014-03-05 11:52:33,585 DEBUG XmlaServletImpl,[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)':215 - No XML/A Connections available
2014-03-05 11:52:33,586 DEBUG XmlaServletImpl,[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)':336 - getConnectionService
2014-03-05 11:52:33,590 DEBUG XmlaServletImpl,[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)':354 - getOlapManagementService

Error on System.out/System.err
<Mar 5, 2014 11:52:33 AM WET> <Error> <ServletContext-/jasperserver-pro> <BEA-000000> <JasperXmlaServlet: Failed to initialize XMLA handler
java.lang.NullPointerException
at mondrian.xmla.XmlaHandler.<init>(XmlaHandler.java:512)
at com.jaspersoft.jasperserver.war.xmla.XmlaHandlerImpl.<init>(XmlaHandlerImpl.java:73)
at com.jaspersoft.ji.ja.security.service.SecureXmlaHandlerImpl.<init>(SecureXmlaHandlerImpl.java:44)
at com.jaspersoft.ji.ja.security.service.MTXmlaHandlerImpl.<init>(MTXmlaHandlerImpl.java:49)
at com.jaspersoft.ji.ja.security.service.MTXmlaServletImpl.getXmlaHandler(MTXmlaServletImpl.java:143)
Truncated. see log file for complete stacktrace
>

Error Extract on Applicatin Server (WebLogic) Log:
####<Mar 5, 2014 11:52:33 AM WET> <Error> <ServletContext-/jasperserver-pro> <myserver.local.corp> <jasperServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1394020353591> <BEA-000000> <JasperXmlaServlet: Failed to initialize XMLA handler
java.lang.NullPointerException
at mondrian.xmla.XmlaHandler.<init>(XmlaHandler.java:512)
at com.jaspersoft.jasperserver.war.xmla.XmlaHandlerImpl.<init>(XmlaHandlerImpl.java:73)
at com.jaspersoft.ji.ja.security.service.SecureXmlaHandlerImpl.<init>(SecureXmlaHandlerImpl.java:44)
...

#6Posted by bruno.fs.antunes on March 5, 2014 - 5:56am

Examining the source on mondrian version 3.2.0-13661-JS-3 ( Source Bundle at http://jaspersoft.artifactoryonline.com/jaspersoft/simple/third-party-ce... ), error happens in statement "for (DataSourcesConfig.DataSource ds : dataSources.dataSources)". for a non null dataSources object in class constructor for "mondrian.xmla.XmlaHandler"

Code Extract:

[line][code]
511 if (dataSources != null) {
512 for (DataSourcesConfig.DataSource ds : dataSources.dataSources) {
513 if (map.containsKey(ds.getDataSourceName())) {

Feedback
randomness