{{Quickfixn}} Exception in a QF/n thread causing the whole application to crash?

[Joseph Lam]

Hi

I just had my application using QuickFIX/n crashed with below exception:

20140303-15:15:02.073 : Session FIX.4.2:ORBIS->BKORBIS disconnecting: System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at QuickFix.SocketInitiatorThread.Send(String data)
   at QuickFix.Session.Send(String message)
   at QuickFix.Session.SendRaw(Message message, Int32 seqNum)
   at QuickFix.Session.GenerateTestRequest(String id)
   at QuickFix.Session.Next()
   at QuickFix.SocketInitiatorThread.Read()

It looks like it's the SocketInitiatorThraed automatically triggering a TestRequest itself during a time when the FIX connection was being brought up and down (by our own codes in a retry loop, due to the target comp rejecting our logon). And the exception in the thread seemed to have bubbled up to crash the whole application (a Windows service).

Is there any way I can prevent an exception in the QuickFix thread crashing the whole application?

Thanks.

Regards,
Joseph
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20140303/197ae2fb/attachment.htm>