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: '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 > >-----Original Message----- >From: Shapira, Yoav [mailto:[EMAIL PROTECTED] >Sent: Thursday, January 15, 2004 11:32 AM >To: Log4J Users List >Subject: 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 ChemInformatics > > >>-----Original Message----- >>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 (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" logging system? Is Log4J recommended only for use for >>development/debugging/system status type logging, or is it robust >enough >>for transactional logging? >> >>If Log4J isnt really suited to the task, can anyone recommend something >>that might be better? >> >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] > > > > >This e-mail, including any attachments, is a confidential business >communication, and may contain information that is confidential, >proprietary >and/or privileged. This e-mail is intended only for the individual(s) to >whom it is addressed, and may not be saved, copied, printed, disclosed or >used by anyone else. If you are not the(an) intended recipient, please >immediately delete this e-mail from your computer system and notify the >sender. Thank you. > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
