[ https://issues.apache.org/jira/browse/UIMA-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789819#action_12789819 ]
Burn Lewis commented on UIMA-1703: ---------------------------------- Since the UIMA_AS need for this properties file is minimal ... Spring uses it now that we include a log4j jar file in the classpath when we load from the ActiveMQ directories ... and normally nothing is written to it ... I suggest we just add a few entries to the UIMA Logger.properties file and share it with both loggers. I've found that the following suppresses the warning about missing appenders, and suppresses the multiple "retrying in 5 ms" messages when a service fails to connect to its input broker. log4j.rootLogger=WARN, stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout > UIMA AS service uses the same log4j.properties file as the AMQ broker > ---------------------------------------------------------------------- > > Key: UIMA-1703 > URL: https://issues.apache.org/jira/browse/UIMA-1703 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout > Reporter: Jerry Cwiklik > Fix For: 2.3AS > > > Same log4j.properties file is used by AMQ broker started from startBroker > script and by UIMA AS service. The UIMA AS service startup script sets this > property > -Dlog4j.configuration=file:c:\uima\releases\2.3.0-07\apache-uima\as_config\log4j.properties > it is picked up by AMQ and Spring and used for logging. The same > log4j.properties file is copied from as_config directory to > UIMA_HOME/bin/amq/config when startBroker script is started for the first > time. So, the same configuration is used by two different processes. This > doesnt seem right. We most likely need different log4j.properties for each > process since each of them needs to log at different level. For example, the > broker needs to be started with INFO level logging to show status information > on broker startup. Logging at INFO level when UIMA AS service starts may lead > to excessive messages being logged. An instance of this is when a broker is > killed when a service is running. The broker failure forces listeners to > reconnect using Spring's blocking call. This call produces log msgs at INFO > level at 5 sec intervals. > The fix would be to use a different property files. UIMA AS should use a > basic configuration with a single log of say 100MB size and should log at > WARNING level only. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.