Re: [Quickfixj-users] Initiator.stop leaves file handles open whenusing FileStore

[Steve B. <st...@te...>]

As you've seen, the FileStore is not designed to be used this way. One
way to support your usage pattern is to modify the FileStoreFactory
to keep a reference to FileStores that it has created. You could then add
a close() method to the factory that would close all the FileStores.

> Robert McConnell wrote:
> We are finding that our application is running out of file handles. The 
> problem occurs because our auto recovery code having detected an acceptor 
> initiated logout, attempts to re-start the connection by constructing a 
> new SocketIinitiator (having stopped the old one first) and then calling 
> start on it.
>
> The problem seems to be that the FileStore maintained by the Session
object 
> does not close its file handles (except when a reset is done at which
point 
> it promptly opens the files > again). The Socket initiator creates a new 
> Session object and so we find that with each disconnect we are using up 
> more file handles. The problem also seems to occur with the event and 
> message logs.
>
> Has anyone had to handle this situation before and found a way around it?