Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 13 Feb 2014 00:47:20 +0000 (UTC)
From: "Mike Drob (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12694526.1392136843773.34147.1392252440006@arcas>
In-Reply-To: <JIRA.12694526.1392136843773@arcas>
References: <JIRA.12694526.1392136843773@arcas>
Subject: [jira] [Commented] (ACCUMULO-2349) Accumulo should give some
 notification if there is no *_logger.xml file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mike Drob commented on ACCUMULO-2349:
-------------------------------------

> http://logging.apache.org/log4j/1.2/faq.html#a3.6

{quote}
Is there a way to get log4j to automatically reload a configuration file if it changes?

    Yes. Both the DOMConfigurator and the PropertyConfigurator support automatic reloading through the configureAndWatch method. See the API documentation for more details.

    Because the configureAndWatch launches a separate wathdog thread, and because there is no way to stop this thread in log4j 1.2, the configureAndWatch method is unsafe for use in J2EE envrironments where applications are recycled. 
{quote}

> Accumulo should give some notification if there is no *_logger.xml file
> -----------------------------------------------------------------------
>
>                 Key: ACCUMULO-2349
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2349
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: John Vines
>             Fix For: 1.7.0
>
>
> Right now if you're missing general_logger and the appropriate service_logger, it seems accumulo just happily carries on with no logs whatsoever. We should alter it to complain loudly if it's missing them.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)