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
![]()
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.
|
![]()
BTW - The better fix would be to use JRS as a data source, which would allow us to better control how much data is being sent to RPE, but JRS does not return artifacts with format of "module". I put in an enhancement request for that last year which is being targeted for 6.0.2.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.