SV - DevTest 10.4 - One of the VSEs is not coming up

book

Article ID: 211395

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

One of the 4 VESs in one of the VSE servers is not coming up. Could see the "port already in use" exception when tried to start the standalone VSE component. 

Cause

You were having JMX properties set in s4 VSE vmotpions file with port 9004 set. 

Since there is a VS already deployed on this port, it couldn't use that when starting s4 VSE. 

Environment

Release : 10.4

Component : CA Service Virtualization

Resolution

We renamed the s4 VSE specific folders from VSBuilderSessions and VSERecordings folders. 

For now we commented the JMX properties for S4, if you want to continue the monitoring you can use a different port and configure the same on the monitoring tool.