Hi, Do you get this for all the reports or only for one report? And are you testing in a LIVE copy environment? or in the LIVE itself?

Can you also let me know the service pack level in Apps7.5?

Hi @Rohini S 
Most Probably this may due to huge data load. As work around the user runs the report in background and makes the preview from the report archive instead. Since the report itself contains of many thousands of pages, its very difficult to preview it online.

Please let us know the report name as R&D gives some bug fixes for some reports

Ex:

 General Ledger Report
-Best Regards

Hi @Nalaka Samarasinghe , Currently I am testing this in Live Copy environment and it is the same in Live environment as well. This is happening only for a particular report 

Can you also let me know the service pack level in Apps7.5? it is SP6

Hi @Kelum Niranjana This is FA year Report

Hi @Rohini S, If your error is thrown after a predefined time out (like 30 minutes), then you will need to increase the timeout values of IFS framework timeout and oracle DB Default timeout. Because a correction has been made via SP3 for App75 version. Do you have access to IFS solutions and their information?

In IFS Solution  184959  it suggest as below 

Since the report size is quite large, you  should have the required resources like Hard Disk space and memory. Need to have more than 5GM Disk space for caching and enough memory to process the job. For an example if the XML is 420MB It might take approximately 3 hours for processing, this might generate timeout issues as our framework and Oracle DB default timeout values are less than 3 hours. 

So you need to change the following timeouts as well. So please change the following for at least 4 hours in this particular instance. 

1. “Timeout” in the Apache config file: <ifs_home>\apache2\conf\httpd.conf. This should be set in seconds, so a value of more than 14400(4*60*60) would be necessary. 
2. “connection_pool_timeout” in the worker configuration for the connection between Apache and Jboss: <ifs_home>\apache2\conf\worker.properties. This is set in seconds. Again, more than 14400 here. 
3. “socket_timeout” in the same file as above (2). Again, in seconds. 
4. “Utl_Http.Set_Transfer_Timeout(600);” in the database package WEB_SERVICES_UTIL_API inside Invoke method must be changed. This is set in seconds just like the above parameters. Change this and compile the package. I know this is a little bit awkward but there is not configuration to change for this so it must be handled with a customized version of this package. 
5. In sqlnet.ora. ($ORACLE_HOME/network/admin) where you can set EXPIRE_TIME which dictates how long a client session can stay inactive For more details  it's recommended for you to go for a external report formatter (ERF), and apply the bugs and the configurations as mentioned above. The purpose of using an external Report Formatters is to offload the central application server and to eliminate disturbance for other processes which runs on the server. For more details and for steps of configuration of ERF refer: http://wis.ifsworld.com/f1docs/apps75/Foundation1/030_configuration/040_configure_output_reports/015_setup_external_report_formatters/default.htm

Check whether this is relevant to your issue.

Best Regards
 

Hi actually this is not the case of time out error as i get the error within 5 to max 10minutes.

Hi @Rohini S, In that case, can you check the timeout values in the locations where Kelum has mentioned in the above comment to see whether it has been set a very low value?

If nothing helps and no further assistance received from this post, it would be good to raise a IFS Support case for an in detailed technical investigation.