Hi,
We have a problem with our application that uses Log4j. All of a sudden
it stops logging INFO level and only keeps on logging DEBUG level. If I
restart the application it works fine for a while then it stops.
We are using Log4J version 1.2.8 and Java 1.4.
We initialize Log4J with a property
Thank you developers for adding trace. But it isn't "readily available" from
what I can tell so far, which my question specified. Regarding what
developers have decided to do or not do, did it ever occur to you that the
log4j users list would be a good place to reveal that trace is added even to
you shouldn't modify Log4j to add new levels. It's not optimal in general
to modify Log4j because it will make it more difficult to upgrade as new
releases occur.
To add levels extend the Level class, and specify your class in your config
XML, for example:
You have a good point but since this the (infamous) trace level we're
talking about isn't it ok? I fully expect to be able to unplug my
trace-enabled jar and plug in the new logj4 1.3 jar when it is available for
production, if I understand correctly that Logger.trace() and
Logger.isTraceEnable
Does this have anything to do with log4j?
On Apr 1, 2005 10:10 PM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> i need to load a bunch of image files located outside my exploded war
> file. for example, say that the images live here
>
> |---c:\myimages
> |---\app
> |-\p
Hallo,
I'm writing a client-server application where the client sends a request to
the server and the server starts a complex process. This process has to
generate a protocol that can be stored in a database or send to an email
address. I would like to generate this protocol with log4j but I don't
You may find that creating a logger per user would work for you.
Logger logger = Logger.getLogger(username + "." + getClass().getName());
On Apr 4, 2005 7:35 AM, Weseloh, Markus <[EMAIL PROTECTED]> wrote:
> Hallo,
>
> I'm writing a client-server application where the client sends a request to
> t
That is strange. Have you already tried turning on log4j debug output
to see if somebody's resetting or re-reading the configuration that you
don't know about?
Todd.
> -Original Message-
> From: Henrik Engert [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 04, 2005 3:30 AM
> To: log4j
On Sun, 3 Apr 2005, Andy McBride wrote:
| You don't need to look at CVS to find what you are looking for.
|
| A search of the log4j-dev mailing list would have revealed many posts over
| the past year which answered your question. Perhaps you should look there
| before making remarks regarding wh
My working modification for adding a native trace level to log4j adds 18
non-comment lines to Category, 3 to Level, 1 to Priority. In other words, it
is a simple little 22 line mod. The committers of log4j voted to include
trace, when? About a year ago? Two have corrected me about my technically
Likelihood of this going in as a new 1.2.x version = 1 / (harsh tone of
your emails)^2
We (at least I) want to focus on 1.3.x. You have the power and license
to create your own version of log4j with TRACE embedded, or extended.
Go for it. By releasing another 1.2.x series with TRACE added we
Sorry about the harsh tone.
- Original Message -
From: "Paul Smith" <[EMAIL PROTECTED]>
Newsgroups: gmane.comp.jakarta.log4j.user
Sent: Monday, April 04, 2005 10:54 PM
Subject: Re: log4j trace enabled version
Likelihood of this going in as a new 1.2.x version = 1 / (harsh tone of
your e
I think we found the problem.
We have bunch of threads running and sometimes we don't want to log things like
passwords etc. so we set the loglevel to WARN when these calls to the database
comes (We actually don't encrypt passwords which is strange, but it is not me
who makes those decissions)
13 matches
Mail list logo
