accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3264) AuditMessageIT broken
Date Mon, 27 Oct 2014 18:06:34 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185530#comment-14185530
] 

Josh Elser commented on ACCUMULO-3264:
--------------------------------------

Ok, I think I see what's going on, and the problem stems from the fact that we don't setup
our "normal" logging for MiniAccumuloCluster/ITs. One subtlety of how the FileWatchdog classes
that Log4j uses to monitor configuration files is that it can handle the file existing and
not-existing. The only reason that our tests have been getting logging (before this change)
is because they inherits the log4j.properties from {{test/src/test/resources}}. The change
I made had reset the logger configuration but there was nothing to re-add the log4j.properties
from the maven module. So, because we also didn't have any of our standard logging set up,
we ended up getting no logger whatsoever.

> AuditMessageIT broken
> ---------------------
>
>                 Key: ACCUMULO-3264
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3264
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.2, 1.7.0
>
>
> Looks like I might have broken the AUDIT log in ACCUMULO-3258 as AuditMessageIT started
failing after those changes were pushed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message