Embedded Daemon many repeatingConnection to null broken messages
#225
Comments
|
Hmm... The message is logged when a pair of message and connection from the output-queue ( It looks like it is possible that a connection might be re-added to |
|
Great, thanks a lot. I'll get a new build of our app to this user and tell him to keep an eye for the same thing. As far as I know, this version of the app has been in use for a good week or so, so it may be a little while before I hear about this again. |
|
Sadly, we have had a couple of reports of this still happening. It does appear though that the additional debugging you added is now visible. As before, this output continues until the JVM is killed. |
…g of messages already queued for broken connections; Improved logging (again)
|
That's too bad. I updated the code of DBusDaemon again. This change addresses the handling of messages in Is it possible that you increase the log level to |
|
I have not personally been able to reproduce, but my colleague @ludup who is having this problem seems to get it pretty regularly just by using the app day to day. This is internal testing of the next version we had hoped to release (a VPN client, not that it matters). The things we do know ..
Anyway, thanks for the changes. I'll get another build done and we can see how this one goes. I'll also ask for log level to be increased. Edit: I've just realised the version we were using previously was 4.2.1. So it's possible that the issue started in 4.3.0 (which we have never used here). I notice there are some others changes to the embedded daemon in that. |
|
Sorry it's been a while, but this does seem to have gone away now. It looks like your last changes did the trick, At least it has not been reported. Closing, will re-open if more it turns up again. |
Have had a report our of app failing with this error in the logs. Something happens, then the embedded daemon gets into some kind of bad state and will repeat this error over and over (probably infinitely, and probably sending one core to 100% usage).
I suspect that the users laptop, is going into and coming out of a sleep mode quite often. I have don't have full logs for this, just the
WARNthats coming fromDBusDaemonSenderThread(the initial output is from our app)This then repeats over and over, with some log output from our app interspersed. Any thoughts on what might cause this?
Edit: should have said this is with 4.3.1-SNAPSHOT.
The text was updated successfully, but these errors were encountered: