reverted back to Mondrian 3.3.0 version of mondrian.jar and olap4j.jar
due to query concurrency issue http://jira.pentaho.com/browse/MONDRIAN-1130
hi Raimonds, could you check if the bug still happens even with jruby-1.6.8 or jruby-1.7.0-preview?
I've had some weird concurrency issues with jruby-1.6.7.
just to be sure if it's really a mondrian bug
Original http://jira.pentaho.com/browse/MONDRIAN-1130 issue was solved but then when repeating the same test with many concurrent requests got the next issue which is described in that issue comments. I have traced it down to failing Mondrian code and periodically reminding Pentaho developers about it :)
I would like very much to move to Mondrian 3.4 as I also would like to move to Java 7 and JRuby 1.7 but as currently due to this bug some eazyBI reports are failing then I cannot do it yet...
also would like to upgrade, I was testing mondrian-3.4.10.jar (built from branch in github) when I saw your comment here. Just voted there on their jira issue ;)
One workaround is to set
With this set and then using recent Mondrian 3.4 build I could not repeat that issue. But as I understand with this option Mondrian might work slower therefore did not use that as default option.
ok thanks. I had to set
because of MONDRIAN-1067.