Hi All I've been using Log4J for a couple of weeks and I have recently made use of it in a Java servlet.
I came across a bit of problem when the servlet was deployed, in that the admin guy doing the deployment introduced a space between the 1st servlet init parameter and the init parameter that held the location of the log4j.properties file that I was using to configure the logging in my servlet. The webserver (NES4.1) was stopped and restarted by the administrator and I began testing my servlet. I saw no log entries at all from Log4J but I could see that the servlet was being hit. I asked the admin guy to switch on log4j.debug, restart the webserver and I tried again - still no messages. I requested that the admin guy restart the webserver and redirect the stdout to a file which I could then look at, lo and behold, I could see log4j error messages informing me that Log4J had not been initialised - due to the init param problem. I had the admin guy correct the init param and Log4j in initialised and logged great. Is there another anyway of achieving this without having to redirect stdout? Cheers Anthony Pounder Systems Technical Consultant R & D Team Experian Information Solutions Direct Dial: 0115 992 2861 [EMAIL PROTECTED] ======================================================================= Information in this email and any attachments are confidential, and may not be copied or used by anyone other than the addressee, nor disclosed to any third party without our permission. There is no intention to create any legally binding contract or other commitment through the use of this email. Experian Limited (registration number 653331). Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
