At 04:50 PM 9/17/2006, you wrote:
>Trace is not working, I am using log4j 1.2
1.2.13? You should be specific. You might want to try 1.2.14, which
should be made an official release shortly. Until then, it is just a
release candidate, so wait for an official release announcement
before assum
Trace is not working, I am using log4j 1.2
It works only from the main class. For example, if I have a class
component, and I do some logging in this class using trace, it's never
shown.
Those are the priorities I found:
ALL -2147483648
TRACE 5000
DEBUG 1
INFO 2
WARN 3
ERROR 4
I went back yesterday to 1.2, after the shared JVM issue.
I didn't test it with trace, yet. I will report again if I find it a
problem.
Thanx
Jacob Kjome wrote:
If you are new to Log4j, I would avoid using 1.3alpha. You are welcome
to report a bug on 1.3alpha, but you won't get much suppor
If you are new to Log4j, I would avoid using 1.3alpha. You are
welcome to report a bug on 1.3alpha, but you won't get much support
for it. Releases have been few and far in between, though it looks
like there will be a new one coming up here shortly following the
release of Log4j-1.2.14. I
I am using logging-log4j-1.3alpha-8
I haven't used any configuration file. I am just following the baby
steps, and doing very basic logging. Here' part of my code:
In the main class, which is an applet:
logger = Logger.getLogger(this.getClass());
logger.addAppender(new FrameAppender(this,"Cont
At 11:23 AM 9/16/2006, you wrote:
>I changed it to logger.error, and it worked fine. Now I checked again
>the configuration and couldn't find what's wrong.
>May be this ??
>
>logger.setLevel(Level.ALL);
>
>but isn't suppose to log all levels ??
>if I am wrong, how do i fix this ??
>
Theoreticall
I changed it to logger.error, and it worked fine. Now I checked again
the configuration and couldn't find what's wrong.
May be this ??
logger.setLevel(Level.ALL);
but isn't suppose to log all levels ??
if I am wrong, how do i fix this ??
James Stauffer wrote:
Try changing it to logger.err
Try changing it to logger.error(msg, exception). If that works then
you probably have your config setup incorrectly. I think trace is
between debug and info so you probably need to lower the level.
On 9/16/06, Mansour <[EMAIL PROTECTED]> wrote:
Hi everybody:
I am tring to use logger.trace(msg
Hi everybody:
I am tring to use logger.trace(msg, exception) but I am getting
nothing. Nothing is being logged.
I am using in the same way I use logger.info () or logger.debug() . Some
thing like this:
try{
//do somehting
}catch (Exception e) { logger.trace("exception: ",e);}
I couldn't fin
