Devtest Server is installed on AWS linux EC2 instance and is accessed behind an NLB-Proxy set up , through a VPCE DNS. When we start the components, They are running on private subnet IP addresses. They have configured a load balancer.
Registry and Portal are correctly picking up the VPCE hostname. Simulator, Coordinator, and VSE are running on a private IP subnet. The issue we are facing is , We are unable to deploy virtual services from my Workstation as the default VSE is shown to have the Private subnet ip, which cannot be accessed.
This is the error we are getting:
Workstation.log
java.rmi.RemoteException: JMS Messaging problem with ServerRequestHandler for tcp://ip-127.0.0.1:2013/VSE Could not connect to broker URL: tcp://ip--127.0.0.1:2013?wireFormat.maxInactivityDuration=0. Reason: java.net.UnknownHostException: ip-127.0.0.1; nested exception is:
Caused by: java.net.UnknownHostException: ip-127.0.0.1
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
Vse.log
Creating a virtual service environment:
... VSE Server name: tcp://<VseHost>:2013/VSE
..... Registry name: tcp://<RegistryHost>:2010/Registry
Cannot register with the DevTest Registry [Timed out trying to connect to test registry tcp://<RegistryHost>:2010/Registry]
java.rmi.RemoteException: Timed out trying to connect to test registry tcp://<RegistryHost>:2010/Registry
at com.itko.lisa.test.Environment.bootUpTestRegistry(Environment.java:2750)
at com.itko.lisa.test.Environment.setTestRegistry(Environment.java:2729)
at com.itko.lisa.test.Environment.setTestRegistry(Environment.java:2686)
We want all the components to start with VPCE hostname
Release : 10.7
Component : DevTest Workstation
Registry and Portal are correctly picking up the VPCE hostname.
Simulator, Coordinator, and VSE are running on a private IP subnet.
1. In the linux environment, Map in /etc/hosts file localhost --> <ServerHostName>
127.0.0.1 localhost <ServerHostName>
2. For each Service vmoptions and add the below properties
1. Registry
-Dlisa.registry.url=tcp://<ServerHostName>:2010/Registry
-Dlisa.registryName=tcp://<ServerHostName>:2010/Registry
2. VirtualServiceEnvironmentService.vmoptions
-Dlisa.vseName=tcp://<ServerHostName>:2013/VSE
3. SimulatorService.vmoptions
-Dlisa.simulatorName=tcp://<ServerHostName>:2014/Simulator
4.CoordinatorService.vmoptions
-Dlisa.coordName=tcp://<ServerHostName>:2011/Coordinator
In PortalService-> SERVER Health, we are able to see that all the components are now starting with the right name <ServerHostName>