Thread: Re: [log4plsql] [log4plsql - Open Discussion] Code contribution - log to arbitrary file

hi

Welcome to log4plsql projets ;)

Whist is your sourceforge user?

Do you know the log4plsql feature to log in alert.log and trace file?


Guillaume



On Fri, Jan 23, 2009 at 1:20 AM, SourceForge.net <no...@so...>wrote:

>
> Read and respond to this message at:
> https://sourceforge.net/forum/message.php?msg_id=6220742
> By: nobody
>
> I would be interested in contributing some PLSQL code that does logging to
> arbitrary
> files with log file rotation/management. I know that currently it can be
> done
> via the log4j process, but it might be useful to have the option to log to
> a
> arbitrary file without the extra java process.
>
> let me know it it make sense or not, and if it makes let me know how can I
> proceed
> with it... you can email me at zoly at daxtechnologies dot com
>
>
>
> ______________________________________________________________________
> You are receiving this email because you elected to monitor this forum.
> To stop monitoring this forum, login to SourceForge.net and visit:
> https://sourceforge.net/forum/unmonitor.php?forum_id=170438
>

Hi,

Someone in log4plsq community think is a new interesting feature ?

Guillaume
---------- Forwarded message ----------
From: Zoltan Farkas <zo...@da...>
Date: Fri, Jan 23, 2009 at 6:23 PM
Subject: Re: [log4plsql - Open Discussion] Code contribution - log to
arbitrary file
To: guillaume moulard <gui...@fr...>


I am going over the code in Log4PLSql and found  some code that I think in
not optimal in ReaderThread.java:

public void run() {
    while (true) {
        ldbLogger.debug("ReaderLogDataBase: CallBD");
        readerDB.readlog(ldbLogger);
ldbLogger.debug("ReaderLogDataBase: EndCallBD");
        try {
            sleep(1000);
        } catch(InterruptedException e) {
            ldbLogger.error(e);           }
    }
 }

I believe in this case the InterruptedException handler should exit the
infinite loop, and since this case is not really an error the logging should
be changed to info.

This will allow you to stop your thread and effectively stop your java
process and implement a clean SIG_TERM process termination.

let me know what you think

Regards

--zoly





guillaume moulard wrote:

> hi
>
> Welcome to log4plsql projets ;)
>
> Whist is your sourceforge user?
>
> Do you know the log4plsql feature to log in alert.log and trace file?
>
>
> Guillaume
>
>
>
> On Fri, Jan 23, 2009 at 1:20 AM, SourceForge.net <no...@so...<mailto:
> no...@so...>> wrote:
>
>
>    Read and respond to this message at:
>    https://sourceforge.net/forum/message.php?msg_id=6220742
>    By: nobody
>
>    I would be interested in contributing some PLSQL code that does
>    logging to arbitrary
>    files with log file rotation/management. I know that currently it
>    can be done
>    via the log4j process, but it might be useful to have the option
>    to log to a
>    arbitrary file without the extra java process.
>
>    let me know it it make sense or not, and if it makes let me know
>    how can I proceed
>    with it... you can email me at zoly at daxtechnologies dot com
>
>
>
>    ______________________________________________________________________
>    You are receiving this email because you elected to monitor this
>    forum.
>    To stop monitoring this forum, login to SourceForge.net and visit:
>    https://sourceforge.net/forum/unmonitor.php?forum_id=170438
>
>
>