This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Log files are like a heaven when any application goes live .
So is there any good solution available for logging. At present what i do , when ever any method is invoked in a servlet or a java code , i'm logging a message like "Came into getCustInfo() with parameters .. ... ..." and some processed results, is there any better solution, that makes the application support maintenance easier.
Logging is essential for the application and the performance of the application too. Sometimes we have to do a lot of logging in our application to track down the exact problems. Log4J today is the most popular logger component used and is said to be one of the best as far as performance is concerned.
I am curious to know the reasons for log4j being performing better than any custom made component. What makes Log4J log messages faster than other components ?
Its true that Log files are Heaven, when an application goes to production. But the second part is, after some time in production, it should be taken care that these Log files dont become a HELL.
ya, IO operations are very costly which may directly degrade the performance of your application.
so use widely accepted tools like Log4j, which has different levels of logging and you can control which level should be logged, what should the threshold file size should be. What should be done when the file size reaches the threshold limit..etc
As thumb of rule, Dont try to re-invent the wheel.
Work like you don't need the money. Love like you've never been hated. Dance like nobody's watching. Sing like nobody's listening. Live like it's Heaven on Earth.
Currently I Reside HereWEBlog