I agree, it’s a strange thing to log on ‘warning’ level. Was Jennifer also the person that sent you the message that didn’t show at the time?
I looked before for the source of this log message, which I could not find. That means that either I’m not looking hard enough (entirely possible), or that you are running some old bits of code. The only way that I see that happening is if there are some plugins left, that don’t get updated.
Next to the logs folder, there should be a plugins folder. Could you clear it (create backups first) please? Restart Spark afterwards, to see if the problem disappears. When it does, try to restore the .jar files in the plugin directory one by one, restarting each time, to find out which plugin is causing the issue. You only need to restore the .jar files, not the subdirectories, as those will be created automatically.
I have analyzed the code and code history in all ways that I know how. I cannot find any reference in our code that would lead to a log statement like this:
WARNING: chatRoomOpened: jennifer@OpenFireServer
I did, however, found third-party code that creates this statement, here: MUCFileUpload/MUCFileUpload.java at develop · Speedy-Gonzalez/MUCFileUpload · GitHub
This matches the log statements exactly: up to the two spaces that are used between “chatRoomOpened:” and the JID.
Have you every played around with MUC file upload stuff?
No I’ve never used the MUC file uploader. I don’t use any Spark plugins other than what installs with the spark installer so I’m not sure where that would come from.
@Gretchen Raff would you mind popping into our chatroom? The Group Chat link on top of this page will get you to a web-based client, using Spark, you can add the conference server “conference.igniterealtime.org” and join the room named “open_chat” there.
So far so good. Since I deleted my old Spark AppData folder (Roaming), I’ve received every message sent to me. Guus, I’m in the group chat room if you’re available.
As often goes with Spark, some things are left in the profile and mess things. So, we have a workaround. It would be great to find the root cause of this, but i don’t believe we will (after so lengthy investigation already) and new users shouldn’t encounter this, i hope. Going to close the ticket now.
Sure, no problem. I renamed my transcript folder and checked “disable chat history” under general chat settings in preferences. I’ll let you know how it goes today.