Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 3.4.1 GA (4.5.0 GA Suite Release), 3.4.3 GA
-
Fix Version/s: 3.4.4 GA
-
Component/s: None
-
Labels:None
-
CS:CS1
-
Customer Case:
-
QA Validation Status:Not Yet Validated
Description
Apparently, Mondrian is issuing only one mdx query at a time.
Steps to reproduce:
Open Analysis View - Create connection over steel-wheels and issue a top count query. We have a breakpoint set in RolapNativeTopCount so execution stops there.
Open another analysis View - Create connection over SampleData (another cube which should rule out cache sharing, I guess) .
Mondrian is called to get that first screen, execution goes into RolapConnection.execute, shepherdExecution method is called but the executeInternal (line 628) is not called - only after execution is resumed on the previous breakpoint.
Apparently, if I wait long enough (about 4 minutes), the second thread will go into executeInternal due to a new request coming in from JPivot.
Steps to reproduce:
Open Analysis View - Create connection over steel-wheels and issue a top count query. We have a breakpoint set in RolapNativeTopCount so execution stops there.
Open another analysis View - Create connection over SampleData (another cube which should rule out cache sharing, I guess) .
Mondrian is called to get that first screen, execution goes into RolapConnection.execute, shepherdExecution method is called but the executeInternal (line 628) is not called - only after execution is resumed on the previous breakpoint.
Apparently, if I wait long enough (about 4 minutes), the second thread will go into executeInternal due to a new request coming in from JPivot.
Issue Links
- is duplicated by
-
MONDRIAN-1165
Parallel mdx queries
-