Return-Path: X-Original-To: apmail-empire-db-user-archive@www.apache.org Delivered-To: apmail-empire-db-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AA3E918072 for ; Fri, 12 Feb 2016 12:46:38 +0000 (UTC) Received: (qmail 96829 invoked by uid 500); 12 Feb 2016 12:46:38 -0000 Delivered-To: apmail-empire-db-user-archive@empire-db.apache.org Received: (qmail 96806 invoked by uid 500); 12 Feb 2016 12:46:38 -0000 Mailing-List: contact user-help@empire-db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@empire-db.apache.org Delivered-To: mailing list user@empire-db.apache.org Received: (qmail 96795 invoked by uid 99); 12 Feb 2016 12:46:38 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Feb 2016 12:46:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 24C58C0D87 for ; Fri, 12 Feb 2016 12:46:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.671 X-Spam-Level: ** X-Spam-Status: No, score=2.671 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.329] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id XUOmcaJKmefP for ; Fri, 12 Feb 2016 12:46:36 +0000 (UTC) Received: from remote.esteam.de (mail.esteam.de [5.158.128.25]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id A0B3224EB7 for ; Fri, 12 Feb 2016 12:46:35 +0000 (UTC) Received: from ESTEAMSBS11.esteam.local ([fe80::38fe:2743:5c01:2b76]) by ESTEAMSBS11.esteam.local ([fe80::38fe:2743:5c01:2b76%12]) with mapi id 14.02.0387.000; Fri, 12 Feb 2016 13:46:28 +0100 From: =?iso-8859-1?Q?Rainer_D=F6bele?= To: "user@empire-db.apache.org" Subject: re: Stop EmpireDB Logging by Default Thread-Topic: Stop EmpireDB Logging by Default Thread-Index: AdFlk0ZFE2fVCSh8TCC4nU4fJNJZKA== Date: Fri, 12 Feb 2016 12:46:28 +0000 Message-ID: <723ECD29D465BC46ADF7646B1CC726141A82EB84@ESTEAMSBS11.esteam.local> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.57] Content-Type: multipart/alternative; boundary="_000_723ECD29D465BC46ADF7646B1CC726141A82EB84ESTEAMSBS11este_" MIME-Version: 1.0 --_000_723ECD29D465BC46ADF7646B1CC726141A82EB84ESTEAMSBS11este_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Chieu in our examples we are using log4j and SQL statement logging is activated l= ike this:

Set the level to "info" or "warn" and you will not get SQL statements in yo= ur logfile. Regards, Rainer from: Nguyen, Chieu X [mailto:chieu.nguyen@verizon.com] to: user@empire-db.apache.org re: Stop EmpireDB Logging by Default Hi All, Currently, I see these log statements in my log file. This causing our log= file to grow too quickly. How do I stop EmpireDB from logging this out? [Feb/11/16 00:11:43] INFO org.apache.empire.db.DBDatabase - Executing: UP= DATE CIRCUIT_AZ SET LAST_UPDATE=3Dsysdate WHERE CIRCUIT_AZ_ID=3D12627769 Thank You, Chieu Nguyen Chieu.nguyen@verizon.com --_000_723ECD29D465BC46ADF7646B1CC726141A82EB84ESTEAMSBS11este_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Dear Chieu<= /span>

in our = examples we are using log4j and SQL statement logging is activated like thi= s:

&n= bsp;

= &nb= sp;

<log= ger name=3D"org.apache.empire.db.DBDatabase" additivity=3D"f= alse">

&= nbsp; &nbs= p; <level value=3D"debug"/>

&= nbsp; &nbs= p; <appender-ref ref=3D"default"/><= /p>

</lo= gger>

&n= bsp;

Set the= level to “info” or “warn” and you will not get SQL= statements in your logfile.

&n= bsp;

Regards= ,

Rainer<= o:p>

&n= bsp;

from: Nguyen, Chieu X [mailto:chieu.nguyen@verizon.com]
to: user@empire-db.apache.org
re: Stop EmpireDB Logging by Default

Hi All,

Currently, I see these log stat= ements in my log file. This causing our log file to grow too quickly.= How do I stop EmpireDB from logging this out?

[Feb/11/16 00:11:43] INFO = org.apache.empire.db.DBDatabase - Executing: UPDATE CIRCUIT_AZ<= /o:p>

SET LAST_UPDATE=3Dsysdate<= /o:p>

WHERE CIRCUIT_AZ_ID=3D12627769<= o:p>

Thank You,

Chieu Nguyen

Chieu.nguyen@verizon.com<= o:p>

--_000_723ECD29D465BC46ADF7646B1CC726141A82EB84ESTEAMSBS11este_--