{{Quickfixn}} ClientHandlerThread's debug log file

[Alan Kisiev]

That was my first thought, but ClientHandlerThread provides an internal interface method  "ILog GetLog()" which returns exactly that  log which was instantiated in constructor.
So I decided not to mess with dependencies and simply made it dependent on a  specific configuration key. If key exists and enabled it will use FileLog, otherwise - NullLog.

And yes, I agree that using FileLog in this context looks pretty much like a quick workaround/alternative for a proper logging :)

28.02.2014, 22:10, "Grant Birchmeier" <gbirchmeier at connamara.com>:
> The logging in QF/n needs to be improved.  There is a submitted fix, but it's not quite ready, and I haven't had time to wrap it up.
>
> The ClientHandlerThread logging doesn't use the regular logger, which is just not right.  I don't know the history of why it is this way.
>
> Looks like there is no config setting to disable the ClientHandlerThread logging, but if you want to hack the code, you could go into ClientHandlerThread.cs and comment out the constructor line that assigns _log and the related lines in the rest of this class that use _log.
>
> On Fri, Feb 28, 2014 at 9:32 AM, Alan Kisiev <os.alan at yandex.ru> wrote:
>> 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
>> _______________________________________________
>> 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
>
> ,
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com