logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jay <difficult...@yahoo.com>
Subject Re: Logging messages directed to stdout
Date Fri, 16 Jan 2009 14:41:09 GMT
Yes. That is what I asked in my original email. Any sample applications/guidelines, which will
not break any of my 3 requirements ?
 
TIA

--- On Fri, 1/16/09, Guilherme Costa <gccostabr@gmail.com> wrote:

From: Guilherme Costa <gccostabr@gmail.com>
Subject: Re: Logging messages directed to stdout
To: "Log4J Users List" <log4j-user@logging.apache.org>, difficult_id@yahoo.com
Date: Friday, January 16, 2009, 9:37 AM

Maybe you could create an application that will read all the outputs of your
old application and throw the messages using log4j!


On Fri, Jan 16, 2009 at 12:30 PM, Jay <difficult_id@yahoo.com> wrote:

> Not exactly. It has got lots and lots of system.out messages.
>
> TIA
>
> --- On Fri, 1/16/09, Guilherme Costa <gccostabr@gmail.com> wrote:
>
> From: Guilherme Costa <gccostabr@gmail.com>
> Subject: Re: Logging messages directed to stdout
> To: "Log4J Users List" <log4j-user@logging.apache.org>,
> difficult_id@yahoo.com
> Date: Friday, January 16, 2009, 9:27 AM
>
> The application is sending the messages thru log4j ConsoleAppender?!
>
> On Fri, Jan 16, 2009 at 12:19 PM, Jay <difficult_id@yahoo.com>
wrote:
>
> > Just wanted to add that, the application redirects lot of messages to
> > stderr also and they also should be logged in the same log file.
> >
> > TIA
> >
> > --- On Fri, 1/16/09, Jay <difficult_id@yahoo.com> wrote:
> >
> > From: Jay <difficult_id@yahoo.com>
> > Subject: Logging messages directed to stdout
> > To: log4j-user@logging.apache.org
> > Date: Friday, January 16, 2009, 9:16 AM
> >
> > OS Linux:
> >
> > Am using an application which redirects lot of messages to stdout
> >
> > I do not have access to the source code of this application.
> >
> > I would like to log4j these messages through RollingFileAppender.
> > Requirements:
> >
> > 1) The no of lines to be logged are very high and very fast rate.
> >
> > 2) The new logging mechanism should not have any impact on the
> performance
> > of
> > the application or the system
> >
> > 3) Not even single line of the message should be missed.
> >
> > Could someone please let me know, what is the best way to achieve
this ?
> >
> > TIA
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>



      
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message