it's not %-X{something} it's just %X{something}
why is the '-' in there?
Paul
On 14/12/2005, at 5:35 PM, Sriram Venkatasubramanian wrote:
Hi ,
This is my log4j.xml . I am using logger namely -
'ACPTORD_CTRLR' and
associated appender namely ' ACPTORDER_CONTROLLER ' which has the
patte
Hi ,
This is my log4j.xml . I am using logger namely - 'ACPTORD_CTRLR' and
associated appender namely ' ACPTORDER_CONTROLLER ' which has the
pattern
%-X{MessageJSP} .
Despite this settings , no values from MDC is visible
Regards,
Sriram V
http://jakarta.apache.org/log4j
At 12:16 PM 12/13/2005 -0800, you wrote:
>I'm trying to upgrade to log4j-1.3alpha-7, but not seeing what I would
>expect...which is hopefully user error.
>
>First, I thought I could replace my call to
>DOMConfigurator.configureAndWatch(,
>);
>
>With:
>
>JoranConfigurator joran = new JoranConfigura
Dirk Ooms wrote:
And what about the log4j.dtd which is still in the 1.3alpha6 distribution? Has
it any value?
Some, but it would only catch a small set of errors (misspelling
appender for example), but would not catch bad class names, bad file
values, missing attributes, etc.
--
You forgot:
Or
(e) Don't use log4j to inform end users of error conditions
If you really want to, you could gather events in memory using
org.apache.log4j.varia.ListAppender, iterate over those and present them to the
end user (likely after applying a PatternLayout to each event).
Scott
---
If I was writing an app with an end user then I would do the following:
1) Implement file - based logging so that I could use it for
debugging and troubleshooting purposes.
2) I would not use log4j to provide feedback to the user but
would rather simply trap the error in the appli
It's common in applications which have an end user.
JSP's are running in a web browser, so there is a need to tell the user when
an error occurs that prevents the page from loading or displaying correctly.
I expect that:
(a) Everyone simply resends the same message (or variation of it) to the
Actually, I think that logging to the screen would *NOT* be a common
need. I use logging to a file because I have a large multi - threaded
application, and I use this information for tracability and debugging.
Much of this information would not be shown to the user (and would not
make much sense ev
Thanks for the reply Phillip,
So, it sounds like log4j can not log to a screen unless you create your own
subclass of the ConsoleAppender.
Is it me, or does that not just sound weird? Is there a reason why this
rather common need does not already exist in log4j as a ScreenAppender?
How do you o
I assume that your application has a logger configured and is using the
console appender. If so then you need to create your own appender by
subclassing (look in the log4j javadoc for the correct class to use).
You would then update your config file to add your appender to the
logger. Any messages
post your log4j configuration file, this will help a lot..
On 13/12/2005, at 11:04 PM, Sriram Venkatasubramanian wrote:
With RollingFileAppender , I am not getting any log - MDC keys. ( I
have given the pattern %X{Key}...
Any idea ?
-Original Message-
From: Paul Smith [mailto:[EMAIL
What do I need to do to set up an Appender to log to the screen not the
console?
The equivalent of out.print in a JSP file instead of System.out.print
I need to let the user know when an error occurs and logging error messages
to a console does not do it. I'd think a common task would be to send
I just tried a linux box and windows(cygwin). Neither work, so I am blaming
it on my company's firewall...
Thanks for the help.
On 12/13/05, Scott Deboy <[EMAIL PROTECTED]> wrote:
>
> It Worked for me.
>
> Maybe you have some kind of subversion client problem (assuming you can
> get to the http
It Worked for me.
Maybe you have some kind of subversion client problem (assuming you can get to
the http url in the command from a browser).
-Original Message-
From: Mark [mailto:[EMAIL PROTECTED]
Sent: Tue 12/13/2005 12:30 PM
To: Log4J Users List
Subject: Re: svn problems
nope, that
nope, that did not work either.
On 12/13/05, Scott Deboy <[EMAIL PROTECTED]> wrote:
>
> Try this command:
>
> svn co http://svn.apache.org/repos/asf/logging/chainsaw/trunk chainsaw
>
>
> -Original Message-
> From: Mark [mailto:[EMAIL PROTECTED]
> Sent: Tue 12/13/2005 11:49 AM
> To: Log4J U
I'm trying to upgrade to log4j-1.3alpha-7, but not seeing what I would
expect...which is hopefully user error.
First, I thought I could replace my call to
DOMConfigurator.configureAndWatch(,
);
With:
JoranConfigurator joran = new JoranConfigurator();
joran.doConfigure(,
LogManager.getLoggerRepos
Try this command:
svn co http://svn.apache.org/repos/asf/logging/chainsaw/trunk chainsaw
-Original Message-
From: Mark [mailto:[EMAIL PROTECTED]
Sent: Tue 12/13/2005 11:49 AM
To: Log4J Users List
Subject: svn problems
I am trying to check out chainsaw, and am having problems. I am usi
I am trying to check out chainsaw, and am having problems. I am using
cygwin and get the following errors:
bash-3.00$ svn co
http://svn.apache.org/repos/asf/logging/chainsaw/trunklogging-chainsaw
svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
svn: REPORT of '/repos/asf/!svn/vcc/defau
Quoting Steve Pringle <[EMAIL PROTECTED]>:
> Hi All,
>
> We're using 1.3 and scheduled to go into production with our application in
> 3 months. We're using 1.3 minimally, nothing fancy. Do you think we should
> switch to 1.2.13, or stay with 1.3?
If you are doing "nothing fancy", I would recom
Hi All,
We're using 1.3 and scheduled to go into production with our application in
3 months. We're using 1.3 minimally, nothing fancy. Do you think we should
switch to 1.2.13, or stay with 1.3? If we stay with 1.3 is there a way to
silence all the default output (sample below)?
Many thanks,
With RollingFileAppender , I am not getting any log - MDC keys. ( I
have given the pattern %X{Key}...
Any idea ?
-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Monday, December 12, 2005 2:44 AM
To: Log4J Users List
Subject: Re: How to carry fwd log messages from mul
Hi,
we need a much smaller version of log4j because of the package size
we plan to distribute.
What is the absolute necessary core of log4j for basic logging
functions?
What can be stripped from it?
-
To unsubscribe, e-ma
And what about the log4j.dtd which is still in the 1.3alpha6 distribution? Has
it any value?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
23 matches
Mail list logo
