I want to send the log to Syslog so in my properties file i'm using
log4j.appender.A1=org.apache.log4j.net.SyslogAppender
log4j.appender.A1.facility=LOG_LOCAL7
I can't see any log in any of the files
Could you plaese tell me what am i missing here
Shelly
-
Title: 1.04 -> 1.12 port
Hello,
I was sailing along with 1.04, but my "DateFormat" don't seem to work in 1.12. Specifically:
log4j:WARN No such property [dateFormat] in org.apache.log4j.PatternLayout.
... is what I get using the following properties:
log4j.appender.LOGFILE_OUT=org.apac
Hi
Is it a simple oversight that DefaultCategoryFactory is not in Javadocs?
Thanks
Anshul Chhabra
Techone Inc.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
hi,
I am trying to log statements to a JMS queue using the default appender
provided with log4j. I am using log4j1.1.1. I set up the config file as
shown below:
===> Config file start <===
log4j.rootCategory=A1
### JMS Appender
log4j.category.A1=DEBUG
log4j.appe
Hi
If I do not have any new options to be handled in my Category sub-class, do
I still need to implement the OptionHandler interface? Also - I have noticed
that Category class does not implement this interface - how then do the
configurators configure the category class?
Thanks
Anshul Chh
At 12:13 08.06.2001 -0400, you wrote:
>Hi Ceki,
>
>I have a few issues that I would like to discuss, I need some advice
>as I'm doing some refactoring in Turbine and I'm not sure what the
>best practice is vis-à-vis logging in components and/or packages
>that are used by a parent application.
>
>I
Hi,
I'm sorry I have to ask this question again, but I haven't seen the exact
answer to my problem or understood the answers... (?)
I've got the following complaints from log4j :
log4j:ERROR No appenders could be found for category
(worm.gui.TimestamperGUI).
log4j:ERROR Please initialize the log
Hi Ceki,
I have a few issues that I would like to discuss, I need some advice
as I'm doing some refactoring in Turbine and I'm not sure what the
best practice is vis-à-vis logging in components and/or packages
that are used by a parent application.
I have just started some work on refactoring th
Atte A wrote:
>
> >
> >This problem is about multiple clients logging to two different log files.
> >(One log file for errors and one for tracing)
> >
> >I have two categories and each one of them has its own configuration
> >property file. In both of the configuration property file the file appe
[EMAIL PROTECTED] wrote:
>
> this my log4j.xml file. During runtime i removed the 2 outcommenting lines.
> And later, i commented out again these category declarations.
> As i said, log4j recognize the new declarations during runtime, but has a
> problem when i 'remove' them during runtime.
>
>
Hi, again!
Sorry, I have to correct and add some info to my problem statement.
I use remote sockets (SocketAppender) and not file appender, similar to
org.apache.log4j.net.test.SocketMin. Instead of
BasicConfigurator.configure() I call
PropertyConfigurator.configure(propertyConfigurator) once
At 01:24 08.06.2001 -0700, Craig R. McClanahan wrote:
>I think this is really a significant question. How significant a patch
>does it take for someone to legitimately be considered an additional
>"author" of a particular source file? Attribution in a CVS commit should
>always be there -- but i
It should have been attached (at least one person got it) I'll inline it here
-- hopefully Netscrape won't kill the format too badly:
package org.apache.log4j.varia;
import org.apache.log4j.*;
import org.apache.log4j.spi.*;
import org.apache.log4j.PatternLayout;
import org.apache.log4j.helper
Kevein,
Sure. I could replace the earlier class if I had the newer version. :-)
That was the essence of my previous question. Can you post it? Ceki
At 01:22 08.06.2001 -0700, you wrote:
>I'm not sure I understand the question really but it is supposed to be an
>update to the JDBCAppender I've a
OK, that makes sense.
Here are some relevant rules.
0) When reading a new config file, the existing log4j configuration is not reset.
1) See rule 0.
3) Whenever a category element is seen in the config file, then all the existing
appenders for THAT category are closed and then removed from
I'm not sure I understand the question really but it is supposed to be an
update to the JDBCAppender I've already contributed -- so it belongs to
ASF and should replace that earlier class (please could you do that
Ceki?). I haven't mentioned it outside of the Log4J list if that's what
you mean.
Could you provide a snipet of the configuration file indicating the
entries you added and then took out.
Thanks,
- Paul
--
Beware of bugs in the above code. I have
only proved it correct, not tried it.
-Don Knuth
-
To unsubsc
Jamie Tsao wrote:
>
> 1) How do you turn off logging completely in the properties file ?
>
Check the javadoc for the field BasicConfigurator.DISABLE_KEY.
Including a property like
log4j.disable=INFO
will disable everything all INFO and DEBUG messages (and makes them very
efficient to pass
Hi Paul (and the others),
this my log4j.xml file. During runtime i removed the 2 outcommenting lines.
And later, i commented out again these category declarations.
As i said, log4j recognize the new declarations during runtime, but has a
problem when i 'remove' them during runtime.
log4j:ERROR
At 09:04 08.06.2001 +0200, you wrote:
>Dear Ceki,
>
>-Original Message-
>From: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
>Sent: Donnerstag, 7. Juni 2001 19:02
>To: LOG4J Users Mailing List
>Subject: RE: Log4J config file
>
>Thilo,
>
>This is partially true. Any setter method in an appender or
Hi,
Is the new JDBCAppender available to the wider public? Ceki
At 09:12 05.06.2020 -0700, you wrote:
>I spent a lot of time yesterday updating my JDBCAppender.
>Looks like that was appropriate timing.
>
>The new version of my appender has bean-like get/set methods
>(plus the now deprecated set
--- Atte A <[EMAIL PROTECTED]> wrote:
> Hi!
>
> This problem is about multiple clients logging to
> two different log files.
> (One log file for errors and one for tracing)
>
> I have two categories and each one of them has its
> own configuration
> property file. In both of the configuration
--- Atte A <[EMAIL PROTECTED]> wrote:
> Hi!
>
> This problem is about multiple clients logging to
> two different log files.
> (One log file for errors and one for tracing)
>
> I have two categories and each one of them has its
> own configuration
> property file. In both of the configuration
Hi!
This problem is about multiple clients logging to two different log files.
(One log file for errors and one for tracing)
I have two categories and each one of them has its own configuration
property file. In both of the configuration property file the file appender
is stated.
The problem
Dear Ceki,
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
Sent: Donnerstag, 7. Juni 2001 19:02
To: LOG4J Users Mailing List
Subject: RE: Log4J config file
Thilo,
This is partially true. Any setter method in an appender or layout
corresponds to a configurable property. Ho
25 matches
Mail list logo