JMS Messaging problem with ServerRequestHandler for tcp://mycomputer1:2013/Func_VSE Could not connect to broker Reason: java.net.UnknownHostException

Products

• Service Virtualization

Issue/Introduction

Encountered problem to deploy a virtual service to DevTest environment. Both Functional and Performance servers give error message below. Looks like, it uses hostname “tcp://mycomputer1:2013" Instead of fully qualified names

functional VSE - mycomputer1.pt1.pt2.pt3.pt4

Performance VSE - mycomputer2.pt1.pt2.pt3.pt4


java.rmi RemoteException: JMS Messaging problem with ServerRequestHandler for tcp://mycomputer1:2013/Func_VSE Could not connect to broker URL: tcp://mycomputer1:2013?wireFormat.maxInactivityDuration=0. Reason: java.net.UnknownHostException: mycomputer1; nested exception is:
               com.itko.jms.JMSException: Could not connect to broker URL: tcp://mycomputer1:2013?wireFormat.maxInactivityDuration=0. Reason: java.net.UnknownHostException: mycomputer1
               at com.itko.lisa.net.Transporter.init(Transporter.java:412)
               at com.itko.lisa.net.Transporter.<init>(Transporter.java:326)
               at com.itko.lisa.net.Transporter.createTransporter(Transporter.java:285)
               at com.itko.lisa.net.Transporter.getTransporter(Transporter.java:215)
               at com.itko.lisa.net.Transporter.transport(Transporter.java:161)
               at com.itko.lisa.net.Transactor.transact(Transactor.java:68)
               at com.itko.lisa.net.ClientBase.transact(ClientBase.java:359)
               at com.itko.lisa.net.ClientBase.invokeMethod(ClientBase.java:269)
               at com.itko.lisa.net.ClientBase.invokeMethod(ClientBase.java:242)
               at com.itko.lisa.net.VSEClient.getServiceNames(VSEClient.java:67)
               at com.itko.lisa.vse.ui.actions.DeployToVSEAction$1.doCallback(DeployToVSEAction.java:188)
               at com.itko.util.swing.panels.ProcessingDialog$2.run(ProcessingDialog.java:195)
               at java.lang.Thread.run(Thread.java:745)
Caused by: com.itko.jms.JMSException: Could not connect to broker URL: tcp://mycomputer1:2013?wireFormat.maxInactivityDuration=0. Reason: java.net.UnknownHostException: mycomputer1
               at com.itko.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)
               at com.itko.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:309)
               at com.itko.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:228)
               at com.itko.activemq.ActiveMQConnectionFactory.createQueueConnection(ActiveMQConnectionFactory.java:191)
               at com.itko.lisa.net.ActiveMQFactory.getRemoteQueueConnection(ActiveMQFactory.java:325)
               at com.itko.lisa.net.Transporter.getOrMakeConnection(Transporter.java:427)
               at com.itko.lisa.net.Transporter.init(Transporter.java:398)
               ... 12 more
Caused by: java.net.UnknownHostException: mycomputer1
               at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
               at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
               at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
               at java.net.Socket.connect(Socket.java:589)
               at com.itko.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:497)
               at com.itko.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:460)
               at com.itko.activemq.util.ServiceSupport.start(ServiceSupport.java:53)
               at com.itko.activemq.transport.InactivityMonitor.start(InactivityMonitor.java:127)
               at com.itko.activemq.transport.TransportFilter.start(TransportFilter.java:58)
               at com.itko.activemq.transport.WireFormatNegotiator.start(WireFormatNegotiator.java:72)
               at com.itko.activemq.transport.TransportFilter.start(TransportFilter.java:58)
               at com.itko.activemq.transport.TransportFilter.start(TransportFilter.java:58)
               at com.itko.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnect

Environment

* All supported DevTest releases
* 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.

Cause

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.

Resolution

Configure the VirtualServiceEnvironmentService to use the server fully qualified domain name and following the other steps should resolve the issue. Here are the steps to change the VirtualServiceEnvironmentService service name in the vmoptions file.

1. Added the below properties to the VirtualServiceEnvironmentService.vmoptions file on the functional VSE machine:
-Dlisa.registryName=tcp://mycomputer3.pt1.pt2.pt3.pt4:2010/Registry
-Dlisa.vseName=tcp://mycomputer1.pt1.pt2.pt3.pt4:2013/Func_VSE

2. Added this property to the VirtualServiceEnvironmentService.vmoptions file on the performance VSE machine:
-Dlisa.registryName=tcp://mycomputer3.pt1.pt2.pt3.pt4:2010/Registry
-Dlisa.vseName=tcp://mycomputer1.pt1.pt2.pt3.pt4:2013/Perf_VSE

3. Brought down Portal, Registry, Enterprise Dashboard and IAM services in this order.

4. Deleted folder DevTest_Home\lisatmp_10.x.x on this machine.

5. Noticed there was a DevTest_Homet\tmp.txt file but no DevTest_Home\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 DevTest_Home\lisatmp_10.x.x on both machines.

9. Was then able to deploy with no errors.

10. On the Coordinator machine add these properties to the CoordinatorService.vmoptions file:
-Dlisa.registryName=tcp://mycomputer3.pt1.pt2.pt3.pt4:2010/Registry
-Dlsa.lisa.coordName=//<fully qualified name of Coord machine>:2011/Coordinator

11. Restart Coordinator service.

12. On the Simulator machine add these properties to the SimulatorService.vmoptions file:
-Dlisa.registryName=tcp://mycomputer3.pt1.pt2.pt3.pt4:2010/Registry
-Dlsa.lisa.simulatorName=//<fully qualified name of Sim machine>:2014/Simulator

13. Restart Simulator service.