Remote VSE unable to start: Cannot register with the DevTest Registry timeout

book

Article ID: 140223

calendar_today

Updated On:

Products

CLOUDTEST CA Application Test CA Cloud Test Mobile MOBILECLOUD Service Virtualization

Issue/Introduction

When trying to start a VSE that is remote to the registry, the VSE fails to start with this message in the vse.log: 
ERROR com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Cannot register with the DevTest Registry [Unable to add incoming VSE with a service name of tcp://192.168.10.10:2013/VSE5 - connection timed out after 5000 milliseconds.]

The following property was configured in vmoptions to connect to the registry:
-Dlisa.registry.url=tcp://registryserver:2010/Registry
There was no problem for the Workstation to connect to this registry.

The name of the VSE was configured in vmoptions with:
-Dlisa.vseName=tcp://192.168.10.10:2013/VSE5

Cause

The registry received the connection request from the VSE but cannot connect back to the VSE server using ip address 192.168.10.10 and port 2013

Environment

Release : 10.3

Component : CA Service Virtualization

Resolution

The registry.log showed: 

ERROR com.itko.lisa.coordinator.TestRegistryImpl - Unable to add incoming VSE with a service name of tcp://192.168.10.10:2013/VSE5 - connection timed out after 5000 milliseconds.

This means the registry received the connection request from the VSE but cannot connect back to the VSE server using ip address 192.168.10.10 and port 2013


Running ping to the VSE server on the registryserver confirmed that there was a problem to connect to the IP address:

ping 192.168.10.10

"Time to live Exceeded"


Another problem might have been that port 2013 was blocked by a firewall.


Using the hostname of the VSE server showed no errors for ping.

The problem was resolved after configuring the hostname of the VSE server in vmoptions with:

-Dlisa.vseName=tcp://vseserver:2013/VSE5

Additional Information

See the following document for requirements regarding TCP network connectivity between DevTest components:

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