Return-Path: Mailing-List: contact turbine-torque-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list turbine-torque-user@jakarta.apache.org Received: (qmail 3038 invoked by uid 98); 16 Dec 2002 23:34:53 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Received: (qmail 3016 invoked from network); 16 Dec 2002 23:34:51 -0000 Received: from daedalus.apache.org (HELO apache.org) (63.251.56.142) by nagoya.betaversion.org with SMTP; 16 Dec 2002 23:34:51 -0000 Received: (qmail 78870 invoked by uid 500); 16 Dec 2002 23:33:35 -0000 Received: (qmail 78863 invoked from network); 16 Dec 2002 23:33:35 -0000 Received: from qodns00.genelogic.com (149.2.141.40) by daedalus.apache.org with SMTP; 16 Dec 2002 23:33:35 -0000 Received: from qolotus00.genelogic.com (qolotus00 [10.1.1.21]) by qodns00.genelogic.com (8.11.0/8.11.0) with ESMTP id gBGNXIK10846 for ; Mon, 16 Dec 2002 18:33:18 -0500 (EST) Subject: Can I stop Torque's console logging? To: "Turbine Torque Users List" X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 Message-ID: From: JDiggans@genelogic.com Date: Mon, 16 Dec 2002 18:31:47 -0500 X-MIMETrack: Serialize by Router on QOLOTUS00/Genelogic(Release 5.0.10 |March 22, 2002) at 12/16/2002 06:33:06 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N At the moment Torque is dumping all its queries to the console and to a file and I cannot figure out where and how I'm telling it to do this. The only logging info I have in Torque.properties is: log4j.category.org.apache.torque = ALL, org.apache.torque log4j.appender.org.apache.torque = org.apache.log4j.FileAppender log4j.appender.org.apache.torque.file = ${torque.applicationRoot}/logs/torque.log log4j.appender.org.apache.torque.layout = org.apache.log4j.PatternLayout log4j.appender.org.apache.torque.layout.conversionPattern = %d [%t] %-5p %c - %m%n log4j.appender.org.apache.torque.append = false and the only console-ish logging I'm doing is in TurbineResources.properties: # A facility for debugging applications. Messages will go both # to the log file and the server console. services.LoggingService.debug.destination.file=/logs/turbine.log services.LoggingService.debug.destination.console=true services.LoggingService.debug.className=org.apache.turbine.services.logging.FileLogger services.LoggingService.debug.level=INFO Is the TurbineResources logging services pushing that setup down through to Torque? It doesn't seem so, because if I set console=false and level = ERROR I still get queries by the hundreds printed to STDOUT. Any ideas? -j