Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have my own logging engine which writes the logs on a separate thread with a blocking queue. For the sake of using “standard software” I am thinking about switching to log4j.
I don’t want my highly concurrent software to be slowed down by log commands that write everything to disk as some as the command is called. Can log4j be used as a dumpster instead?
Log4j is the logging implementation on most JavaEE app-servers out there, so that’s a good advert for its concurrency abilities.
Having said that, I have seen Log4j 1.2 deadlock under high load conditions. A bit of investigation highlighted some scarily bad synchronization in the source code. Apparently, this was fixed in Log4j 1.3, although development on this has slowed or stopped altogether – I get the feeling much of the source was unsalvageable.
However, if you’re free to choose, then you should consider Logback instead, the spiritual successor to Log4j. It’s a ground-up redesign, and is probably a better option for you.