{{Quickfixn}} ClientHandlerThread's debug log file

[Alan Kisiev]

Thanks for the reply. 
It is not the same log that Initiator/Acceptor use. ClientHandlerThread classs uses FileLog class explicitly - it instantiates it in the constructor and does not use factory class. 
But anyway, I didn't find how to disable that logging "out of the box" so to speak, so I had to make some minor changes to the source code.

28.02.2014, 17:22, "Dinko Papak" <rimokatolik at outlook.com>:
> You can always use your own logger, and nit use default one which I don't like for multiple reasons. Just create small class implementing ILogFactory, implement Create method, instantiate object and pass it to proper constructor (either ThreadedSocketAcceptor or SocketInitiator)
>
> Sent from my Windows Phone
>
> ----------------------------------------
> From: Alan Kisiev
> Sent: ‎2/‎26/‎2014 11:28
> To: Mailing list for QuickFIX/n
> Subject: {{Quickfixn}} ClientHandlerThread's debug log file
>
> Hello!
>
> Acceptor connections use "ClientHandlerThread" class, which uses "FileLog" to log its messages.
> With my workflow, I have to restart/recreate fix applications, but I often face with file access related errors.
> So I am trying to avoid where possible file system IO: I have implemented database log and message store, but "ClientHandlerThread" uses FileLog explicitly, so... i still face thread-related problems accessing those files.
>
> My question: am I missing something in the code and there is a way to disable filesystem IO completely (including "ClientHandlerThread") or I have to make changes to the source code? (really don't want to do it).
> Thanks in advance!
>
> ,
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com