I will check with the QA engineer who ran our tests. However, you might want
to test with Flume 1.3.0 which was just released. We actually use the CDH
version of Flume from Cloudera and so our tests had many of the fixes that are
in 1.3. I'm not sure what if what we were measuring is what you
One other thing I just remembered. When you are using the embedded appender
you are writing to the embedded flume. In our testing we found that we were
getting control back in our application long before the embedded Flume had a
chance to forward all the messages to the remote agent. If the
No, you aren't confused. When the EnhancedPatternLayout was incorporated from
Log4j 1.x it doesn't actually do that. In looking at the code it turns out the
WriterAppender is formatting the throwable, not the PatternLayout. That
behavior isn't correct. If you could create a Jira issue for
