#859 [mod_mam_muc] Only last 20 messages are fetched
Reporter
thededem
Owner
Zash
Created
Updated
Stars
★ (1)
Tags
Priority-Medium
Type-Defect
Status-Invalid
thededem
on
What steps will reproduce the problem?
1. Create a MUC with two participants.
2. Post more than 20 messages with one participant, while the other participant is offline.
3. Connect the offline participant to the server and the MUC.
Expected output: See all the messages posted, while the participant was offline.
Real output: Only the last 20 messages are fetched/displayed.
What version of the product are you using? On what operating system?
0.10 (commit 7239:703f7f45feb4) on CentOS 6.8 with community-modules commit 2625:8c6562f16496
I use sql storage with a PostgreSQL database.
I have tested the scenario with Gajim and Conversations.
In normal (one on one) chats, the problem does not occur. There all messages are delivered as expected.
Since the default value for max_archive_query_results is 20, I thought, that this might explain the number of retrieved messages. However, changing max_archive_query_results to a different value does not change the behaviour.
Zash
on
Hi. Please also include what versions of the clients are used, and preferably also which version of the MAM protocol they implement.
Some debug logs would also be helpful in order to diagnose the issue.
Changes
owner Zash
tags Status-NeedInfo
thededem
on
Hi, I'm sorry, I just realised that gajim does not support mam in mucs yet, after opening the ticket. With conversations however, the problem disappeared, now that I have updated prosody to the latest commit in the 0.10 branch and latest community modules.
So, the ticket can be closed.
What steps will reproduce the problem? 1. Create a MUC with two participants. 2. Post more than 20 messages with one participant, while the other participant is offline. 3. Connect the offline participant to the server and the MUC. Expected output: See all the messages posted, while the participant was offline. Real output: Only the last 20 messages are fetched/displayed. What version of the product are you using? On what operating system? 0.10 (commit 7239:703f7f45feb4) on CentOS 6.8 with community-modules commit 2625:8c6562f16496 I use sql storage with a PostgreSQL database. I have tested the scenario with Gajim and Conversations. In normal (one on one) chats, the problem does not occur. There all messages are delivered as expected. Since the default value for max_archive_query_results is 20, I thought, that this might explain the number of retrieved messages. However, changing max_archive_query_results to a different value does not change the behaviour.
Hi. Please also include what versions of the clients are used, and preferably also which version of the MAM protocol they implement. Some debug logs would also be helpful in order to diagnose the issue.
ChangesHi, I'm sorry, I just realised that gajim does not support mam in mucs yet, after opening the ticket. With conversations however, the problem disappeared, now that I have updated prosody to the latest commit in the 0.10 branch and latest community modules. So, the ticket can be closed.
Thanks.
Changes