Memory leak of reportSource in session

[Former Member]

Hi there,

I have been working with Crystal Reports for Java for a few weeks now. Right now I try to keep the memory usage steady in my application while I open several reports.

For every report I open a session variable is added when I call viewer.processHttpRequest. This is the variable from the session:

com.crystaldecisions.report.web.viewer.RPT_SRC:CrystalViewer967219=com.crystaldecisions.sdk.occa.report.application.AdvancedReportSource@ec233

After cleaning my own dataSource and ReportClientDocument this variable stays in the session. By every report I open there is another one added to my session.

Is this a memory leak in the CR api or do I need to destroy this variable myself??

[Former Member]

Every time I call the method reportClientDocument.getReportSource an extra ReportSource is added to my session. Can I use this attribute in the session in my own code? Than I don't need to put the reportSource in the session myself and I can clean the session attribute when I'am finished.

What value do I need to use to access the sessions attribute with the ReportSource in it???

[Former Member]

Thanks for your reply!

I'am using CR for Eclipse 2.2.

What can I do about it? Is it a request to the servlet that shouldn't be fired should there be a method call to cleanup these resources. I don't want my session to be polluted with these resources.

Thanks for your time...

[ted_ueda]

It's where the ReportSource is cached for CrystalReportViewerServlet to use.

It's persists after you clean up your own objects - there may be outstanding client requests coming into the CrystalReportViewerServlet.

Note that the ReportSource object itself isn't the report object - it's a reference to the report object held by the backend (whether that happens to be the Java ER Print engine used by CR4E or the RAS server), so not resource heavy.

This is new with Crystal Reports 2008 and Crystal Report for Eclipse 2.0

Sincerely,

Ted Ueda