>> I would log to the database. In the same transaction as the operation you
want to log about. <<
Beware ... this approach will never record any failed transactions, because the
logging will be rolled back along with everything else!
It really depends on what you really mean by 'reliability'. I
Howdy,
Not mainframe ;) Sun enterprise servers (Solaris 8 and 9 operating
systems), as well as windows machines (mostly Windows 2000 servers).
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Lin, Bosheng [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 15, 2004 11:31 AM
To: &
, 2004 11:31 AM
>To: 'Log4J Users List'
>Subject: RE: Question on Log4J Reliability
>
>By in production, you mean Windows/Linux/Unix or Mainframe like IBM
OS390?
>
>I am more interested to hear people from mainframe side.
>
>Thanks,
>
>Bosheng
>
>-Or
: RE: Question on Log4J Reliability
Howdy,
We've been using log4j in production for years without any failures.
He means reliable in a less common sense of the word, I think, in that log4j
will notify you if it fails and try to do its best to continue.
Yoav Shapira
Millennium ChemInform
--
>From: Edmund Y Dean [mailto:[EMAIL PROTECTED]
>Sent: Thursday, January 15, 2004 11:30 AM
>To: Log4J Users List
>Subject: Question on Log4J Reliability
>
>Greetings all,
>
>I've been looking into possibly using Log4J for some
>application/transactional logging uses
Greetings all,
I've been looking into possibly using Log4J for some
application/transactional logging uses (like access logs or user
auditing ,etc.) However, I'm concerned about the statement in the FAQ
that it is not a "reliable" logging system. What is the definition of a
"reliable" loggin
