Getting error: Double connect reset occurred using a virtual service

book

Article ID: 141267

calendar_today

Updated On:

Products

CLOUDTEST CA Application Test CA Cloud Test Mobile MOBILECLOUD Service Virtualization

Issue/Introduction

When hitting request against a deployed virtual service, getting below error:

============================================================================

| java.lang.RuntimeException: Double connect reset occurred. Please contact CA support.

============================================================================

| Step:        Virtual HTTPS Live Invocation 8443

----------------------------------------------------------------------------

| Message:     Double connect reset occurred. Please contact CA support.

----------------------------------------------------------------------------

| Trapped Exception: Double connect reset occurred. Please contact CA support.

| Trapped Message:   java.lang.RuntimeException: Double connect reset occurred. Please contact CA support.

----------------------------------------------------------------------------

STACK TRACE

java.lang.RuntimeException: Double connect reset occurred. Please contact CA support.

at com.itko.lisa.vse.stateful.protocol.http.HttpLiveInvocationStep.execute(HttpLiveInvocationStep.java:473)

at com.itko.lisa.test.TestNode.executeNode(TestNode.java:995)

at com.itko.lisa.test.TestCase.execute(TestCase.java:1297)

at com.itko.lisa.test.TestCase.execute(TestCase.java:1198)

at com.itko.lisa.test.TestCase.executeNextNode(TestCase.java:1183)

at com.itko.lisa.test.TestCase.executeTest(TestCase.java:1124)

at com.itko.lisa.coordinator.Instance.run(Instance.java:208)

============================================================================

 

Environment

Release : 10.x

Component : CA Service Virtualization

Resolution

The error being received could be due to the following reasons and would need corresponding actions.

- Make sure that the Live endpoint for this service is accessible from the VSE server. We can test this by using telnet to command or curl command to the live endpoint on Linux machine.

e.g. # curl [target_hostname]

If successful some HTML response would be returned, if not, then involve the network team for enabling the access at firewall level.


- A proxy setting might have been enabled in local.properties file of VSE installation that is applicable for all virtual services and the Live server call for this specific service is failing due to that proxy. You can verify that by looking into the local.properties file and follow the below article to make changes only for the service(s) that need the proxy for Live Server call. 

https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=122748

- As the Live endpoint is being accessed on SSL, make sure that the certificates being used in the Live Invocation Step can be verified correctly. In case, the passwords are verified correctly and the issue persists then please add below property to local.properties file of VSE installation and restart VSE service.

https.protocols=TLSv1.2,TLSv1.1,TLSv1