nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

BIRT rptdocument getting generated even when browser is closed in Maximo

vijay_kota

Hi All,

Any one have idea about rptdocument during runtime..??

I have a report, when i run this report rptdocument of size 30 GB getting generated in Maximo.

I just closed report browser, but still rptdocument growing. Is there any way i can stop this in my script..??

Cluster is configured and temporary file is getting saved in a particular physical path.

Any suggestion appreciated..

Thanks and Regards,

Vijay

Find more posts tagged with

Comments

CBR

Hi,

the server is not getting notified if the client browser is closed. If you fire a request to the server the request is always handled completely. It doesn't matter if you close the browser your do anything else. The only way to stop a request from beeing processed is to kill the server process (which normally means that you stop your server).

A rptdocument of 30GB is caused by loading to much data from your database. Do you use subreports?
Can you revise your database query to see if you load to much unnessary data?

vijay_kota

Cbrell,

Yes, report is having many sub reports.

Works great when user runs for a set of parameter from application.

cause of concern is when user runs this report by mistake for all records its obviously creates huge rptdocument file.

In a normal scenario maximo handles temporary file deletion when procees gets completed.

Since user runs for all records(more than 30,000 and this is not intentional) browser gets hanged and he just closes that... But in the back end huge rptdocument gets created like a infinite loop.

Yes you are right by stopping server we can delete the file.

But i am trying with out server stoppage.

paulk

In the Report Administration application, you can limit the number of records that will run for that report. An error message will occur telling the user to select less records before the report can run.

vijay_kota

Hi Paul,

This is only possible when there is no parameter.

In my case i do have a non mandatory parameter.

Regards,

Vijay

paulk

You could change the queries for the datasets within the report to limit the records, SELECT TOP N for SQL.

Create an extra dataset with just COUNT(*) that has the same where conditions. If the COUNT(*) is greater than N, display a message to the user stating the report was trimmed to N records and rerun the report with tighter criteria.

vijay_kota

Paul,

That a really good idea.. I will try and implement this.

Thanks a lot..:)

Regards,

Vijay

wwilliams

You should be able to add something like this to the beforeFactory. 
 
<pre class='_prettyXprint _lang-auto _linenums:0'>
reportContext.getDesignHandle().findDataSet("mainDataSet").rowFetchLimit = params["row_limit"].value;

</pre>
 
-W 
 
<blockquote class='ipsBlockquote' data-author="'vijay_kota'" data-cid="107658" data-time="1343651588" data-date="30 July 2012 - 05:33 AM">
Paul, 
 
That a really good idea.. I will try and implement this. 
 
Thanks a lot..:) 
 
Regards, 
 
Vijay </blockquote>

vijay_kota

Hi Wwilliams,

This is similar to limiting number of rows in data set settings right...??

Regards,

Vijay

wwilliams

<blockquote class='ipsBlockquote' data-author="'vijay_kota'" data-cid="108847" data-time="1346047469" data-date="26 August 2012 - 11:04 PM">
Hi Wwilliams, 
 
This is similar to limiting number of rows in data set settings right...?? 
 
Regards, 
 
Vijay </blockquote>

wwilliams

Yes, same thing