FIXEngine can take over sessions even when using SOLE_LIBRARY mode or using SessionProxy about artio

[pcdv]

Reading #361 (Don't revert ownership of offline sessions to the Engine in Sole Library mode) seems to indicate that this is a bug.

[haoyang1994]

I have the same confusion. The existing tcp connection will not be released when the sole library is disconnected, but will be taken over by the Gateway Library. As a result, SessionProxy cannot track all outbound messages. I'm wondering whether to put Engine and Library in the same process and release the engine's tcp connection in the library disconnect callback.

[pcdv]

FYI this is what I do: several processes embed their own engine + library, even though that is not the original philosophy behind artio (and is heavier in terms of processing).

Nevertheless, disconnections between engine and library due to timeout can still happen. I've seen it in two scenarios:

• invalid shutdown implementation on my side: the library would time out while the engine was closing (hopefully fixed now)
• attaching a debugger to the process

I'm wondering whether I should take care of closing all sessions from the library before shutting down the engine, to avoid the risk of having sending uncontrolled outbound messages because of this issue.