BO4 - Idle Connection Timeout + session timeout apply to scheduled reports

[former_member272336]

Hi,

We are reducing our session timeout  (web.xml) and idle connection timeout settings on web intellignce processing servers.

Assume both of these settings are applicable to scheduled reports.

Is this the case?

Thanks

[Former Member · Accepted solution]

Idle Connection Timeout (minutes): it is for WIPS

Specifies the amount of time, in minutes, that the server waits for a request from an idle connection. Setting a value that is too low can cause a request to close prematurely. Setting a value that too high can caused requests to be queued while the server waits for idle requests to be closed.

Default value is 20 (minutes)

Session Timeout in (web.xml): this is for the Web application server/Tomcat

This will be for the Web application server/Tomcat timeout.

Reducing Session Timeout in Web.XML will not impact the schedules. Scheduling is completely based on the BOE services.

[Former Member · Accepted solution]

Hello,

If you're scheduling a document, it is not really to worry about the web application timeout (web.xml) in case you're sending the instance to a user inbox.
However, you have to worry about the timeout of the connection to the database and the processing servers. You have to give them a sufficient time for the processing of the amount of data to be sent to the instance.

Best Regards,

Insaf

[Former Member]

I agree with Insaf here, we need not make any changes to the timeout of web server. I would suggest to check initially to retrive lesser data while report is being scheduled. This will help to understand whether the issue is with huge amount of data being pulled in.

I would also suggest you to fire the report query against your database and find the time taken to retrieve data. Post these checks; it would be advisable to modify timeout change at WIPS level.

[former_member272336]

Thanks all for the great advice.