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.

While running WebSerive Jobs simultaneously receive Call Failed with Socket Closed error

book

Article ID: 84950

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
com.automic.http.client.exception.HttpRequestException: Socket Closed

While running multiple Web Service Jobs simultaneously, one or more Jobs fail with a call failed with Socket Closed error similar to the one above.

Investigation

Step to reproduce:
  • Load Web Service SOAP 4.1 and start the RA Agent
  • Create a Web Service SOAP  test Job with a request to http://www.webservicex.com/CurrencyConvertor.asmx?wsdl or any wsdl.
  • Duplicate the test Job 5 times to create 5 identical jobs
  • Run all 5 test Jobs recurring every 1 minute.
Results

Actual:  Some Jobs fail with the following error:
com.automic.http.client.exception.HttpRequestException: Socket Closed
at com.automic.soap.client.nat.NativeWebServiceClient.getResponse(NativeWebServiceClient.java:122)
at com.automic.soap.client.nat.NativeWebServiceClient.callSAAJWS(NativeWebServiceClient.java:69)
at com.automic.soap.client.nat.NativeWebServiceClient.invokeMethod(NativeWebServiceClient.java:142)
 
Expected:  All jobs should run successfully.

Cause

Cause type:
Defect
Root Cause: Web Service Jobs fail sporadically if executed in parallel.

Environment

OS Version: N/A

Resolution

Update to a fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Web Service SOAP Solution 4.2 - Available

Additional Information

Workaround :
N/A
Powered by Wolken Software