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 <[email protected]> wrote: > Not exactly. It has got lots and lots of system.out messages. > > TIA > > --- On Fri, 1/16/09, Guilherme Costa <[email protected]> wrote: > > From: Guilherme Costa <[email protected]> > Subject: Re: Logging messages directed to stdout > To: "Log4J Users List" <[email protected]>, > [email protected] > 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 <[email protected]> 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 <[email protected]> wrote: > > > > From: Jay <[email protected]> > > Subject: Logging messages directed to stdout > > To: [email protected] > > 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 > > > > > > > > > > > > > > > > > > >
