VSE unable to start with java.net.NoRouteToHostException

book

Article ID: 222403

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

VSE is not able to start with below error in vse.log:


ERROR com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Cannot register with the De
vTest Registry [JMS Messaging problem with ServerRequestHandler for tcp://VSEhostname:2013/VM_FuncVSE_Tmp Could not connect to b
roker URL: tcp://VSEhostname:2013?wireFormat.maxInactivityDuration=0. Reason: java.net.NoRouteToHostException: No route to host
(Host unreachable); nested exception is:
        com.itko.jms.JMSException: Could not connect to broker URL: tcp://VSEhostname:2013?wireFormat.maxInactivityDuration=0. R
eason: java.net.NoRouteToHostException: No route to host (Host unreachable)]
java.rmi.RemoteException: JMS Messaging problem with ServerRequestHandler for tcp://VSEhostname:2013/VM_FuncVSE_Tmp Could not co
nnect to broker URL: tcp://VSEhostname:2013?wireFormat.maxInactivityDuration=0. Reason: java.net.NoRouteToHostException: No rout
e to host (Host unreachable); nested exception is:
        com.itko.jms.JMSException: Could not connect to broker URL: tcp://VSEhostname:2013?wireFormat.maxInactivityDuration=0. R
eason: java.net.NoRouteToHostException: No route to host (Host unreachable)
        at com.itko.lisa.net.Transporter.init(Transporter.java:412)

Cause

Problem is communicating from the Registry to the new VSE. The communication has to be open 2 ways between VSE and Registry.

Environment

All supported DevTest releases and platforms.

Resolution

Perform below steps:

> On VSE machine, run the below command:

sudo ncat -l 2013

This will open a TCP service listening on port 2013

> On Registry machine run below command

telnet <VSEHostOrIP> 2013

Make sure you are connected.

> If you get any error, report it to your network team and make sure this connection works.

> If you are able to connect, then open a support case and share the latest VSE log and the Registry log covering the issue replication time.

Additional Information

Communication Requirements
Ensure that your firewall allows 
DevTest Solutions
 to send and receive network transmissions. The functionality that DevTest Solutions provides requires access to network resources and does not work properly when blocked by a firewall. Authorize DevTest Solutions applications.
All DevTest server components must have access to the External Database the Registry is connecting to. Each DevTest server component communicates directly with the database to record their actions. Any restriction to the flow of this data has adverse effects.