[log4plsql] Log4plsql problem
Brought to you by:
gmoulard
From: <log...@li...> - 2004-06-07 16:12:52
|
Hi, We are using Log4plsql Background process to log for external appenders = using log4j. All the appenders are getting the messages if no threshold is not set. In case threshold is set for the appenders, appenders are not getting = the messages. Appenders are getting Initialization messages, and not getting the = messages from DB_PIPE. I think the problem is at dbLogger.callAppenders(event) of = ReaderLogDataBase.sqlj, as the threshold is set for the event reading = from cache (dynamic level).This dynamic level is different from log4j = default levels. Log4j default level are=20 public final static int OFF_INT =3D Integer.MAX_VALUE; public final static int FATAL_INT =3D 50000; public final static int ERROR_INT =3D 40000; public final static int WARN_INT =3D 30000; public final static int INFO_INT =3D 20000; public final static int DEBUG_INT =3D 10000; //public final static int FINE_INT =3D DEBUG_INT; public final static int ALL_INT =3D Integer.MIN_VALUE; And these are reverse orders also ( as compared with the levels = log4plsql levels in the table). Is it possible to change the code ReaderLogDataBase so that it uses the = log4j levels, or the values in the table can be changed according to log4j levels? I would appreciate if you can look at the it and let us know the = solution. Thanks&Regards, Ramakrishna. Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. |