Symptoms
IBP job errors related to SocketTimeoutException or SocketException
Cause
The reason that you are seeing timeouts with V2 of the connector is that V2 added support for setting IBP Job parameters from RMJ. When the job is run from RMJ we attempt to fetch the parameters from the remote job so we can merge them with the values provided in RMJ. When the IBP Job has many parameters, this call can take a long time to complete, in some cases longer than the default timeout setting which is why the timeout exception is happening.
The long delay in starting the job happens when you see this timeout because it attempts to retry the call a certain number of times with a wait in between, so that does cause the delay if it continues to timeout.
Workaround
Create following Registry Entries to increase the default timeouts
valid for IBP v1 and v2
/configuration/sap/ibp/connecttimeout with value 120
/configuration/sap/ibp/sockettimeout with value 120
valid for IBP v2 only
/configuration/jcs/apps/SAP/IBP/ConnectTimeout with value 120
/configuration/jcs/apps/SAP/IBP/SocketTimeout with value 120Affected version
IBP v2
Resolution
n/a
Reference
-
Error
WARN 2024-03-06 08:04:37,265 GMT [Redwood Job Thread Pool: xxxIBP worker 0-Executor 1778] job.Redwood_IBP_SubmitJob.280096774 - Failed to fetch parameters for template xxx. The job will be submitted without parameters.
java.net.SocketTimeoutException: Read timed out
Caused by: java.net.SocketException: Network is unreachable
Comments
0 comments
Please sign in to leave a comment.