Hi team.
Hope you're all doing fine.
Is there any update regarding SAME-38796 ?
Is there any workaround for newer versions of Chrome & Chromium-based than V90 specified in the following KB:
https://support.hcl-software.com/csm/en?id=kb_article&sysparm_article=KB0088900 ?
None of the flags suggested in the article are available in V98 of Chrome / Chromium-based browsers.
Thank you very much in advance.
Sincerely,
Elvis.
Thank you for reporting this. If you are experiencing this issue, open a support case with HCL to review options since the intensive-wake-up-throttling flag has been removed.
Hi Trevor.
Thanks for your response.
As a matter of fact, I created a support case too.
Flags are indeed missing.
Developers say it is not a Server-side issue (which is correct), but there is no workaround yet; they suggest to work with a Full client (Notes-embedded, ST Standalone) for this.
They have reports that on Firefox, the issue is the same, So, it is not tied to Chromium-based browsers, but they don't either have a workaround for this browser.
We're testing with Opera.
Another suggestion was use Chromium-based Browser App (PWA) client, but again, it will simply create and have a direct connection to ST Server and iNotes/Verse would indeed logout.
Seems a not handy/easy going workaround for end-users.
I actually noticed that from Connections it also logs out.
If I have found any additional info and/or feedback from Dev, I'll post back here.
Sincerely,
Elvis.
Hi. Just to post latest feedback from DEV:
I just received an update from dev team , that this SAME-38796 is deferred due to this is an Browser issue and not an server side or client side issue, the Chrome based browsers are designed to work like this, closing the connection, that is an Chrome designed thing, that´s why they removed the flags from chrome 9, as the webclient developer did the change, the webclients are affected too,
our development team tested the issue using ST App and ST Client and the session did not close their , this states that our server didn't have this timeout setting in our code, and unfortunately as chrome developers removed the flags , we didn't have other workaround than using our official Sametime Clients, in mobile and OS's and not the webclient via browser
Hi team.
Just to post an update here:
I requested an update directly on the following KB:
Sametime in iNotes and Verse disconnecting due to timeout inactivity (hcltechsw.com)
And they added the following three updates:
Applies to
Sametime Proxy 11.5IF1, 11.6
As a matter of fact, this last workaround described in item 3 resulted good.
Hope this helps anybody else.
Sincerely,
Elvis.