[Mondrian] XML/A support in mondrian not working

Robert Lemmen robertle at semistable.com
Mon Mar 7 06:06:32 EST 2011


hi julian,

On Fri, Mar 04, 2011 at 11:33:48AM -0800, Julian Hyde wrote:
> I looked more closely at this. I don't think it has anything to do with
> distinct-count. That just happens to be the first query Mondrian executes.
> 
> I see you got the error "Container was opened in read-only mode". According
> to http://db.apache.org/derby/releases/release-10.1.3.1.html this is a
> symptom of bug DERBY-541.     
> 
> Suggest you upgrade Derby.

thanks, that was it! I thought i had a recent derby, but indeed i was
confused about the different CLASSPATH (as always). 

however, i am still not quite there yet. i now get a different error
message "The Mondrian XML: Feature not implemented"

if i look in catalina.out, more detail is provided:

mondrian.xmla.XmlaServlet#doPost: Errors when handling XML/A message
mondrian.xmla.XmlaException: Mondrian Error:XMLA Discover unparse
results error
...
Caused by: mondrian.olap.MondrianException: Mondrian Error:Internal
error: while counting members of level '[Customers].[Name]; sql=[select
count(*) from (select distinct "customer"."fullname" from "customer" as
"customer") as "init"]
...
Caused by: java.sql.SQLException: Feature not implemented
...
Caused by: ERROR XSAI3: Feature not implemented
    at
org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
    at org.apache.derby.impl.store.raw.log.ReadOnly.checkVersion(Unknown
Source)
    at org.apache.derby.impl.store.raw.RawStore.checkVersion(Unknown
Source)
    at
org.apache.derby.impl.store.access.RAMTransaction.checkVersion(Unknown
Source)
    at
org.apache.derby.impl.store.access.heap.HeapConglomerateFactory.createConglomerate(Unknown
Source)
    at
org.apache.derby.impl.store.access.RAMTransaction.createConglomerate(Unknown
Source)
    at org.apache.derby.iapi.store.access.DiskHashtable.<init>(Unknown
Source)
    at
org.apache.derby.iapi.store.access.BackingStoreHashtable.spillToDisk(Unknown
Source)
    at
org.apache.derby.iapi.store.access.BackingStoreHashtable.add_row_to_hash_table(Unknown
Source)
...

spillToDisk() is probably not going to work if the database is embedded
in the jjar, right? I set the memory params of tomcat to ridiculously
high based on the assumption that it wouldn't "spill" then, but to no
avail... any ideas?

thanks  robert

-- 
Robert Lemmen                               http://www.semistable.com 



More information about the Mondrian mailing list