Re: [Quickfix-developers] SocketInitiator.stop() Problem

[Tom W <twi...@mq...>]

Anyone ............... ?????




Tom W wrote:
> 
> I have been trying to find a solution to this problem, without success. 
> I've seen several other posts around the internet (mostly from a few years
> ago) but have yet to find a tangible solution.
> 
> I am finished with my current FIX session, so I send a logout message (5)
> to the FIX server and the logout completes fine.  I then want to
> stop/close my SocketInitiator and reset it so it can be reused for the
> next session.  This is the code I have :
> 
> public void onLogout(SessionID sessionID)
> {
>      if (this._socketInitiator != null)
>      {
>           this._socketInitiator.stop(true); // HANGS HERE
>      }
> }
> 
> When I then try to start another session using the same SocketInitiator, I
> get the exception :
> 
> "Configuration failed: Could not open body file:
> Logs\\FIX.4.2-ABC-DEF.body"
> 
> when I try to run this line of code :
> 
> this._socketInitiator = new SocketInitiator(this, this._storeFactory,
> this._settings, this._logFactory, this._msgFactory);
> 
> It seems as if the SocketInitiator has not released all its resources
> fully, and the .body file is indeed locked when I try to open it in, say,
> Notepad.  I have seen suggestions to using CVS (I'm not sure exactly what
> this is or how to go about doing this) but surely there is a simpler
> solution to what must be a fairly common action?  I am using FIX 4.2 and
> the latest version of QuickFIX from www.quickfixengine.org.
> 
> Any solutions gratefully received!
> 
> Tom
> 

-- 
View this message in context: http://www.nabble.com/SocketInitiator.stop%28%29-Problem-tp18473551p18754916.html
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.