Hello Team,
A client of ours is running
eazybi 4.7.1 on
jira 7.13.0 via
java 1.8.0_172
They report the eazybi child dying and logs reveal:
[root@lumeris-jira01 log]# tail -n100000 -f /opt/j2ee/domains/lumeris.com/jira/data/log/eazybi-child.out
…
Puma 2.14.0 starting…
- Min threads: 0, max threads: 20
- Environment: production
- Listening on tcp://127.0.0.1:3801
java.lang.NullPointerException
at mondrian.rolap.cache.SegmentCacheIndexImpl$HeaderInfo.access$100(SegmentCacheIndexImpl.java:1048)
at mondrian.rolap.cache.SegmentCacheIndexImpl.loadSucceeded(SegmentCacheIndexImpl.java:272)
at mondrian.rolap.agg.SegmentCacheManager$Handler.visit(SegmentCacheManager.java:604)
at mondrian.rolap.agg.SegmentCacheManager$SegmentLoadSucceededEvent.acceptWithoutResponse(SegmentCacheManager.java:1122)
at mondrian.rolap.agg.SegmentCacheManager$Actor.run(SegmentCacheManager.java:1034)
at java.lang.Thread.run(Thread.java:748)
java.lang.NullPointerException
at mondrian.rolap.cache.SegmentCacheIndexImpl$HeaderInfo.access$100(SegmentCacheIndexImpl.java:1048)
at mondrian.rolap.cache.SegmentCacheIndexImpl.loadSucceeded(SegmentCacheIndexImpl.java:272)
at mondrian.rolap.agg.SegmentCacheManager$Handler.visit(SegmentCacheManager.java:604)
at mondrian.rolap.agg.SegmentCacheManager$SegmentLoadSucceededEvent.acceptWithoutResponse(SegmentCacheManager.java:1122)
at mondrian.rolap.agg.SegmentCacheManager$Actor.run(SegmentCacheManager.java:1034)
at java.lang.Thread.run(Thread.java:748)
Exiting
…
System events show errors like:
Mondrian::OLAP::Error: org.olap4j.OlapException: Mondrian Error:Query timeout of 60 seconds reached
{
“cube”: “Issues”,
“cube_table”: “jira_issues_measures”,
“cube_report_id”: 531,
“dashboard_id”: 51,
“embed”: “embed dashboard”,
“initial_query”: false,
“mdx”: “”"
SELECT {[Measures].[Issues resolved], [Measures].[Today Line], [Measures].[Component Release], [Measures].[Product Release]} ON COLUMNS,
FILTER([Time].[Day].Members, DateBetween([Time].CurrentHierarchyMember.StartDate, DateSerial(2019,4,21), DateSerial(2019,8,19))) ON ROWS
FROM [Issues]
WHERE ([Feature Fix Version.By name].[SQL 2017 Migration], [Project].[All Projects])
“”",
“account_id”: 6,
“user_id”: null,
“root_cause_message”: “Query timeout of 60 seconds reached”,
“root_cause_backtrace”: [
“root cause: mondrian.olap.QueryTimeoutException: Mondrian Error:Query timeout of 60 seconds reached”,
“root cause: mondrian.resource.MondrianResource$_Def13.ex(MondrianResource.java:1214)”,
“root cause: mondrian.server.Execution.checkCancelOrTimeout(Execution.java:252)”,
“root cause: mondrian.rolap.RolapResultShepherd.shepherdExecution(RolapResultShepherd.java:171)”,
“root cause: mondrian.rolap.RolapConnection.execute(RolapConnection.java:607)”,
“root cause: mondrian.olap4j.MondrianOlap4jCellSet.execute(MondrianOlap4jCellSet.java:87)”,
“root cause: mondrian.olap4j.MondrianOlap4jStatement.executeOlapQueryInternal(MondrianOlap4jStatement.java:415)”,
“root cause: mondrian.olap4j.MondrianOlap4jPreparedStatement.executeQuery(MondrianOlap4jPreparedStatement.java:72)”,
“root cause: mondrian.olap4j.MondrianOlap4jPreparedStatement.executeQuery(MondrianOlap4jPreparedStatement.java:42)”,
“root cause: sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)”,
“root cause: sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)”,
“mondrian/olap4j/mondrian/olap4j/MondrianOlap4jConnection.java:858:increateException'", "mondrian/olap4j/mondrian/olap4j/MondrianOlap4jStatement.java:420:inexecuteOlapQueryInternal’”,
“mondrian/olap4j/mondrian/olap4j/MondrianOlap4jPreparedStatement.java:72:inexecuteQuery'", "mondrian/olap4j/mondrian/olap4j/MondrianOlap4jPreparedStatement.java:42:inexecuteQuery’”,
“java/lang/reflect/java/lang/reflect/Method.java:498:in `invoke’”
],
“exception”: [
“Mondrian::OLAP::Error”,
“org.olap4j.OlapException: Mondrian Error:Query timeout of 60 seconds reached”
]
}
Is there something wrong with the query?
I was looking for bug reports and upgrades resolving this issue but so far no luck.