You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Eqbal <eq...@yahoo.com> on 2007/01/30 00:08:46 UTC
question mark displayed for certain patterns
Hi,
I am fairly new to log4j. I am experiencing a problem
when configuring log4j in Tomcat and use it through
commons logging framework. I get a ? (question mark)
in place of %F and %L patterns. When I run a Java
class file as a standalone using "main", I get the
proper file name and line number. But when I run the
web application I get a question mark in the console.
Anyone can tell me what I am doing wrong?
Thanks.
____________________________________________________________________________________
Don't get soaked. Take a quick peak at the forecast
with the Yahoo! Search weather shortcut.
http://tools.search.yahoo.com/shortcuts/#loc_weather
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: question mark displayed for certain patterns
Posted by Eqbal <eq...@yahoo.com>.
Okay. It was a compile issue as I was using ant and
compiling with no debug flag so it defaulted to off.
The issue is resolved, thanks for your help.
--- Curt Arnold <ca...@apache.org> wrote:
>
> On Jan 29, 2007, at 5:08 PM, Eqbal wrote:
>
> > Hi,
> >
> > I am fairly new to log4j. I am experiencing a
> problem
> > when configuring log4j in Tomcat and use it
> through
> > commons logging framework. I get a ? (question
> mark)
> > in place of %F and %L patterns. When I run a Java
> > class file as a standalone using "main", I get the
> > proper file name and line number. But when I run
> the
> > web application I get a question mark in the
> console.
> > Anyone can tell me what I am doing wrong?
> >
> > Thanks.
> >
>
> That behavior is expected when the calling class is
> compiled without
> debug information (like using javac -g:none).
> Commons logging may
> complicate issues since it would be responsible to
> pass a fully
> qualified category (aka logger) name to log4j
> otherwise all logging
> requests will appear to originate from just a few
> lines in commons
> logging. I'd expect that the problem is likely a
> compilation
> problem, a commons logging problem, or a tomcat
> problem in that order
> and unlikely to be a log4j problem.
>
> If that doesn't resolve the problem, I would suggest
> asking on the
> Tomcat list and specifying what platform and the
> versions of JDK,
> Tomcat, Commons Logging, and log4j are in use.
>
>
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail:
> log4j-user-help@logging.apache.org
>
>
____________________________________________________________________________________
Get your own web address.
Have a HUGE year through Yahoo! Small Business.
http://smallbusiness.yahoo.com/domains/?p=BESTDEAL
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: question mark displayed for certain patterns
Posted by Curt Arnold <ca...@apache.org>.
On Jan 29, 2007, at 5:08 PM, Eqbal wrote:
> Hi,
>
> I am fairly new to log4j. I am experiencing a problem
> when configuring log4j in Tomcat and use it through
> commons logging framework. I get a ? (question mark)
> in place of %F and %L patterns. When I run a Java
> class file as a standalone using "main", I get the
> proper file name and line number. But when I run the
> web application I get a question mark in the console.
> Anyone can tell me what I am doing wrong?
>
> Thanks.
>
That behavior is expected when the calling class is compiled without
debug information (like using javac -g:none). Commons logging may
complicate issues since it would be responsible to pass a fully
qualified category (aka logger) name to log4j otherwise all logging
requests will appear to originate from just a few lines in commons
logging. I'd expect that the problem is likely a compilation
problem, a commons logging problem, or a tomcat problem in that order
and unlikely to be a log4j problem.
If that doesn't resolve the problem, I would suggest asking on the
Tomcat list and specifying what platform and the versions of JDK,
Tomcat, Commons Logging, and log4j are in use.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org