What can cause IO Exception (java.net.SocketException) in RPE?
I have an RPE report that has been running perfectly for a few months but suddenly started failing. When I run it in the RPE Launcher, the console shows an IO Exception / SocketException and resets the connection. The rpe.log shows no errors.
The underlying REST API query returns data from the Browser, but causes the above error when run from RPE. The only difference from when the report was working and started failing is the volume of data being returned.
Any guidance would be greatly appreciated.
Thanks,
Robert
3 answers
The user may not be a member of the RM project or it was removed from the project. If so, try to add it into that RM project. You'd better go through rm.log and rpe.log for the detail.
Comments
Unfortunately, nothing in the rm or rpe logs.
This issue has to do with volume of data being returned by the REST API. The driving REST query is pulling from a view of modules. If I add an additional filter to reduce the number of modules in the view, everything works. Also, I believe the report stopped working because the volume of data returned by the view grew over time.
However, it is not a ridiculous amount of data coming back (197 modules), and the REST query will return the data to the browser. It only seems to break in RPE.
I found a way to get the report to run in RPE by using the "size=" parameter. Apparently, the default of 100 artifacts per REST call was too much for RPE and RRDG to handle when returning information on modules. We will have to adjust the default count in the RM advanced properties to get this to work on the server.