Simulator Service is getting shutdown after few mins

Products

• CA Application Test
• Service Virtualization

Issue/Introduction

Trying to add a more Simulators (as a service) on a second server to connect to the remote registry, the Simulator is getting shut down after a few minutes and seeing the below errors. 

INFO  com.itko.lisa.coordinator.SimulatorServerImpl - Lost connection to DevTest Registry, retrying
java.rmi.RemoteException: JMS Messaging problem with ServerRequestHandler for tcp://HOST002:10142/Simulator1 Could not connect to broker URL: tcp://HOST002:10142?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://HOST002:10142?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection timed out: connect
    at com.itko.lisa.net.Transporter.init(Transporter.java:412)
    at com.itko.lisa.net.Transporter.<init>(Transporter.java:326)

[ServerRequestHandler-1] ERROR com.itko.lisa.net.ServerRequestHandler - Could not fetch a message from QUEUE: peer (vm://lisa1#1) stopped.
com.itko.jms.JMSException: peer (vm://lisa1#1) stopped.
    at com.itko.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:72)
    at com.itko.activemq.ActiveMQMessageConsumer.dequeue(ActiveMQMessageConsumer.java:505)
    at com.itko.activemq.ActiveMQMessageConsumer.receive(ActiveMQMessageConsumer.java:583)
    at com.itko.lisa.net.RemoteRequestHandler.run(RemoteRequestHandler.java:313)
    at java.lang.Thread.run(Thread.java:748)
Caused by: com.itko.activemq.transport.TransportDisposedIOException: peer (vm://lisa1#1) stopped.
    at com.itko.activemq.transport.vm.VMTransport.stop(VMTransport.java:233)
    at com.itko.activemq.transport.TransportFilter.stop(TransportFilter.java:72)
    at com.itko.activemq.transport.TransportFilter.stop(TransportFilter.java:72)

Able to start Simulator as a server component but not as a service.

Environment

Release : 10.7

Cause

Looks like firewall on the second server causing the issue.

Resolution

Adding the Inbound and Outbound rules in Firewall for SimulatorService as in below screenshot should resolve the issue. 

 

Additional Information

Creating and Configuring Multiple Simulators on the Same Machine for Windows,  see the knowledge article https://knowledge.broadcom.com/external/article?articleId=234858