{{Quickfixn}} how to clear Session.sessions_ ?

[Grant Birchmeier]

You may be right.  I doubt that this would take up enough memory to cause a
real issue, but technically I think you are correct.


On Sun, Feb 23, 2014 at 10:41 PM, Joseph Lam <joseph.lam at orbis.com> wrote:

>  Hi
>
>
>
> In my own unit tests, the Session.Lookup() would return sessions that were
> constructed programmatically from earlier tests in the same run, causing
> interference. Looking at the source code I can't seem to find where/how the
> underlying Session.sessions_ dictionary gets cleaned up. Should there be a
> Session.Remove(SessionId) or Session.Clear() of some sort?
>
>
>
> Also, in a run of unit tests where there are many sessions with different
> IDs created, wouldn't this cause unnecessary memory usage build up? And in
> production, decommissioning a counter-party relationship will still leave
> behind the Session object on the server unless the whole application is
> restarted.
>
>
>
> Regards,
>
> Joseph
>
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>
>


-- 
Grant Birchmeier
*Connamara Systems, LLC*
*Made-To-Measure Trading Solutions.*
Exactly what you need. No more. No less.
http://connamara.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20140226/632e1161/attachment-0001.htm>