This is for OBM 2020.10 on RHEL7 with remote Oracle DB, HA with 2 DPs and 4 GWs. Patches up to early January, with patches from 1/15 and 1/22 pending in our dev environment so will soon be up on this environment. The production environment is eyes-on-glass 24x7 with multiple users handling events.
Since moving from the Flash event browser to HTML5 the users have reported slow refresh on new events. They have a 3-pane event browser, unwired, each with their own filter. New unassigned for this group events show in the top pane. A user takes ownership, so the event then appears in the 2nd pane (assigned to users in this group). The 3rd pane is for events assigned to other groups from this group in the last 24 hours.
The users typically set the first pane to trigger the sound on new event. In some cases a user will hear the ding but see no event. If they refresh the pane or the entire window they then see the event. The Event counter may or may not reflect the unseen event, but that may be unreliable as there is a 1/22 hotfix soon to be installed addressing the event counter updates.
Some users do not get a ding or see an event, but the counter on "Assigned to group" shows a number, so they refresh and _then_ see the event.
Server logs do not indicate any particular errors. We have a forwarder sending events to Splunk and it is updated with new/changed events as they arrive, so it's not the event pipeline being stopped up.
I personally get the sense that the browser is just slower to refresh. "Not showing" for the users is anything more than several seconds, but one user might see the event several more seconds before other users. It boils down to a new event is not pushed to the user's event browser, but that the event browser appears to poll periodically, and perhaps that poll might be slow if the user's system is lagging for any reason. I have not confirmed this, but it feels to me like the HTML5 browser is less proactive than the old Flash browser.
I am trying now to confirm if that is truly the case. I have the static Flash-enabled Firefox browser built and will try to compare the concurrency of the HTML5 vs Flash event browsers. Luckily, the HTML5 event browser these users rely on was copied from a matching Flash event browser. I feel like the slowness is in all HTML5 event browsers, but their particular page if most import right now.
I am going to throw all of this into a support case as well. Wondering here if others have noticed this effect.