[slf4j-user] Disabling QuickFIX/J logging

[Túlio Guimarães]

Hey guys, so I've been in touch with the broker I am connected to and the
Logger class was hardcoded to the API they provide that is why I could not
find any config file.

So, for now I created a dumb logger and passed as argument so no message
log is created.

Thank you for the support.

See ya!

On Tue, May 5, 2020 at 5:35 AM Túlio Guimarães <fx.tulio at gmail.com> wrote:

> Hi Matt and Joachim, thank you for the feedback.
>
> I am looking for any configuration file that allows me to disable the
> logging hehehe but I could not find any.
>
> My application is not running inside any container, it's just a bunch of
> jar files and a call to java on command line, then the app starts to listen
> to online quotes and the messages are flushed to a log file (that I wanna
> remove).
>
> Thank you for the information, I'll search a little more and repost if
> necessary.
>
> Regards.
>
> On Mon, May 4, 2020 at 8:05 PM Joachim Durchholz <jo at durchholz.org> wrote:
>
>> Am 04.05.20 um 16:25 schrieb Túlio Guimarães:
>> > Hi guys,
>> >
>> > So I've been looking for a way to disable quickfix/j logging but I
>> could
>> > not find anything helpful so far (my fault).
>>
>> SLF4J is just a common API for applications that want to write log
>> messages.
>>
>> If everything is done according to best practices, you'll have:
>>
>> 1) A logging backend (Logback, Commons Logging, java.util.logging,
>> whatever).
>> 2) SLF4J.
>> 3) The quickfix/j library.
>> 4) Your application, possibly inside a web container (e.g. Tomcat).
>>
>> Level 4 configures what backend is in use at level 1, and at what detail
>> level everything is being logged.
>>
>> Since you're asking on the SLF4J mailing list and talk about quickfix/j,
>> I am assuming that quickfix/j is indeed doing just SLF4J calls, and the
>> real backend is configured at level 4.
>> So you'll have to look at the logging configuration in level 4 to
>> determin what backend is in use, then look at the backend docs to find
>> out how it is being configured, then look into the configuration in
>> level 4 which gets interpreted by level 1.
>>
>> Hope this helps.
>>
>> Regards,
>> Jo
>> _______________________________________________
>> slf4j-user mailing list
>> slf4j-user at qos.ch
>> http://mailman.qos.ch/mailman/listinfo/slf4j-user
>
>
>
> --
> Abração!
> Tuio.
>


-- 
Abração!
Tuio.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/slf4j-user/attachments/20200505/1f48267b/attachment-0001.html>