By abbreviation “OPF”, I meant Openfire, similarly, “HTH” meant “Hope That Helps”.
- In some experiments that I did, I see that messages are persisting. This is after I disconnect my clients, re-boot my server etc. This suggests that these messages are being persisted someplace. I could not find them being stored in the DB nor filesystem nor on the client-side. Hence this mystery.
Out of the box, the Monitoring Service*1 plugin does not install, so you would never see this happening by your current methods. However, multi-user chat can be logged (see tables ofMucConversationLog). After the initial install is established, you would need to enter the Openfire Admin Console, typically running on “http://localhost:9090/”, and login with credentials you specified during initial install.
Through plugins, the OPF server’s capabilities are extended, and is perhaps one of the (many) good design qualities of the server itself. It appears you have gotten to the Admin console already, so from there go to “Plugins” tab, and install the Monitoring plugin. Once that is done, you can set how you want conversations archived. Chat conversations ***will be logged to the database (*see tables OfConversationLog, IIRC) after a “flush” timer (also an option for specification).
- I realise from the spec (rfc3290) that after a tcp-session is establised between the clients an “xml-stream” goes back and forth. Further this is perhaps encoded in some form. (base64 ?). So, a human eye may not pick these up and we may need to use some decoding tool on the stream. But this is besides the point. The big mystery to me is where are these messages stored such that they re-appear after re-starting clients & servers.
The format is ASCII text, seen by command, tcpdump -X -s 0 port 5222, unless encrypted, which would appear as a mix of hex characters.