Was SAME-38312 really fixed in Sametime 12?

HCL Sametime Sametime Forum
,
1

Hi.

A customer has reported to experience what is described here:

Sametime Meeting Server requires restart after losing connectivity to MongoDB

https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0094200

The article is related to versions 11.x, stating that in 12.x the issue is solved, but the problem is that customer's deployment is 12.0.1FP1 (soon to be upgraded to the latest).

It also mentions the issue as being coded SAME-38312, but, as far as I have been able to search, I haven't found it in any Sametime 12.x fix list.

Was the issue really fixed in Sametime 12.x?

Thank you very much and best regards.

2

We've taken a number of steps to recover when mongodb become unavailable and believe we have them all resolved.

If you're currently having an issue with mongodb recovery, please open a case so that we can review and discuss the specifics of your scenario.

3

Thanks a lot for the quick confirmation.

As we are going to upgrade customer's deployment soon, we'll retest after it and confirm if the issue is still happening.

Thanks again.