Return-Path: Delivered-To: apmail-logging-log4j-user-archive@www.apache.org Received: (qmail 44971 invoked from network); 2 Mar 2011 21:48:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Mar 2011 21:48:16 -0000 Received: (qmail 63658 invoked by uid 500); 2 Mar 2011 21:48:15 -0000 Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org Received: (qmail 63593 invoked by uid 500); 2 Mar 2011 21:48:15 -0000 Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@logging.apache.org Received: (qmail 63583 invoked by uid 99); 2 Mar 2011 21:48:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Mar 2011 21:48:14 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kangotam@gmail.com designates 209.85.212.47 as permitted sender) Received: from [209.85.212.47] (HELO mail-vw0-f47.google.com) (209.85.212.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Mar 2011 21:48:09 +0000 Received: by vws4 with SMTP id 4so488708vws.34 for ; Wed, 02 Mar 2011 13:47:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type; bh=xXxwK27xxRTqajkBLcA3l9Ds4vvx70zXMcqyacyRPFM=; b=RzeIgb4HLaaafd/dkgziIyoenMhtCiS3GEUHLRkyfvxOqLUVzMzMklJON6Y83e2ai/ R/RAyW244SJii8eukgjahP17mi/XYTkD66nDybT/2ubOfgRnXWlwdVYVSkPR0DKwOkdu UGhDc41QSQU6l8Rg8zZqc4GRd4i1zRUH1/35I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=opfGwf8Gf3Jx6V7AYD9mna8G2RX9oSFEDvkS31T5Y9Hr6+ny2X7joW6gFgicnjoJHs cqzrEE8aWUtrd7NDxtNCCueS6tCeqhFmuYHq41f29hI5bM+UfSS+lj00w5jIVsWpB/M7 0myI+/PHBHtFLrpH0/dpRIAhfKDJECUDtVA6c= Received: by 10.52.176.161 with SMTP id cj1mr508757vdc.268.1299102468115; Wed, 02 Mar 2011 13:47:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.180.136 with HTTP; Wed, 2 Mar 2011 13:47:07 -0800 (PST) From: Kannan G Date: Wed, 2 Mar 2011 23:47:07 +0200 Message-ID: Subject: Logging only specific number of lines To: log4j-user@logging.apache.org Content-Type: multipart/alternative; boundary=20cf3071cf8e238ed7049d86dd62 --20cf3071cf8e238ed7049d86dd62 Content-Type: text/plain; charset=ISO-8859-1 Hi Since my application is in integration platform(Fuse) log files grow easily, so we thought of controlling it by logging only specific number of lines whenever exceptions are thrown. Is this possible with log4j to log specific number of lines say 30 lines only instead entire stacktrace? Also i have a requirement of logging fatal errors to syslog and application exceptions to separate file. Is this possible to let log4j categorize the error and send to different logs? Or any standard of way of doing this. Thanks. Kann --20cf3071cf8e238ed7049d86dd62--