[log4plsql] RE: Log4jBackgroundProcess Problem

[<log...@li...>]

Hi Jose,


For ChainSAW could you use pLOGTABLE =3D> TRUE. I think is only necessary t=
o log in table.



In my 10G when a log with pLOG4J =3D> TRUE, if there is no Log4jBackgroundP=
rocess, my plsql block is in wait. When I launch the
Log4jBackgroundProcess the process restart to log.

Be careful, if you shutdown you database, all message in pipe is lost.







-- My test case -----------------------

Declare

    pCTX PLOG.LOG_CTX :=3D PLOG.init (pSECTION     =3D> 'firstSection',

                                    pLEVEL       =3D> PLOG.LDEBUG,

                                    pLOG4J       =3D> TRUE

                                    );

begin

  for i in 1..2000 loop

     PLOG.debug (pCTX, 'Hello LOG:'||i);

  end loop;

end;

/



Regards,
Guillaume Moulard
gmo...@us...

Project : LOG4PLSQL : Oracle Database Loggin tools
see : http://log4plsql.sourceforge.net/
and :  http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-i=
nfo or
http://www.mail-archive.com/log...@li...
for  log...@li...

-----Message d'origine-----
De : SAG - Jose Antonio Tarifa

Envoy=E9 : jeudi 6 mai 2004 15:05
=C0 : Guillaume Moulard
Objet : RE: Log4jBackgroundProcess Problem



Hello Guillaume,



thank your for your reply. But my problem is another.



We MUST use pLOG4J =3D> TRUE, because we want to trace every log in our Cha=
inSAW client.  But the problem is when
Log4jBackgroundProcess is not running because an error in Java or another p=
roblem (imagine the process shuts down suddenly because a
socket error, or anything else).  Then, Oracle seems to be blocked sending =
logs through the pipe to the process.  And that is my
problem, if the process stops suddenly, every PL/SQL procedure in our datab=
ase using Log4PLSQL are blocked.



greetings,

      Jos=E9 Antonio Tarifa Lorenzo



 -----Mensaje original-----

De: Guillaume Moulard [mailto:gmo...@us...]

Enviado el: jueves, 06 de mayo de 2004 13:03

Para: log...@li...

Asunto: RE: Log4jBackgroundProcess Problem



Jos=E9,



If you don't use in the context the pLOG4J =3D> TRUE it in not necessary to=
 lauche the Log4jBackgroundProcess.



I don't now the unstable behaviour of Oracle when PL/SQL code writes a log.=
 Perapse you can send more informations about you

problem.





Regards,

Guillaume Moulard

gmo...@us...



Project : LOG4PLSQL : Oracle Database Loggin tools

see : http://log4plsql.sourceforge.net/

and :  http://sourceforge.net/mailarchive/forum.php?forum=3Dlog4plsql-all-i=
nfo or

http://www.mail-archive.com/log...@li...

for  log...@li...









-----Message d'origine-----

De : jatarifa

Envoy=E9 : vendredi 30 avril 2004 11:05

=C0 : gmo...@us...

Objet : Log4jBackgroundProcess Problem







Hello Guillaume.















I am the technical consultor of OMEL (Operador del Mercado







Electrico Espa=F1ol - http://www.omel.es) and we are very







interested to incorporate your development to our Database,







because we think is a great tool to monitorize the electricity







market.















But we have a problem.  We have put in our test environment







the latest version of Log4PLSQL and we have noticed an







unstable behaviour of Oracle when PL/SQL code writes a log







to Log4jBackgroundProcess and this Java program is not







running.















Oracle seems to be locked on PLOG statement on PL/SQL







code until Log4jBackgroundProcess is started!!!















Is that a normal behaviour (I think no) of Oracle or is







something wrong in PLOG PLSQL code?















As I said after, we are very interested in Log4PLSQL and the







Spain Electricity Market would be improved with this tool.















Thank you















      Jos=E9 Antonio Tarifa