Service Virtualization

Need help:

.DevTest Workstation through the ip address can be linked to the Registry service, but through the domain name suggested that the error "connection timeout"
..DevTest Workstation through the ip address can be connected to the Registry service, but also prompted the

following error:

log:

ERROR - Error collecting simulator info. JMS Messaging problem with ServerRequestHandler for tcp://dtserver:2014/Simulator Could not connect to broker URL: tcp://dtserver:2014?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection timed out: connect; nested exception is:
 com.itko.jms.JMSException: Could not connect to broker URL: tcp://dtserver:2014?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection timed out: connect
ERROR - Error Getting VSE Data
ERROR - Error Getting CS Data
ERROR - An error occured while trying refresh the Simulator panel for the test run. JMS Messaging problem with ServerRequestHandler for tcp://dtserver:2011/Coordinator Could not connect to broker URL: tcp://dtserver:2011?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection timed out: connect; nested exception is:
 com.itko.jms.JMSException: Could not connect to broker URL: tcp://dtserver:2011?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection timed out: connect
ERROR - Exception reading Simulators: java.rmi.RemoteException: JMS Messaging problem with ServerRequestHandler for tcp://dtserver:2014/Simulator Could not connect to broker URL: tcp://dtserver:2014?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection timed out: connect; nested exception is:
 com.itko.jms.JMSException: Could not connect to broker URL: tcp://dtserver:2014?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection timed out: connect
ERROR - Error Getting VSE Data

Please look at the  communities post below on 'Name Resolution'

Tech Tips: DevTest Environmental Restrictions 

I am not very understanding how to operate.

Name Resolution

DevTest requires that hostname resolution work correctly at all times, in both a forward and reverse direction – that is, resolving a name to an IP address must function correctly, and then resolving that IP address must yield the original host.

After reviewing the link shared by abrsh01, check with your engineering team and ask if your DNS provides shortname to fully qualified domain name (FQDN) mapping.  

Your Exception appears to indicate that shortnames are being used:

ERROR - Error collecting simulator info. JMS Messaging problem with ServerRequestHandler for tcp://dtserver:2014/Simulator Could not connect to broker URL: tcp://dtserver:2014?

I seem to recall a similar issue on LISA 7.5. If memory is correct, we added the lisa.net.bindToAddress=ip.Address.Of.Registry in the local.vse.properties and local.workstation.properties file. We used a JVM directive to point the servers to local.vse.properties and local.workstation.properties, respectively.  Not sure, but you might also get around this by adding a shortname to FQDN mapping in etc/hosts.

adding a shortname to FQDN mapping in etc/hosts,no work.

How to add information, I can not find these two files in the lisa installation directory:

local.vse.properties and local.workstation.properties file

local.vse.properties & local.workstation.properties are copies of local.properties (or _local.properties).

OOB both VSE & workstation use a common local.properties file. However, in a situation where both these components are started from the same installation & need a different set of values for the same keys, we create copies of local.properties & override default values for different keys as required.

The corresponding .vmoptions file need to have the -D directive for the components to pick up the respective property file

e.g. VirtualServiceEnvironment.vmoptions file under bin directory need to have

-DLISA_LOCAL_PROPERTIES=<path_to>\local.vse.properties

Similarly, Workstation.vmoptions file needs to have

-DLISA_LOCAL_PROPERTIES=<path_to>\local.workstation.properties

I assume dtserver is the Server where the Coordinator, Simulator & maybe the VSE is running. What is the IP corresponding to this server?

Please check if you can add the following line in the etc/hosts file of your workstation machine & try starting your workstation again.

<IP of dtserver>               dtserver

Dtserver corresponding to the ip is 10.252.45.183, workstaion with the server is not a LAN, workstaion and dtserver network has been put, workstaion can tcp: //10.252.45.183: 2010 / Registry (tcp: // dtsever: 2010 / Registry, Can not use the service, prompt timeout), you can use the service, but not using vse, and other components
Machine has set up the host file 10.252.45.183 dtserver,and restart workstaion,is no worker

##
# Host Database
#
# Localhost is used to configure the loopback interface
# When the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
:: 1 localhost
10.252.45.183 dtserver

On the machine where the Coordinator, Simulator and VSE are running:

Edit VirtualServiceEnironmentService.vmoptions file and add entry:
-Dlisa.vseName=tcp://10.252.45.183:2013/VSE

Edit SimulatorService.vmoptions file and add entry:
-Dlisa.simulatorName=tcp://10.252.45.183:2014/Simulator

Edit CoordinatorService.vmoptions file and add entry:
-Dlisa.coordName=tcp://10.252.45.183:2011/Coordinator

Restart Coordinator, Simulator and VSE services.

In the local.properties file of where the Workstation is running add these properties:

lisa.vseName=tcp://10.252.45.183:2013/VSE
lisa.simulatorName=tcp://10.252.45.183:2014/Simulator
lisa.coordName=tcp://10.252.45.183:2011/Coordinator

The Workstation will have to be restarted.

See if this works.

Jade,

Did Marcy's recommendations help you out with this issue?

yes