Hello Anton,
Thanks for your response and hints about further debugging. Here are my quick feed backs -
1) Yes, you can set Transparency to False, if you catch the exceptions everywhere you use the DeviceProxy.
=> I am catching and exception carefully, hence I will prefer to set the Transparency to ‘False’, as it can avoid client application hang.
(3) That issue only applies to cppTango (and PyTango, which uses it). It would not affect JTango.
=> In the log JTango is showing two events one is stamped with device-server IP and other without it. In the report , I gave the log
I see the code uses setDev_timeout and set_timeout_millis. I don’t know what setDev_timeout is for.
=> setDev_timeout is for dserver device ( admin-device), the purpose of setting this as well so that KeepAliveThread and other Java thread which connects DServer shall not take default timeout of 3 seconds, instead it shall take the set timeout for e.g. 5 Milli-seconds
It you use ATK Panel to monitor your device, does it have similar behaviour? E.g., very long “hanging” (5 to 10 minutes), updates only after 6 seconds when device restarted, etc.?
=> Yes, ATK Panel / Jive show that the application do hang for 5 to 6 minutes as mentioned in the test-report.
Jitendra