ln -sf ../../lib/log4j.jar server/all/deploy/ejb3.deployer/log4j.jar
ln -sf ../../lib/log4j.jar server/default/deploy/ejb3.deployer/log4j.jar
Thank you for the information, but it did not help. I believe that the problem is on the client side. Maybe to do with the jboss-remoting package.
Yes - it was a little bit late and I didn't read carefully ... :(
Your problem is, that you probably need to configure log4j. E.g. create a file like /tmp/log4j.properties with the following content:
log4j.rootCategory=INFO, stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%r %p [ %t ] %c - %m%n
And start your application with the option -Dlog4j.configuration=file:///tmp/log4j.properties .
Optionally you may include the file into your jar at the top level - than log4j will find and use it automatically ... For more info, read the log4j short manual...
yes, you need to have a log4j.xml in your classpath. Download EJB3 Beta1 and you'll see that each tutorial example comes with a log4j.xml file.
try adding jboss-common.jar