Which approach is good?

Question

I don;t know if I am posting this on the right forum. So Please....
The question is with respect to logging.
I know using the log4j , we can configure/direct the logs based on the package names.
Now I have one package and in the same package, In every class, I have to normal log and also do audit log. And now the audit log should go to db.
Now I have three proposals, I want you to tell me which one is better and why
Case 1)
Create a class called AdminLogger and have a static method "log" which would do log the message to the DB.
Q) If I use static method, I believe I need to put synchronized key word to the "log" method ?. Because, it might be called from different places. And more over there is a possibility that several users may be invoking the objects.
case 2)
Create a class called AdminLogger with no public constructor and have a method called getLogger which would return a new instance every time and call log method on the instance
Q) Pretty much it creates a new instance of AdminLogger for every log.
case 3) Have one static instance for each class like
public static AuditLogger logger = new AuditLogger();
Q) This would create n instances for n classes. and they will be in memory all the time.
thanks

Answer 1

Log4j is thread safety you do not have to synchronize your static methods.
Regards,
Sławomir Wojtasiak