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
I noticed this when a server I use rebooted for an upgrade, and left my QXMPP-based bot in reconnection limbo.
I can reproduce it easily. If I set my bot to connect to, for instance, my router's IP, so the connection will be refused, QXMPP's logging shows this:
Tue Nov 27 22:55:33 2018 INFO Connecting to 192.168.1.1:5222
Tue Nov 27 22:55:33 2018 WARNING Socket error: Connection refused
and then nothing else for, at least, one full hour.
The error() signal from the QXmppClient object is never emitted. I understand maybe those signals only refer to errors when the session has been actually started, but then, how can we (sanely) handle this kind of thing?
This happens both with autoreconnection enabled and disabled.
#98 and #119 seem to be related. I have QXMPP 0.9.3 via Mageia packages.
The text was updated successfully, but these errors were encountered:
I noticed this when a server I use rebooted for an upgrade, and left my QXMPP-based bot in reconnection limbo.
I can reproduce it easily. If I set my bot to connect to, for instance, my router's IP, so the connection will be refused, QXMPP's logging shows this:
and then nothing else for, at least, one full hour.
The error() signal from the QXmppClient object is never emitted. I understand maybe those signals only refer to errors when the session has been actually started, but then, how can we (sanely) handle this kind of thing?
This happens both with autoreconnection enabled and disabled.
#98 and #119 seem to be related. I have QXMPP 0.9.3 via Mageia packages.
The text was updated successfully, but these errors were encountered: