Instant Messaging 10 Users Show Chat Messages As "delayed" To Users Not On The Same Backend In Server Pool
(Doc ID 2222802.1)
Last updated on MARCH 15, 2019
Applies to:Oracle Communications Instant Messaging Server - Version 10.0.0 and later
Information in this document applies to any platform.
Instant Messaging (IM) configured in multi-node front end (FE) and back end (BE) server pool.
Adium(IM client) users connected to back ends see group chat message from any user connected to a different back end as if the IM10 user is "offline".
The user's presence is synchronizing properly. We see each other as "online" or "offline" properly. Everyone's roster shows the correct status.
But Adium has this behavior that when you come into a chat and it shows history, it displays those messages slightly grey and blurred. Normally that is all history before any new messages. But what is happening here is that new current chat messages from the user on a different back end is appearing as this same "offline" or "delayed" slightly grey and blurred history mode.
Users who happen to be connected to the same backend (which currently also means they must be connected to the same front end) do not get the "offline" thing and therefore appear current/online/normal.
Messages from users who happen to be on a different back end from other users have the "delayed" thing and appear to be delayed/offline.
Messages are still delivered. The difference is only visible to Adium users.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document