Skip to Content
Former Member
Aug 28, 2015 at 02:48 AM

How to find which WebI Report(s) is causing Out of Memory


We are randomly getting "Exception in thread "Thread-43" java.lang.OutOfMemoryError" in WebSphere SystemErr.log with a timestamp. But we are not sure which user/WEBI report causes this in BOXI 3.1

I have access to Query Builder and Auditor information. I believe Auditor has historical information that I am looking for and not Query Builder.

I know how to troubleshoot heap dump and narrow down to Java classes causing out of memory.

But with BOXI application I am not sure if there is anyway I can pin point the problem report.

Things I have:

- Date/time when out of memory was thrown

- Auditor schema

- Query Builder

- WebSphere and XI3.1 Logs.

- Oracle AWR report that shows possible problematic SQL that retrieves millions of records. But I am not sure how to pin point the report or at least the universe using that.

I am trying to achieve this without having to use SDKs.