Hi,
When client does some update like creating a view, changing carema in a view, the client failed to get notification from server about the change. When user re-login the client, we can see the change. The program registered the update event with the following API. _messageCommunication.RegisterCommunicationFilter(GroupViewUpdateHandler,
new CommunicationIdFilter(MessageId.SmartClient.ViewGroupModifiedIndication)); noticed the event notification
It seems to us that the event notification was delayed. Is there any workaround for this so that client can get update in time?
From our practice, the response is quick sometimes. However it’s slow in most case. And you have to re-login to get the change in some cases.
Perhaps it is not much of a surprise that I could not reproduce this in my small test setup. I did try, I tried just using the Message Tester tool plugin sample, in my test the message was always there and I did not observe any noticeable delay.
Have you seen this in multiple pcs? Have you seen this with multiple XProtect sites? Do you have one site (test or production) where this issue is now observed? Only one site?
What product and version is XProtect? What version is the Smart Client?
If you look at the load of the setup, is there any indication of overload? One example could be servers at 95-100% CPU usage.
Please describe the situation in further detail and let me get an idea what you are looking at..
Sorry for the late reply. We just used 1 - 3 clients on one site and every client pc can see the same issue. The version is xprotect corporate 2018R3. After re-starting the event server, everything was ok. Will let you know the detailed system overload when the issue happen again.