I am not familiar with this portion of the XMPP protocol, but this urn:ietf:params:xml:ns:xmpp-streamsStream Error occurred for me recently, which correctly caused xmpp-client to SIGTERM and disconnect from the server immediately (XMPP Stream Errors are unrecoverable). If parsing the XML to see if there is an error message is considered acceptable, it might be a bit more informative to the user to know more about what went wrong, rather than what I saw:
* (8:25PM) {http://etherx.jabber.org/streams error} &{{http://etherx.jabber.org/streams error} {urn:ietf:params:xml:ns:xmpp-streams system-shutdown} Received SIGTERM}
* (8:25PM) EOF
* (8:25PM) Exiting because channel to server closed
This was from a build of 4f8a025e481ee8776a19e37425615bebffa1af3f.
I am not familiar with this portion of the XMPP protocol, but this
urn:ietf:params:xml:ns:xmpp-streams
Stream Error occurred for me recently, which correctly caused xmpp-client to SIGTERM and disconnect from the server immediately (XMPP Stream Errors are unrecoverable). If parsing the XML to see if there is an error message is considered acceptable, it might be a bit more informative to the user to know more about what went wrong, rather than what I saw:This was from a build of
4f8a025e481ee8776a19e37425615bebffa1af3f
.