VSM fails to connect to live endpoint and throws the exception java.net.SocketException: Connection reset

Document ID : KB000094808
Last Modified Date : 16/10/2018
Show Technical Document Details
Introduction:
This document describes some steps that can be taken when a Virtual Service fails with the exception 'java.net.SocketException: Connection reset' while trying to connect to the live system specified in the Live Invocation step.
Here is the exception thrown in the VSE log files:
============================================================================
| java.net.SocketException: Connection reset
============================================================================
| Step:        Virtual HTTPS Live Invocation 80
----------------------------------------------------------------------------
| Message:     Connection reset
----------------------------------------------------------------------------
| Trapped Exception: Connection reset
| Trapped Message:   java.net.SocketException: Connection reset
----------------------------------------------------------------------------

 
Environment:
All supported DevTest releases.
Instructions:
The 'java.net.SocketException: Connection reset' exception appears when the remote connection is unexpectedly and forcefully closed due to various reasons like application crash, system reboot, a hard close of the remote host.
If the problem is intermittent, verify if there is any kind of connectivity issues in the environment. Performing a test using the ping command can be helpful.
In the VSE Server open a command prompt and ping the target system configured in the Live Invocation step:
# ping -t <LiveSystemIPaddress or HostName>
with the option '-t', without quotes, it will ping the target until you force it to stop by using Ctrl+C.

Leave this command running for some time, or until you face the issue.
If there is a connectivity issue, you will most likely see some packets being lost.
Save the ping statistics for future reference.

It can be that ICMP echo (used for ping) may have been disabled in the environment. If that is the case we will not be able to use the ping command for testing.

If there are no connectivity issues in the environment, please open a support ticket and consider capturing the network traffic in the VSE server.
Wireshark can be used for Windows environment and tcpdump can be used for Linux environment.
Refer to the article on how to capture network traffic using tcpdump command - KB000094804.