Is there a way to fix OMI slowness?

Hi Daniele,

Did you end up submitting a support ticket?  I would like to follow up, if there is an AVEVA support case.

Hi , yes i submitted a support tickert yesterday but I haven't got an answer yet

Hi Daniele, was your issue resolved? If so, can you comment what was the resolution?

Hi, we contacted the AVEVA support but without an official solution. However me and my team found out that the issue used to happen when the application was in "idle" for a while.So substantially after 5-10 minutes unused the issue happened. So we tried to put a simple  script on the layout that every minute triggers a boolean variable on the namespace "cache", just to keep the application always busy and never in idle.
This solution seems to work and for now I didn't experienced the issue again.

For everyone's information, it's most likely a firewall with a relatively short TCP idle timeout, which terminates inactive tcp sessions when there's no interaction with the supervisory client. You must either increase the timeout in the firewall or use some workaround to keep the session alive, like the one adopted above

For everyone's information, it's most likely a firewall with a relatively short TCP idle timeout, which terminates inactive tcp sessions when there's no interaction with the supervisory client. You must either increase the timeout in the firewall or use some workaround to keep the session alive, like the one adopted above