Exception on reconnect ( autoroster )

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Include an idletime instance, configured for a 10 second timeout
2. Handle the idle and unidle events, sending presence for each
3. Rinse and repeat until server disconnections occur ( no server 
disconnections experienced prior to adding the idletimer - once added 
server disconnections become commonplace )
4. Handle the OnDisconnect event
4.a. Issue a connection request on handling the OnDisconnect event
5. The Jabber client throws an exception stating that the client must be 
authenticated before getting the roster
5.a. Appears the client does not check the authenticated state, if 
previously authenticated perhaps, before auto-requesting the roster

What is the expected output? What do you see instead?
Expected output is the client authenticating on the reconnect, before 
attmepting to receive the roster.
See instead is the client throwing an exception

What version of the product are you using? On what operating system?
Latest, 2k8 server, .net latest

Please provide any additional information below.

Original issue reported on code.google.com by rnend...@gmail.com on 18 Sep 2009 at 3:56

[GoogleCodeExporter]

Regarding the mysterious appearance of server disconnects after adding the 
idletimer - the idle is set at 10 seconds with the keepalive at 30, this "may" 
be 
the reason for the appearance of the consistent disconnect issue.

Original comment by rnend...@gmail.com on 18 Sep 2009 at 3:59

[GoogleCodeExporter]

More information.  The disconnects do not start occurring with the addition of 
an 
idle timer.  The disconnects occur when.
1. Login using an invalid account ( unknown to the server )
2. This results in an authentication failure
3. Login using a good account, using the same instance of the jabber client
4. Just wait for 10-60 seconds, server disconnect occurs
5. On reconnect attempt, a client exception occurs ( in the jabber code ) when 
either the client attempts to get the roster ( if autoroster is enabled ), or 
results in a null exception if autoroster is set to false - note that the null 
exception occurs when the client is attmepting to receive a roster ( even 
though the 
autoroster property is false )

Original comment by rnend...@gmail.com on 18 Sep 2009 at 4:18