[Mondrian] [Olap4j-devel] problems with concurrency (shepherd) execution

Paul Stoellberger p.stoellberger at gmail.com
Tue Oct 18 21:22:02 EDT 2011

i had a quick look into our code but i couldn't find anything in there that would match it
is executeInternal only called when an actual query is fired?
harris has tested the new fixed version but seems to get the same error as previously.

i'll have another look tomorrow but i wouldn't see how our code executes the same statement twice in our context.
will let you know what/if i find anything


On Oct 19, 2011, at 1:07 AM, Julian Hyde wrote:

> On Oct 18, 2011, at 9:01 AM, Luc Boudreau wrote:
>> I've reproduced your issue and fixed it on our side. Seems like the
>> Saiku code is executing the same OlapStatement twice concurrently (or
>> the olap4j CellSet). I added a check in our code that cancels the
>> previous execution prior to running it again, but you might want to
>> look into your server code and make sure that you do not share
>> statements across your HTTP threads.
> If that's what's happening -- running two queries on the same statement -- the best behavior would be to fail, but give a descriptive error message. Tough love, as it were.
> Julian
> _______________________________________________
> Mondrian mailing list
> Mondrian at pentaho.org
> http://lists.pentaho.org/mailman/listinfo/mondrian

More information about the Mondrian mailing list