Simple test is to change the appender CONSOLE from target to file (as FILE is) and write to a separate file. If this will work and you 'normal' configuration not you should check the appender configuration.
We tried your suggestion but we got message that "File" is not valid for console appender. What is interesting is that one time without making any changes to the xml file, we saw messages going to console and to the server.log. We did a restart of JBOSS and then nothing was shown on the console display and therefore nothing went to server.log
It seems we have an issue with the console appender not sending messages to console.
Sorry for the edits on this post, but after rereading everything, I think that you need to post your jboss-logj4.xml file because we need to see what you did so that we can tell you how to correct it.
Sorry, a bit unclear. What I meant is that you remove the appender CONSOLE and replace it by a copy of the FILE appender and rename the filename (i.e. console.log) and the appender name = CONSOLE.
The CONSOLE appender set a threshold INFO (no messages with more detail as INFO are logged to console)
In general, the CONSOLE and FILE appender are independent, if you never specify an appender except in the root-logger all will go to the declared appenders and filtered by the different appender.
See the apache log4j documentation http://logging.apache.org/log4j/
Thanks for the clarification. I thought it was strange to add a "File" param to the Console appender config :-)
I will give this a try.