#436 "JID can not be null" after connection error

[A. Haferburg]

jabber.org just kicked me and I got disconnected in Saros.

ERROR 12:37:46,000 (Saros.java:1289) XMPP Connection Error:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)

Saros then tried to reconnect

DEBUG 12:37:46,187 (Saros.java:1253) New Connection State == CONNECTING
ERROR 12:37:52,812 (Saros.java:1255) New Connection State == ERROR
No response from the server.:
at org.jivesoftware.smack.SASLAuthentication.bindResourceAndEstablishSession(SASLAuthentication.java:452)

After clicking the reconnect button again I got an error message in a popup window.

DEBUG 12:38:06,062 (Saros.java:1253) New Connection State == CONNECTING
INFO 12:38:09,453 (Saros.java:1334) Reconnecting...(XXX/192.168.1.33)
DEBUG 12:38:09,453 (Saros.java:1253) New Connection State == CONNECTING
INFO 12:38:12,468 (Saros.java:798) Illegal argument: JID cannot be null
DEBUG 12:38:12,468 (Saros.java:1253) New Connection State == ERROR

Somehow the jid becomes null after a connection error.

[Stefan Rossbach]

4e210da629354999e687824f2fcd4fb048d19d58

Fixed JID = null for connection errors during an established

Added JavaDoc that the JID can still be null for connection
errors during the login process as the real JID is only known after
the login was successfully.