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. If you find this issue in 1.2.14, it would
cause more concern. Trace is a new level to both 1.3 and the 1.2.xx
branch, so it is possible some nuances were missed.
Try setting the level the Level.TRACE. Does Trace logging work after
that?
Jake
At 04:01 PM 9/16/2006, you wrote:
>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,"Controller logs"));
>BasicConfigurator.configure();
>logger.setLevel(Level.ALL);
>logger.info("controller initialized ");
>
>All the loggings are showing except the trace level !!
>I just used logger.debug instead and it worked fine.
>
>
>Jacob Kjome wrote:
>
>> 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 ??
>> >
>>
>> Theoretically, that should work. However, when do you call it?
>> Usually, one configures Log4j using a properties or XML config
file. I
>> would avoid programatically modifying the configuration except in
>> cases where you have an application specifically used for performing
>> runtime configuration changes, such as LogWeb.
>>
>> In any case, if you make the setLevel() call above before you log,
you
>> should see trace messages. If you don't, it's probably a bug. Please
>> confirm and if this is a bug, I recommend you report it to Bugzilla.
>>
>> BTW, what version of Log4j are you using?
>>
>> Jake
>>
>> >
>> >James Stauffer wrote:
>> >
>> >> 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, 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 find tutorials or hints on how to start using it.
>> >>> Any Idea's ??
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >>> For additional commands, e-mail:
[EMAIL PROTECTED]
>> >>>
>> >>>
>> >>
>> >>
>> >
>> >
>>
>---------------------------------------------------------------------
>> >To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
