I was somewhat able to reproduce the problem. Spark is very extensible in nature. All kinds of plugins can add functionality. I’ve found that Spark would stop processing messages completely, if one of the ‘add-ons’ would throw an unexpected problem. I’ve addressed this issue here: https://issues.igniterealtime.org/browse/SPARK-1798 and provided a fix here: SPARK-1798: Gracefully handle exceptions from event listeners. by guusdk · Pull Request #215 · igniterealtime/Spark · Gi…
With the fix for this issue, the root cause of the problem won’t be fixed (I don’t know what it is), but the effect would now be isolated to that ‘add-on’. It would no longer prevent further processing of the message.
There’s a good chance that this will ‘fix’ your problem (not being able to see an incoming message). As a side-effect, the root cause should now be logged in the error logs of Spark. That will allow us to address that too.
I did a search and replace to replace the name of the server that Open Fire is installed on to OpenFireServer, but Domain is just how it is in the logs. We have only one domain and our openfire server shouldn’t be trying to contact another server or domain. I’ll have to look into that to figure out what is going on.
I’ve got the latest build installed now. Here are the raw packets received from a message that again didn’t show in my chat window, but did make my chat window pop up and flash. The second message that she sent me, that you see at the end, did appear in the chat window:
Bah, I had hoped that your problem would have been resolved with the new build. Apparently not.
This new build did improve logging. Does this version write anything related to this issue in the Spark log files?
One last thing that you could try is to start Spark from the command line / dosshell. There’s a chance that an error is printed to the console, instead of the error log. Perhaps that could give us a new insights.
I was hoping this would fix it too! But I suppose having the problem happen fairly consistently to me, and not very often to any of my users, is the best possible troubleshooting scenario.
Nothing relevant in the spark log files. I’ll give running spark from the command line a shot.
I’m running out of ideas, sadly. As long as there’s no way for me to reproduce this problem, it’s going to be hard to debug it.
You could try switching off plugins that you might have installed, toggle some settings, see if that makes a difference. Perhaps you’re lucky and find a cause that way. If your users don’t have this problem, then what’s different between your client and theirs?
No, I’d be surprised if it’s anything outside of Spark. Your client receives the message, it ‘simply’ does not display it. Spark has plugins of its own - I was referring to those.
Harhg. Would you be able to hook on a Java debugger and see what’s going on? I’m at a point where I don’t know what to recommend other than have an on-site Java developer debug your client…
Have you tried installing Spark on another computer, and log in with your credentials there - see if you can replicate it as consistently? Straws…
In any case, it’s around midnight here - I’m turning in. Hopefully, the morning comes with new insights…
Definitely go get some rest. I really appreciate all of your work on this. I’ll give running Spark on a different machine with my credentials a shot. If that doesn’t work, I’ll try some java debugging since I’ve done a little bit of java work myself. I’ll post back if I can figure anything out.
When wroot finds the time to merge my new changes at SPARK-1798: Handle exception thrown by eventhandler. by guusdk · Pull Request #217 · igniterealtime/Spark · GitHub and creates a new download, you’ll get a client that does a better job at logging errors. Perhaps that will tell us something.
So, Gretchen, you have to look in the logs for something relevant again with this build.
Btw, Guus, as Gretchen reported first, it started happening with 4.0.3. I have seen something similar just once and it was also after 4.0.3 upgrade. So this might still be related to some change in Openfire. It also happens with 2.7.7, so it wasn’t Smack 4 update.