-
1. Re: Logging problem on the client, that uses Jboss JMS.
adrian.brock Sep 19, 2003 6:01 PM (in response to le_ma_)Which version are you using, that should be fixed.
Regards,
Adrian -
2. Re: Logging problem on the client, that uses Jboss JMS.
adrian.brock Sep 19, 2003 6:02 PM (in response to le_ma_)It is just noise anyway.
If you want logging add log4j.jar to your classpath
and a log4j.properties (at the front).
Regards,
Adrian -
3. Re: Logging problem on the client, that uses Jboss JMS.
le_ma_ Sep 20, 2003 10:10 AM (in response to le_ma_)Thank you, Adrian!
I use JBoss-3_2_2_RC3. Something funny continues to happen. Sure, I am allready have log4j.jar in my client's classpath. Below I explain my tricky program.
/*
* Created on 19.09.2003
*/
package examples.examp_1;
import javax.naming.Context;
import javax.naming.InitialContext;
import org.apache.log4j.BasicConfigurator;
import org.apache.log4j.Logger;
public class Main {
public static void main(String[] args) throws Exception {
// This lines only for LOG4J test purposes:
BasicConfigurator.configure();
Logger logger_ = Logger.getLogger("xxx");
logger_.info("info (1)");
logger_.warn("warn (1)");
logger_.error("error (1)");
// Create initial JNDI context.
Context ctx_ = new InitialContext(System.getProperties());
}
}
Result of it is:
0 [main] INFO xxx - info (1)
10 [main] WARN xxx - warn (1)
10 [main] ERROR xxx - error (1)
Failed to initalize pulgin: org.jboss.logging.Log4jLoggerPlugin@b0ce8f
If I comment out line "BasicConfigurator.configure();", output will be:
log4j:WARN No appenders could be found for logger (xxx).
log4j:WARN Please initialize the log4j system properly.
Failed to initalize pulgin: org.jboss.logging.Log4jLoggerPlugin@1f78ef1
As for LOG4J itself - all is ok. But jboss requires something special. May be you know What?... :-) -
4. Re: Logging problem on the client, that uses Jboss JMS.
adrian.brock Sep 20, 2003 11:36 AM (in response to le_ma_)No idea. You'll have to debug the JBoss class to
see what error is causing the failure.
The problem that was fixed I referred to before was the
opposite, where it complained when log4j wasn't present.
Regards,
Adrian -
5. Re: Logging problem on the client, that uses Jboss JMS.
le_ma_ Sep 20, 2003 1:35 PM (in response to le_ma_)Adrian, many thanks for your answers. That was my fault. I'm working in Eclipse and added log4j.jar into "User classes" instead of "Bootstrap classes" list.
(but I needed to debug code to realise this ;-)))
Thank you!