Hi,
We sometimes have a problem where the ssl stream seems to try and write
packets even though the client should have been cleaned up.
Any one else seen this happen?

We do seem to always get a StreamError first.
Do we need to manually reconnect or close the client when this happens?

OnError : jabber.client.JabberClient System.IO.IOException: Unable to write
data to the transport connection: An established connection was aborted by
the software in your host machine. ---> System.Net.Sockets.SocketException:
An established connection was aborted by the software in your host machine
   at System.Net.Sockets.Socket.BeginSend(Byte[] buffer, Int32 offset,
Int32 size, SocketFlags socketFlags, AsyncCallback callback, Object state)
   at System.Net.Sockets.NetworkStream.BeginWrite(Byte[] buffer, Int32
offset, Int32 size, AsyncCallback callback, Object state)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.BeginWrite(Byte[] buffer, Int32
offset, Int32 size, AsyncCallback callback, Object state)
   at System.Net.Security._SslStream.StartWriting(Byte[] buffer, Int32
offset, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security._SslStream.ProcessWrite(Byte[] buffer, Int32
offset, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security._SslStream.BeginWrite(Byte[] buffer, Int32
offset, Int32 count, AsyncCallback asyncCallback, Object asyncState)
   at System.Net.Security.SslStream.BeginWrite(Byte[] buffer, Int32 offset,
Int32 count, AsyncCallback asyncCallback, Object asyncState)
   at bedrock.net.AsyncSocket.Write(Byte[] buf, Int32 offset, Int32 len)

So nobody has seen this error before?
Then i must be doing something wrong!

I too have been receiving this error, but have not had a chance to look into a solution. Would be nice to have one ;)

Keith