#31 CPU 100% when MSN failed to signed but others succeed

[Anonymous]

The easiest way to reproduce.

1. use the TestClient. Remove ca-list.dat from
hamsam/util/net/ssl/, which will cause MSN fail to sign in.
(I found this bug accidentally by not having this file in
correct path).

2. Create MSNProtocol, Yahoo Protocol, AIM Protocol.
and use proper users/passwords to connect.

3. You will see exceptions because of the missing file.

4. Wait for a while, use Windows monitor to check the
CPU usage. The CPU usage for is 100% persistently.

[Nobody/Anonymous]

Logged In: NO

more experients indicate that when one of the Protocol failed
to sign in(e.g. incorrect password/user pair). the CPU would
reach 100% from there.

Anoth bug related is that when you submit a wrong password
for MSN, there is a NULL pointer exception in msn/util.