|
From: Christoph J. <chr...@ma...> - 2018-08-31 08:29:50
|
OK, good news. Just wanted to make sure since there were some minor changes to the SLF4JLog class in the last release. I might find some time next week to set up a little test. Chris. On 31/08/18 10:25, Xiau Wei Toon wrote: > Reverted to 2.0.0, does not work. In fact, we absolutely must use 2.1 since we rely on the new > rawString method. > > If you were the one implementing, how would you do it? The requirement is simple. I want to route > all event messages regardless of session into a daily rolling file using Log4j. > > On Fri, 31 Aug 2018, 4:11 pm Christoph John, <chr...@ma... > <mailto:chr...@ma...>> wrote: > > Hmm, OK. > Just to rule outany regression error: could you please test with version 2.0.0? > > Thanks, > Chris. > > > On 31/08/18 10:06, Xiau Wei Toon wrote: >> Indeed that is correct. The logfile is created but permanently empty. I have: >> 1. Removed all the default slf4j configuration from session settings >> 2. Added appender for log4j.logger.quickfixj.errorEvent >> >> Files are created, but empty. I redirect all the screen logs from java execute line to a >> dumpfile and I can see all quickfixj events and msg logs generated without any WARN or ERROR. >> Turning on additivity will not make a copy in system_debug.log as well. Version2.1 is the one >> used. >> >> >> On Fri, 31 Aug 2018, 3:31 pm Christoph John, <chr...@ma... >> <mailto:chr...@ma...>> wrote: >> >> So you are saying the file ./logs/quickfix.log gets created but with no content? No >> messages and no events? >> The SLF4J settings you are passing are the default ones as far as I can see. What happens >> if you omit them? >> I have just seen there is an undocumented setting SLF4JLogErrorEventCategory which >> defaults to "quickfixj.errorEvent". What happens if you add that to your settings? >> >> IMHO it can only be a minor config error since this feature is used by many people. Which >> QFJ version are you using BTW? >> >> Chris. >> >> On 31/08/18 08:59, ToonXW wrote: >>> QuickFIX/J Documentation:http://www.quickfixj.org/documentation/ >>> QuickFIX/J Support:http://www.quickfixj.org/support/ >>> >>> >>> I have been trying to route all event logs to one daily rolling log file, >>> however it is unclear what is going wrong. I verified that quickfixj picked >>> up the log4j.properties file (by forcing an exception) and also confirmed >>> that the target log file was created post startup. Please advise. >>> >>> *SessionSettings:* >>> SLF4JLogEventCategory=quickfixj.event >>> SLF4JLogIncomingMessageCategory=quickfixj.incoming >>> SLF4JLogOutgoingMessageCategory=quickfixj.outgoing >>> SLF4JLogPrependSessionID=Y >>> SLF4JLogHeartbeats=Y >>> >>> *When building ThreadedSocketInitiator:* >>> LogFactory logFactory = new SLF4JLogFactory(sessionSettings); >>> >>> *log4j.properties:* >>> # Root logger option >>> log4j.rootLogger=DEBUG, core >>> # Write to log files, support date rolling. >>> log4j.appender.core=org.apache.log4j.DailyRollingFileAppender >>> log4j.appender.core.Append=true >>> log4j.appender.core.File=./logs/system_debug.log >>> log4j.appender.core.DatePattern='.'yyyy-MM-dd >>> log4j.appender.core.layout=org.apache.log4j.PatternLayout >>> log4j.appender.core.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss.SSS} >>> %-5p %c{1}:%L - %m%n >>> # Quickfixj appender(s): quickfixj.event / quickfixj.incoming / >>> quickfixj.outgoing >>> log4j.logger.quickfixj.event=DEBUG, quickfixEvents >>> log4j.additivity.quickfixj.event=false; >>> log4j.appender.quickfixEvents=org.apache.log4j.DailyRollingFileAppender >>> log4j.appender.quickfixEvents.Append=true >>> log4j.appender.quickfixEvents.File=./logs/quickfix.log >>> log4j.appender.quickfixEvents.DatePattern='.'yyyy-MM-dd >>> log4j.appender.quickfixEvents.layout=org.apache.log4j.PatternLayout >>> log4j.appender.quickfixEvents.layout.ConversionPattern=%d{yyyy-MM-dd >>> HH:mm:ss.SSS} %-5p %c{1}:%L - %m%n >>> > > -- > Christoph John > Software Engineering > T +49 241 557080-28 > chr...@ma... <mailto:chr...@ma...> > > MACD GmbH > Oppenhoffallee 103 > 52066 Aachen, Germany > www.macd.com <http://www.macd.com> > > Amtsgericht Aachen: HRB 8151 > Ust.-Id: DE 813021663 > Geschäftsführer: George Macdonald > -- Christoph John Software Engineering T +49 241 557080-28 chr...@ma... MACD GmbH Oppenhoffallee 103 52066 Aachen, Germany www.macd.com Amtsgericht Aachen: HRB 8151 Ust.-Id: DE 813021663 Geschäftsführer: George Macdonald |