Well, they come in the same tab.
Anyway removing the logger as Scott suggested, everything is perfect now!
Thanks to all of you for your help
ciao
Giordano
-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Wed 2/13/2008 9:46 PM
To: Log4J Users List
Subject: Re: debug me
ok, well those appear in a separate tab don't they? How are they
getting mixed in with other log messages ?
Paul
On 14/02/2008, at 12:52 PM, Cerizza, Giordano wrote:
Hi Paul,
what I'm talking about are the DEBUG messages coming from the Root
Logger (i.e. org.apache.log4j.chaisaw). This log
This should work:
Add this to your chainsaw receiver xml config:
It will disable all log4j logging (you may want to set this to warn or
error instead of off)
Scott Deboy
Principal Engineer
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Office: 503.224.74
Hi Paul,
what I'm talking about are the DEBUG messages coming from the Root Logger (i.e.
org.apache.log4j.chaisaw). This logger
is the default one that it is loaded when launching Chainsaw and I need to get
rid of these messages.
Can you give me a hint? I looked around but I didn't find any solu
I am pretty new to log4j and have a question that should be easy. I am using
log4j in a web (java servlets) environment.
1) How do I pass in variables? I have an app that uses the JDBCAppender
and would like to pass in the connection values. Is there an easy way to do
this? These values coul
what sort of debug messages are you seeing here?
Paul
On 14/02/2008, at 5:02 AM, Cerizza, Giordano wrote:
Hi all,
I'm working at a complex structure with different supervisors report
error messages
following a certain hierarchy. When launching Chainsaw there are
many default debug
messages
Glad you found it :-)
Lesson learned: compiler classloader behavior is different than runtime
classloader behavior. I wonder if this difference in behavior is intentional
or accidental? Anyone know if there's a Java spec that defines this?
Jake
On Wed, 13 Feb 2008 09:06:46 -0800
"Eric Ko
Hi all,
I'm working at a complex structure with different supervisors report error
messages
following a certain hierarchy. When launching Chainsaw there are many default
debug
messages that complicate the error monitoring and I would like to remove them.
I have this file where I configured ever
Problem solved!
Thanks Jake, you got me thinking I found an earlier release of log4j in
my classpath. It seems when I upgraded to log4j 1.2.15 recently it got
sent to the end of my classpath without me noticing that. The older
log4j JAR is included from another project my main project is dependent
On Wed, 13 Feb 2008 16:51:15 +0100
Martyn Hiemstra <[EMAIL PROTECTED]> wrote:
It is very simple. When you use log4j.rootLogger=debug you must ask
yourself, how is log4j suppost to know which appender to use?
For each logger you have to indicate which appender to use so use this
instead.
log4
It is very simple. When you use log4j.rootLogger=debug you must ask
yourself, how is log4j suppost to know which appender to use?
For each logger you have to indicate which appender to use so use this
instead.
log4j.rootLogger=debug, stdout
Then it should work.
Martyn
Hi folks -
I'm frust
Try running outside Eclipse where you have full control over the environment.
Eclipse is a complex environment and you are almost certainly missing
something. I think we can both agree that if Log4j-1.2.15 were in the
classpath properly, you wouldn't be getting a NoSuchMethodError because
trac
I don't use a properties file to config so I'm not 100% sure but that
is a common thing so a little search should turn up the answer.
On Feb 13, 2008 9:43 AM, James Depaul <[EMAIL PROTECTED]> wrote:
> >>If you add "-Dlog4j.debug" to the command line log4j will print out
> info about how it is bein
>>If you add "-Dlog4j.debug" to the command line log4j will print out
info about how it is being configured.<<
Right... we're getting closer! Using your suggestion I was able to find
the proper place for my file and now I know when it's using it - finally!
so thanks
>>Also, it appears that you
asynchronous logging is basically "fire and forget". asynchronous
means it is not blocking on the submission of the log message.
JMSAppender is definitely for real time use - you can receive the
messages from the jms server with very little latency, but if there are
communications bottlenecks
If you add "-Dlog4j.debug" to the command line log4j will print out
info about how it is being configured.
Also, it appears that you haven't attached the appender to any logger.
On Feb 13, 2008 9:01 AM, James Depaul <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi folks -
>
> I'm frustrated in trying to cont
Put the log4j.properties file in the root of the classpath and it should
be found.
Hi folks -
I'm frustrated in trying to control the run-time configuration of Log4j in
my standalone application. I have log4j-1.2.13.jar in my classpath. I
have a log4j.properties file configured as shown below
Hi folks -
I'm frustrated in trying to control the run-time configuration of Log4j in
my standalone application. I have log4j-1.2.13.jar in my classpath. I
have a log4j.properties file configured as shown below. It seems that I
have no idea where to place the property file in my classpath fo
You can use the open source Vigilog tool: http://vigilog.sourceforge.net
It allows you to open your log4j file and then merge that with another one.
You can make the lines of the different log files get a different color if
you want.
regards,
Wim
2008/2/11, palakolanusrinu <[EMAIL PROTECTED]>:
19 matches
Mail list logo
