dovle01

Tuesday Tips: What to look for when your hostname is not resolving with DevTest components.

Discussion created by dovle01 Employee on Jun 9, 2015
Latest reply on Jun 29, 2016 by sdetweil2

To set the configuration - registry on server machine and remote VSE attempting to connect.  Firewall issues have all been taken care of - Ports 2010 and 2013 are open and by-directional.  When the VSE comes up, it stays up for a brief second and then shuts down.  A blip of traffic shows some communication.  The error log shows -

 

2015-06-08 19:32:55,781Z (14:32) [main] ERROR System.err - Cannot register with the DevTest Registry [JMS Messaging problem with ServerRequestHandler for tcp://<<MachineName>>:2013/VSE Could not connect to broker URL: tcp://<<MachineName>>:2013?wireFormat.maxInactivityDuration=0. Reason:java.net.UnknownHostException: <<MachineName>>; nested exception is:

 

com.itko.jms.JMSException: Could not connect to broker URL: tcp://<<MachineName>>:2013?wireFormat.maxInactivityDuration=0. Reason:java.net.UnknownHostException: <<MachineName>>]

 

2015-06-08 19:32:55,781Z (14:32) [main] ERROR System.err - java.rmi.RemoteException: JMS Messaging problem with ServerRequestHandler for tcp://<<MachineName>>:2013/VSE Could not connect to broker URL: tcp://<<MachineName>>:2013?wireFormat.maxInactivityDuration=0. Reason:java.net.UnknownHostException: <<MachineName>>; nested exception is:

 

com.itko.jms.JMSException: Could not connect to broker URL: tcp://<<MachineName>>:2013?wireFormat.maxInactivityDuration=0. Reason:java.net.UnknownHostException: <<MachineName>>

 

Looking into the log files, we see an unknown host name <<MachineName>>

Okay, now we know there is a problem resolving the machine name.

 

Ping the machine name – do you get IP information?  Yes

 

Do an ipconfig –all in a command window.

 

If you see 2 NIC cards, then it is apparent that JAVA is using the wrong NIC and we need to tell the LISA components to bind to the correct NIC using the following line in the local.properties

 

lisa.net.bindToAddress=<<CorrectIPForMachineName>>

 

Restart the components and all will come up and work if the issue was a binding issue.

Outcomes