Unable to connect DevTest Worksation 10.3 getting timed out error

[Mohammed Sheeraz]

Hi,

We have provided access to few users for DevTest workstation 10.3, They were able to login successfully for 2 days all of sudden they all are getting the below error and couldn't connect to registry.

Could anyone please help on this

Error connecting to the Dev Test Registry.Error message: Timed out trying to test registry            tcp://hostname: 2010/Registry

 

Stack Trace::

    java.rmi.RemoteException: Timed out trying to connect to test registry tcp://hostname:2010/Registry
    at com.itko.lisa.test.Environment.bootUpTestRegistry(Environment.java:2595)
    at com.itko.lisa.test.Environment.setTestRegistry(Environment.java:2574)
    at com.itko.lisa.gui.TestAdmin.startRegistry(TestAdmin.java:577)
    at com.itko.lisa.gui.TestAdmin.access$000(TestAdmin.java:83)
    at com.itko.lisa.gui.TestAdmin$1.doCallback(TestAdmin.java:228)
    at com.itko.util.swing.panels.ProcessingDialog$2.run(ProcessingDialog.java:194)
    at java.lang.Thread.run(Thread.java:745)

Thanks,
Mohammed Sheeraz

[Koustubh Warty]

Please confirm the following - 

- both Registry and workstations are on the same version of 10.3
- your logs show Registry has hostname running on port 2010. Hoping that you have modified the log before posting and that Registry is indeed pointing to the correct hostname.
- your Registry service or process is up and running and that you are able to also bring up the Portal and then the portal url comes up successfully?
- is this for all workstation users or only a few users?
- where is the registry located as compared to the workstation users?

thanks!



------------------------------
Head of Product Management: Service Virtualization
CA Technologies - A Broadcom Company
------------------------------

[Mohammed Sheeraz]

Hello,

Please find my answers inline.

- both Registry and workstations are on the same version of 10.3 - Yes
- your logs show Registry has hostname running on port 2010. Hoping that you have modified the log before posting and that Registry is indeed pointing to the correct hostname.- Yes, we are using hostname in the registry and tried using host IP too but didn't help.
- your Registry service or process is up and running and that you are able to also bring up the Portal and then the portal url comes up successfully? - Yes, Registry service is up and running and the issue only for few users whom i have granted access recently and for rest it works including me.
- is this for all workstation users or only a few users? - Only for few users ( Initially they were able to connect to registry for 2-3 days after granted access, all of sudden they are facing issue and no other changes done.)
- where is the registry located as compared to the workstation users? -( registry is hosted in the AWS standalone server and users are trying to connect from their VSI's or workstations)

Thanks,
Mohammed Sheeraz

[Koustubh Warty]

ahh - so you are using it in an hybrid env. Server components in cloud and Workstation on-prem. This is surely latency and timing issue between those users workstations and the Registry component. Please check on that.

------------------------------
Head of Product Management: Service Virtualization
CA Technologies - A Broadcom Company
------------------------------