You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disclaimer: I'm a complete noob in XMPP. The behavior described here may be caused by some mistake in my ejabberd setup - I can't bring myself to set up a new ejabberd instance just to test it.
If last_item_cache is set to true, pubsub seem to use cached value for headlines, but does not update values in DB. Direct queries (as opposed to headline messages) return values from DB (that do not match headlines).
Environment
Configuration:
Errors from error.log/crash.log
No errors
Bug description
Disclaimer: I'm a complete noob in XMPP. The behavior described here may be caused by some mistake in my ejabberd setup - I can't bring myself to set up a new ejabberd instance just to test it.
If
last_item_cache
is set totrue
, pubsub seem to use cached value forheadline
s, but does not update values in DB. Direct queries (as opposed toheadline
messages) return values from DB (that do not matchheadline
s).The problem was initially discovered here.
Lengthy details
Value in DB (for the particular PEP node
select * from pubsub_item where nodeid = 12;
):current
[email protected]/laptop
001595:328942:525615
001595:329296:110683
<list xmlns='eu.siacs.conversations.axolotl'><device id='542020432'/><device id='820461778'/><device id='578605933'/></list>
get
request and observe the same result:headline
s:last_item_cache
tofalse
, start ejabberd.headline
:The DB value is updated too:
current
[email protected]/desktop
001595:328942:525615
001595:335002:831753
<list xmlns='eu.siacs.conversations.axolotl'> <device id='542020432'/> <device id='578605933'/> </list>
headline
:I also noticed that
pubsub_node_option.persist_items
in the DB is set tofalse
for the particular node, but I don't know whether it is relevant.Update: possibly was caused by the thing discussed here. I don't have time to retest at the moment.
The text was updated successfully, but these errors were encountered: