The warning you are getting, is it on the client or on the server? I am assuming client (that is where I usually get this error). This means that either the client itself, or one of the libraries it is using, does logging, but not logging configuration (whether properties or xml) was found. You can either ignore the warning message (I usually do), or supply a simple log4j.properties file for the client's use.
Some warning that I received from client. But has a problem that I understand. If my client is EJB project, I will receive this warning. But if my client app is Java project, I not receive some warning!
That makes perfect sense.
You need to satisfy three conditions to get this warning:
1) No log4j.properties or log5j.xml file
2) The lag4j.jar file in your classpath
3) Invoke a method that tried to log something
Apparently, when your client calls an EJB, all three conditions are satisfied. For other clients, one or more of these conditions is not satisfied (probably not methods are doing logging).
Hi all !
Thanks about your guides. I solved my problems.