ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

iReporter: Report Timing Out - java.net.SocketTimeoutException: Read timed out

book

Article ID: 38255

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) NIMSOFT PROBES

Issue/Introduction


iReporter: Report Timing Out - java.net.SocketTimeoutException: Read timed out



Cause

IReport time is not correctly set

Environment

UIM 8.5

iReporter

Resolution

There is a timeout value in iReport that can get adjusted in Tools –> Options –> iReport –> JasperReports Server Repository. By default this value is set to zero which indicates no timeout, but it still does. Adjusting this setting to 100,000 resolved the problem.
 
Another value is in <Nimsoft_Home_Dir>\probes\services\wasp\webapps\jasperserver-pro\WEB-INF in a file called web.xml
 
There is a section that looks like this:
<session-config>
    <!-- Default to 20 minute session timeouts -->
    <session-timeout>120</session-timeout>
</session-config>
 
By default, Nimsoft has a value of 720 in there. Bumping it to 10000 seems to have resolved the problem when running the report from a web session as opposed to iReport.

Additional Information

This timeout value along with the setting in iReport is related to a web services call that is made to apache. If the timeout is reached the axis service in apache closes the request.

Powered by Wolken Software