Jump to content
We've recently updated our Privacy Statement, available here ×

EmptyStackException in OLAP Analysis after Update to JasperServer 5.6


planetzone

Recommended Posts

After updaten my JasperServer 4.5 to 5.6 I encountered a few issues with the OLAP analysis. I can open the analysis just fine, but if I try to expand a dimension in the CUBE settings I get the following exception:

java.util.EmptyStackExceptionat mondrian.util.ArrayStack.peek(ArrayStack.java:67)at mondrian.server.Locus.peek(Locus.java:61)atmondrian.rolap.SqlMemberSource.getMemberChildren2(SqlMemberSource.java:949)atmondrian.rolap.SqlMemberSource.getMemberChildren(SqlMemberSource.java:876)atmondrian.rolap.SqlMemberSource.getMemberChildren(SqlMemberSource.java:849)atmondrian.rolap.SmartMemberReader.readMemberChildren(SmartMemberReader.java:248)atmondrian.rolap.SmartMemberReader.getMemberChildren(SmartMemberReader.java:210)atmondrian.rolap.RolapCubeHierarchy$CacheRolapCubeHierarchyMemberReader.readMemberChildren(RolapCubeHierarchy.java:599)atmondrian.rolap.RolapCubeHierarchy$CacheRolapCubeHierarchyMemberReader.getMemberChildren(RolapCubeHierarchy.java:695)atmondrian.rolap.SmartMemberReader.getMemberChildren(SmartMemberReader.java:176)atmondrian.rolap.RolapSchemaReader.internalGetMemberChildren(RolapSchemaReader.java:186)atmondrian.rolap.RolapSchemaReader.getMemberChildren(RolapSchemaReader.java:168)atmondrian.rolap.RolapSchemaReader.getMemberChildren(RolapSchemaReader.java:162)atmondrian.olap.DelegatingSchemaReader.getMemberChildren(DelegatingSchemaReader.java:78)atcom.tonbeller.jpivot.mondrian.MondrianMemberTree.internalGetChildren(MondrianMemberTree.java:252)atcom.tonbeller.jpivot.mondrian.MondrianMemberTree.getChildren(MondrianMemberTree.java:235)atcom.tonbeller.jpivot.navigator.member.TreeModelAdapter.getChildren(TreeModelAdapter.java:106)...                                             [/code]

 

I googled the error and found similar problems with Pentaho BI (they use the same OLAP engine an jpivot; they are also the creators of the Mondrian OLAP engine). It seems to be fixed in their system.

Has anybody encountered similar problems in Jasper BI and could provide a solution for this?

Link to comment
Share on other sites

  • Replies 3
  • Created
  • Last Reply

Top Posters In This Topic

In the Mondrian JavaDoc (http://mondrian.pentaho.com/api/mondrian/olap/SchemaReader.html) I found the following:

If you use a SchemaReader from outside of a mondrian statement, you may get a EmptyStackException indicating that mondrian cannot deduce the current locus (statement context). If you get that error, call withLocus() to create a SchemaReader that automatically provides a locus whenever a call is made.


Could this be the reason for the error? How can I fix this? I couldn't find the source code for the custom Jaspersoft mondrian or jpivor implementations in the subversion repo.

 

 

Link to comment
Share on other sites

  • 4 weeks later...
  • 3 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...