Problem Description:
******************************
We encountered problem to deploy a virtual service to DevTest environment in Bay Pines. Both Functional and Performance servers give error message below. I highlighted a potential problem – it uses host name “tcp://APPDVTFN1:2013" Instead of fully qualified names
functional VSE - APPDVTFN1.pt1.pt2.pt3.pt4
Performance VSE - APPDVTVS1.pt1.pt2.pt3.pt4
java.rmi RemoteException: JMS Messaging problem with ServerRequestHandler for tcp://APPDVTFN1:2013/
com.itko.jms.JMSException: Could not connect to broker URL: tcp://APPDVTFN1:2013?
at com.itko.lisa.net.Transporter.
at com.itko.lisa.net.Transporter.
at com.itko.lisa.net.Transporter.
at com.itko.lisa.net.Transporter.
at com.itko.lisa.net.Transporter.
at com.itko.lisa.net.Transactor.
at com.itko.lisa.net.ClientBase.
at com.itko.lisa.net.ClientBase.
at com.itko.lisa.net.ClientBase.
at com.itko.lisa.net.VSEClient.
at com.itko.lisa.vse.ui.actions.
at com.itko.util.swing.panels.
at java.lang.Thread.run(Thread.
Caused by: com.itko.jms.JMSException: Could not connect to broker URL: tcp://APPDVTFN1:2013?
at com.itko.activemq.util.
at com.itko.activemq.
at com.itko.activemq.
at com.itko.activemq.
at com.itko.lisa.net.
at com.itko.lisa.net.Transporter.
at com.itko.lisa.net.Transporter.
... 12 more
Caused by: java.net.UnknownHostException: APPDVTFN1
at java.net.
at java.net.PlainSocketImpl.
at java.net.SocksSocketImpl.
at java.net.Socket.connect(
at com.itko.activemq.transport.
at com.itko.activemq.transport.
at com.itko.activemq.util.
at com.itko.activemq.transport.
at com.itko.activemq.transport.
at com.itko.activemq.transport.
at com.itko.activemq.transport.
at com.itko.activemq.transport.
at com.itko.activemq.
* DevTest 10.5.0
* All server components running on Windows 2012 R2
IAM, Enterprise Dashboard, Registry and Portal running on the same machine
Coordinator, Simulator and both VSEs running on separate machines.
* No DevTest patches applied.
Deploying VSM from Workstation to both the functional and performance VSEs on the test environment and get error.
This is a test environment that is not used as much and seems to be working as of last Friday, 04/09/2021.
Starting on Monday, the error now occurs.
No known changes have been made in this environment.
From the Registry Monitor on the Workstation the Virtual Service tab is showing MIA VSE for both functional and performance VSEs.
Able to ping and telnet to both machines from the Workstation machine.
1. Added these properties to the VirtualServiceEnvironmentServi
-Dlisa.registryName=tcp://APPDVTRG1.pt1.pt2.pt3.pt4:
-Dlisa.vseName=tcp://APP
2. Added this property to the VirtualServiceEnvironmentServi
-Dlisa.registryName=tcp://APPDVTRG1.pt1.pt2.pt3.pt4:
-Dlisa.vseName=tcp://APP
3. Brought down Portal, Registry, Enterprise Dashboard and IAM services in this order.
4. Deleted folder C:\Program Files\CA\Devtest\lisatmp_10.5.
5. Noticed there was a C:\Program Files\CA\Devtest\tmp.txt file but no C:\Program Files\CA\Devtest\tmp folder. The tmp folder is where OOM hprof files get written to, not sure why there was no folder, so created one and then rename the tmp.txt file to something else.
6. Started IAM, Enterprise Dashboard, Registry and Portal services.
7. Brought down function and performance VSEs.
8. Deleted folder C:\Program Files\CA\Devtest\lisatmp_10.5.
9. Was then able to deploy with no errors.
Next Actions - Customer
*****************************
1. On the Coordinator machine add these properties to the CoordinatorService.vmoptions file:
-Dlisa.registryName=tcp://APPDVTRG1.pt1.pt2.pt3.pt4:
-Dlsa.lisa.coordName=//<fully qualified name of Coord machine>:2011/Coordinator
2. Restart Coordinator service.
3. On the Simulator machine add these properties to the SimulatorService.vmoptions file:
-Dlisa.registryName=tcp://APPDVTRG1.pt1.pt2.pt3.pt4:
-Dlsa.lisa.simulatorName=//<
4. Restart Simulator service.