[
https://issues.apache.org/jira/browse/KAFKA-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461120#comment-13461120
]
nicu marasoiu commented on KAFKA-244:
-------------------------------------
it looks similar to the initial test but in debug i found that this one
configures log4j for the first time when explictly called in test, while the
other was already initialized at that point (was a second call to log4j
PropertyConfigurer.doConfigure).
Other info: my tests use TestNG attributes. I mainly reproduced it with
rootLogger using Kafka appender, but also when it did not.
> Improve log4j appender to use kafka.producer.Producer, and support
> zk.connect|broker.list options
> ---------------------------------------------------------------------------------------------------
>
> Key: KAFKA-244
> URL: https://issues.apache.org/jira/browse/KAFKA-244
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Affects Versions: 0.7.1
> Reporter: Stefano Santoro
> Assignee: Stefano Santoro
> Labels: log4j, newbie
> Fix For: 0.7.1
>
> Attachments: kafka-244-v3.patch, Log4jAppender.patch,
> Log4jAppenderWithWorkingZkConnect.patch
>
>
> Taken from #kafka IRC session with Neha Narkhede:
> The log4j appender is quite obsolete, there are a few things to change there.
> Make it use the kafka.producer.Producer instead of SyncProducer. That allows
> you to use either the broker.list or the zk.connect option
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
