{{Quickfixn}} Bringing down a connection

[Mike Gatny]

If you call Initiator.Stop(), all Sessions on that Initiator will log out
and disconnect until you call Initiator.Start().  In between the Stop and
Start calls, you could probably get away with modifying the SessionSettings
that the Initiator has a reference too.  If that doesn't work, you could
create a new SessionSettings (e.g. after modifying the cfg file), and then
create a new Initiator with those SessionSettings and call Start on that.

I think there have been bugs around resources getting properly released
when calling Initiator.Stop()... you might want to check the latest release
notes (or maybe someone on the list will chime in with details).

--
Mike Gatny
Connamara Systems, LLC


On Mon, Mar 31, 2014 at 8:58 AM, Campbell Wild
<campbellwild at thinkfolio.com>wrote:

>  Is there a "proper" way to bring down a single connection between the
> Start and End (i.e. "Up") time of a connection?  If I have an engine that
> has several routes, but want to bring a single one down for some reason,
> can I do this without affecting the other routes.  Ideally, I would also
> like to be able to make changes to the config (e.g. change start/end times)
> before bringing it up, but I don't know if that's a step too far.
>
>
>
> My thought was to explicitly send a LogOut message, then force a
> disconnect every time the session reconnects, but it seems a bit of a fudge.
>
>
>
> Thanks
>
> Campbell
>
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20140331/375d26da/attachment-0002.htm>