Connection issues when pointing VSE services to Registry server:ERROR com.ca.sv.invoke.controller.v2.VseServerController - JMS Messaging problem

Products

• CA Application Test
• Service Virtualization

Issue/Introduction

Seeing issues when trying to connect VSE services to a new Registry server. These issues are blocking any VSE services from connecting to Registry server.

Registry log shows below errors:

Caused by: com.itko.jms.JMSException: Could not connect to broker URL: tcp://vseHost:2013?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection timed out: connect
 at com.itko.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)

and

2020-04-23 23:15:41,418Z (18:15) [qtp2046211968-2382] ERROR com.ca.sv.invoke.controller.v2.VseServerController - JMS Messaging problem with ServerRequestHandler for tcp://vseHost:2013/xxxxx-1234 Could not connect to broker URL: tcp://vseHost:2013?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection timed out: connect; nested exception is:
 com.itko.jms.JMSException: Could not connect to broker URL: tcp://vseHost:2013?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection timed out: connect
java.rmi.RemoteException: JMS Messaging problem with ServerRequestHandler for tcp://vseHost:2013/xxxxx-1234 Could not connect to broker URL: tcp://vseHost:2013?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection timed out: connect; nested exception is:
com.itko.jms.JMSException: Could not connect to broker URL: tcp://vseHost:2013?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection timed out: connect
at com.itko.lisa.net.Transporter.init(Transporter.java:412)

 

Environment

Release : All supported versions of DevTest

Component : CA Service Virtualization

Cause

Firewal not open both ways for Registry to VSE server and vice versa. Tried to ping from both machines as below.

1. Registry machine -> VSE on VSE Port ( This failed)
2. VSE machine -> Registry on Registry Port( This worked)

Resolution

Work with your network team for Firewall configuration on both servers. Do Telnet or netcat or any other tool to verify connectivity both ways on the Registry and VSE Ports.

NOTE: Connectivity need to be open bidirectional between Registry and VSE.