Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recent MUC messages missing in archive result #38

guusdk opened this issue May 31, 2019 · 1 comment


None yet
1 participant
Copy link

commented May 31, 2019

The response to a (MAM) query for a chatroom should, but does not always, include all messages that were exchanged in the MUC at the time that the query was issued.

The MUC persistence manager writes message archives periodically (in batches), while the MAM implementation expects all archived messages to be in the database immediately. This can lead to situations where "the last few" messages in a MUC are not included in the response for a message archive.

This issue is closely related to, which resolved a similar issue. In OF-1200, the mechanism in which the Monitoring plugin writes data to the database was changed. When the Monitoring plugin is constructing a MAM response, it uses data written to the database by itself, but also by the MUC persistence manager. The latter was unaffected by OF-1200 (which likely was an oversight at the the time).


This comment has been minimized.

Copy link
Member Author

commented May 31, 2019 should make available a mechanism in Openfire that can be used by the Monitoring plugin, to fix this issue.

guusdk added a commit to guusdk/openfire-monitoring-plugin that referenced this issue May 31, 2019

guusdk added a commit that referenced this issue Jun 3, 2019

38: MUC messages should be accessible through MAM immediately.
This addesses #38, and builds on OF-1200 / OF-1788.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.