[ https://issues.apache.org/activemq/browse/AMQ-927?page=comments#action_37186 ] Hiram Chirino commented on AMQ-927: -----------------------------------
I just started up activemq from the command line and noticed this change. I think that the previous behaviour of logging to the console was a good idea. That way folks see when the broker is fully started and what transports are opened and such. > Default log4j.properties has stdout enabled and not the out file appender > ------------------------------------------------------------------------- > > Key: AMQ-927 > URL: https://issues.apache.org/activemq/browse/AMQ-927 > Project: ActiveMQ > Issue Type: Bug > Affects Versions: 4.0.1 > Reporter: Jason Dillon > Assigned To: Rob Davies > Priority: Trivial > Fix For: 4.1 > > > The default log4j.properties has: > {noformat} > log4j.rootLogger=INFO, stdout > {noformat} > and then goes on to say: > {noformat} > # CONSOLE appender not used by default > log4j.appender.stdout=org.apache.log4j.ConsoleAppender > .. > {noformat} > And it also has this header... which is misleading: > {noformat} > # > # The logging properties used during tests.. > # > {noformat} > Also not sure why this would be in data... nor do I ever see this being > created, even when out is enabled... > {noformat} > log4j.appender.out.file=${activemq.home}/data/activemq.log > {noformat} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
