![]() Disabling stream management works as expected.So, if Client A comes back online, it won't receive any messages that were sent to it when it disconnected. During this phase, any messages sent by Client B will be lost, meaning it's not stored in mod_offline which can be referred to as dead messages. Let's say Client A 's network suddenly goes offline, due to the timeout, Client A will still appear as online to the server until the timer runs out. ![]() This happens when a client suddenly disconnects.Īssume Client A and Client B are in a 1:1 conversation. PS:- Earlier I had referred issue #3086 and configured eJabberd with the recommended configuration for mod_stream_mgmt and mod_mam Reconnect the app to server - Only the message2 is received.Ĭan anyone help me with the message drop issue.Send message2 - this gets inserted to spool table.Wait of the user session to become offline.Check the user presence in server is online. ![]() I am able to consistently reproduce this issue using the following steps: I am stll relying on spool for offline message retrieval. Previously (in eJabberd 20.04), this issue was not observed. I have upgraded recently from ejabberd 21.12. Once the user presence is removed from server, the messages received thereafter starts geting saved to spool table in DB and the user gets those messages on reconnect. If the user session is resumed within this window of resume_timeout, all offline messages are received by the user. During this period, any messages sent to the user is never gets stored to spool table. When the mobile app client (SMACK 4.4.5) goes offline, the user session remains in the server for 5 mins (resume_timeout). Access_max_user_messages: max_user_offline_messages
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |