The log4j team is happy to announce the availability of log4j version
1.3alpha8. It can be downloaded from:
http://logging.apache.org/site/binindex.cgi
This version contains many changes to bring it back to better compatibility
with log4j version 1.2.X, and more changes are planned for the up
Work continues on the next major version of log4j, 1.3. Going forward there
will be monthly builds of 1.3, taking place on the last Wednesday of the
month. More builds may be done as needed.
The current focus of work for 1.3 is to restore most compatibility with
version 1.2.X. These changes
r ?
Thanks :)
If the use of the first in one class and the second in another class
would not produce any diffrence, why isn't there only one use ?
2005/12/22, Mark Womack <[EMAIL PROTECTED]>:
It depends on which package you want to use in your code. If you only
want to reference log
It depends on which package you want to use in your code. If you only
want to reference loggers via commons-logging, use the commons logging
one. If you want to reference loggers via log4j, use the log4j one.
Even though commons-logging can use log4j under the covers, it does
not directly expose
like this:
>
> http://logging.apache.org/log4net/release/manual/configuration.html
>
> http://logging.apache.org/log4net/release/config-examples.html
>
> Examples showing how to use each of the built-in appenders is helpful.
>
> ----- Original Message
> From: Mark Womack &
uld just come as learn/use the code so that would be
> the easiest way to add helpful tidbits.
>
> On 12/20/05, Mark Womack <[EMAIL PROTECTED]> wrote:
> > One of the tasks for the log4j 1.3 release (or even before that) is to
> > create a better documentation set for log4
One of the tasks for the log4j 1.3 release (or even before that) is to
create a better documentation set for log4j. This would be both the
documentation that ships at part of the release and what is available
from the web. I am speaking for myself, but I think most of the
committers agree, that t
You could do the same in a J2EE Filter class and reuse it across all of your
servlets/jsp's without requiring any modification/addition to them.
-Mark
- Original Message -
From: "Paul Smith" <[EMAIL PROTECTED]>
To: "Log4J Users List"
Sent: Monday, December 19, 2005 1:43 PM
Subject: [
The Logging Service project and log4j project are happy to announce the
release of log4j 1.2.13.
Version 1.2.13 contains several bug fixes related to the TRACE level
introduced in version 1.2.12 and a fix in the ConsoleAppender for a bug that
affected logging in JBoss. Please see the HISTORY.
Do you have any actual timing or profiling information that would lead you
to suspect that log4j is causing the problem, or just anecdotal experience?
There is nothing I can think of that changed so much in any of the recent
log4j releases to account for the level of degradation you are describing
The log4j project is proud to announce that the next alpha release of
version 1.3, 1.3alpha7, is now available for download.
http://logging.apache.org/site/binindex.cgi
(mirror sites may need some time to pick up the new distribution)
Enjoy!
-The log4j project
---
Sorry, that would 1.3 *alpha* 7, not beta.
-Mark
On 11/2/05, Mark Womack <[EMAIL PROTECTED]> wrote:
>
> The 1.3beta7 build has been approved for release, I just have to move it
> to the right location. Hopefully the history file will have what you are
> looking for, but I don
The 1.3beta7 build has been approved for release, I just have to move it to
the right location. Hopefully the history file will have what you are
looking for, but I don't know if that is guaranteed.
I don't beleive this bug has been addressed in the new build.
I plan to move the build to the down
Thanks for the suggestion. But what happens when the filewatchdog detects a
subsequent change in the configuration file? Is the file wiped again? Would
it be better to enable the "append" settings on the FileAppender?
There are little issues like this that need to be looked at for the
watchdogs. I
I would need to check, but I think this will be fixed in v1.3.
-Mark
On 10/17/05, Philip Denno <[EMAIL PROTECTED]> wrote:
>
> You could implement a timer in your code to write some data at a
> specified period (say midnight).
>
> I don't think this can be done from log4j configuration.
>
> Cheers
George,
Andy McBride reported the following bug in 1.2.12:
http://issues.apache.org/bugzilla/show_bug.cgi?id=36800
and included a patch. Sounds like it might be the same problem. We'll look
at a 1.2.13 to fix it.
-Mark
On 10/6/05, Harp, George <[EMAIL PROTECTED]> wrote:
>
> I just downloaded
You are right. We should not have removed the api, and reviewing the api
changes we have made is a task for the 1.3 beta. We should look at what is
different and if we want to live with it, put it back, deprecated it, etc.
I believe that, yes, configureAndWatch could be implemented with the
; > not locate the method configureAndWatch in PropertyConfigurator class.
> > Please point me to the exact class.
> >
>
> configureAndWatch() has been removed in Log4j-1.3. It is also not
> recommended
> to use this in Log4j-1.2 either if you are running in a J2EE environment.
>
It would be cool if we could plug Chainsaw into Eclipse. Paul, Scott, how
hard do you think that would be?
-Mark
On 10/4/05, Alan Gutierrez <[EMAIL PROTECTED]> wrote:
>
> * Robert Hedin <[EMAIL PROTECTED]> [2005-10-04 11:03]:
> > Checkout the Ganymede Plugin for Eclipse:
> > http://sourceforge.ne
completely separate trains
> of thought of two entirely different logging issues.
>
> > Any idea when the next release will fix this (no time to build from
> > source)?
> >
>
> I believe that some of the developers are working on getting a new
> release out as we spe
Indeed. It is my task for this evening to do the next 1.3 alpha build. I was
going to do it earlier this week, but my time ran out at the ends of the
various days...
-Mark
On 9/29/05, Jacob Kjome <[EMAIL PROTECTED]> wrote:
>
>
>
> I believe that some of the developers are working on getting a new
Can we assume that you are using the 1.3 alpha version? You will want to add
configuration to set org.apache.log4j to WARN/ERROR or OFF.
hth,
-Mark
On 9/28/05, Rakesh Patel <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have a test set up that logs and also the class under test logs too.
>
> I want to
1) If you are logging to a file, then the machine where the logging is being
performed will need access to the volume. Please be aware that a file
cannot be shared across multiple log4j instances, only one instance can have
the file open at one time in the current implementation. If you do not
I think you will need to add something to your configuration to set '
org.apache.log4j' to WARN/ERROR. This is something we need to look into in
the drive to beta.
hth,
-Mark
On 9/23/05, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
>
> Hello!
>
> How can I turn off the logj4 logs ins Log4J 1.3 a
rsion ;-(
> (http://issues.apache.org/bugzilla/show_bug.cgi?id=35996)
>
> I'll have to wait for 1.2.13...
>
> Nico.
>
>
> Mark Womack a écrit :
>
> > The log4j team is proud to announce the official release of log4j
> 1.2.12!
> >
> > This new versi
The log4j team is proud to announce the official release of log4j 1.2.12!
This new version contains a number of bug fixes, the addition of the much
requested TRACE level, and is compile and runtime compatible with the
earlier JDK's 1.1 and 1.2 (this feature had been inadvertently broken in
ver
I know all the committers have probably been following the discussion on
logging general, but just so everyone knows...we are planning to migrate the
logging services cvs repositories to svn (subversion) this weekend, 9/10.
Converting to svn is an apache-wide initiative and besides it being a
diffe
There is a simple one in the log4j-sandbox. It could use some attention
from a caring soul... :-)
-Mark
> -Original Message-
> From: James Stauffer [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 02, 2005 8:46 AM
> To: Log4J Users List
> Subject: Re: Log4J Control Panel
>
> I think
If you just use log4j, by default it looks for a file named "log4j.xml" or
log4j.properties" in the classpath. If it finds one of them, then it uses
it to configure itself (with the proper configurator).
There are schemes for initializing log4j in a web application if you have a
different name fo
, 2005 2:11 PM
> To: 'Log4J Users List'
> Subject: RE: Log4j, websphere, rad, and log4j.xml location
>
> Wow. Nice. I've used it before and it works.
>
> What should I be using with xml files? :P
>
> -Original Message-
> From: Mark Womack [mailt
You sure that is how you are configuring? PropertyConfigurator cannot
process xml files.
-Mark
> -Original Message-
> From: Schuweiler, Joel J. [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 11, 2005 2:02 PM
> To: log4j-user@logging.apache.org
> Subject: Log4j, websphere, rad, and lo
The log4j 1.2.12rc2 build is available from:
http://cvs.apache.org/dist/logging/log4j/log4j-1.2.12rc2/
This release is a release candidate and not an official, final, stable
release and should be used for review and sanity checking. It contains a
few more bug fixes from the 1.2.12rc1 release.
The log4j team is working towards the official release of v1.2.12 which is
primarily a maintenance release with fixes for some annoying bugs. To this
end, the 1.2.12rc1 build has been created. This is not an official release,
it is a release candidate, and should be treated that way. It is provi
+1. I think this falls into the "making sure 1.3 is as api compatible with
1.2 as we can make it" category. Curt and Jake have done some good things
around this, but we should all review the areas we are familiar with.
In this particular case, we an probably even change the underlying
functional
Nicolas,
Yes. Watchdogs will become more of a first order class/interface and will
come in several implemented flavors: FileWatchdog, URLWatchdog,
SocketWatchdog. Watchdogs are based on the new Plugin structure, and as
such will be configurable from config files. Also, Watchdogs will support
an
What page did you access this bad link from?
> -Original Message-
> From: Allen Kardakaris [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 20, 2005 5:41 AM
> To: log4j-user@logging.apache.org
> Subject: log4j download broken links
>
> The link for the *logging-log4j-1.3alpha-6* [.tar.gz
Well, if CompositeConfiguration supports getting a Properties object to
represent the configuration settings, then you could plug it into the
PropertyConfigurator through doConfigure(Properties, LoggerRepository)
pretty easily. Though there is no way to do automatic, default
configuration (ie a si
You are correct. It is only a file watcher, not a url watcher. v1.3 will
have a much richer set of functionality that can watch a file, url, or a
socket for updated configuration data and it will also support any
Configurator.
-Mark
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailt
- Original Message -
From: "Rodent of Unusual Size" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 13, 2005 3:27 PM
Subject: ApacheCon US 2005: Call for Participaton
-BEGIN PGP SIGNED MESSAGE-
In case you missed the news, ApacheCon US 2005 has been schedul
The assumption here is that you have named your classes and packages in some
coherent, logical, useful fashion, as in:
com.mycompany.package1.classA
com.mycompany.package1.classB
com.mycompany.package2.classC
com.mycompany.package2.classD
If you do this, then this gives you maximum flexibility i
Or the log4net-user email list, sorry.
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tom Regan
> Sent: Tuesday, July 12, 2005 9:37 AM
> To: log4j-user@logging.apache.org
> Subject: getting the log4net appenders at runtime
>
> My root appender writes to a text fi
Tom, I think you want the log4net-dev email list.
-Mark
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tom Regan
> Sent: Tuesday, July 12, 2005 9:37 AM
> To: log4j-user@logging.apache.org
> Subject: getting the log4net appenders at runtime
>
> My root appender w
This is bug 9150 in the log4j bug db, and will be fixed in the upcoming
1.2.12 version. I got the fix together over the weekend, but still working
on a unit test before checking it into cvs.
-Mark
> -Original Message-
> From: James Stauffer [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, Ju
Since it has been brought up in relation to bug #9150, I would like to open
this up to the log4j users.
Please review bugs in the log4j bug database, and if there is a bug that you
would like considered for fixing in the 1.2.12 release, then enter the
phrase "1.2.12 candidate" in the bug comments.
I think we should try to create the directory, not even define an option.
If it fails (because it is not allowed), we could catch the exception, then
write out an error message and one is no worse off then if we never tried in
the first place. This just seems basic to me. Jake had to write too mu
We should do another 1.3 alpha release around the same time we release
1.2.11.
-Mark
> -Original Message-
> From: Scott Deboy [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 14, 2005 6:34 PM
> To: Log4J Users List
> Subject: RE: CustomSQLDBReceiver
>
> CustomSQLDBReceiver was left out of
Bruno,
Is this the change you are talking about in JBoss 4.0.2?
http://jira.jboss.com/jira/browse/JBAS-1691
Looks like they decided to default to child-first classloading with options
to allow for parent-first delegation for specified packages.
-Mark
> -Original Message-
> From: Bruno
#x27;t have wayward MDC info sticking around in the thread local
> > getting reported later in some unrelated request context. I would do
> that
> > in a final block if possible to guarantee it gets removed.
> >
> > hth,
> > -Mark
> >
> > > -Ori
ject: Re: [INFO] Log4j Release Overview
>
> Hi,
>
> I would suggest, if possible, more frequent snapshot/alpha builds of
> 1.3 branch.
>
> thanks
> Ricardo
>
> Mark Womack wrote:
>
> > The log4j committers recently voted to accept the following releas
ion id, and any other info from the session that i
> choose so that i can sort my logs per session.
>
> i'll check out the sandbox.
>
> On 5/18/05, Mark Womack <[EMAIL PROTECTED]> wrote:
> >
> > If I understand correctly, you want to set session/user
1.2.8 and 1.2.12 versions?, are we going
> back on version numbers?. I am confused
>
> srini
>
>
> -Original Message-
> From: Mark Womack [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 18, 2005 12:34 PM
> To: log4j-user@logging.apache.org
> Subjec
If I understand correctly, you want to set session/user specific information
per request? Since the MDC is stored in ThreadLocal, I think you will need
to use a servlet filter to set and unset the MDC for each request. And yes,
how threads are assigned to handle requests, etc is very container
The log4j committers recently voted to accept the following release schedule
for future versions of log4j:
1) Release 1.2.11 with JMS build fix. Timeframe is immediate, within the
next week.
We should have a build candidate by this Monday, with the release before the
end of the week. Andy Mc
Testing. For some reason my messages to log4j mailing lists are taking a
while to post.
-Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Yeah, but you are playing roulette with determining which application
installs the respository selector and assuming they are all trying to
install the same one. It really should be better supported at the container
level. Have you gotten the JNDI context selector to work in JBoss? I tried
some
JBoss, by current design, only provides for one logging context (ie
LoggerRepository). On top of that, the JBoss log4j.xml also sets up a
special CONSOLE appender that maps the System.out and System.err streams.
If you do any kind of configuration after JBoss starts up that affects the
console ap
JBoss, by current design, only provides for one logging context (ie
LoggerRepository). On top of that, the JBoss log4j.xml also sets up a
special CONSOLE appender that maps the System.out and System.err streams.
If you do any kind of configuration after JBoss starts up that affects the
console ap
So noted. Would anyone be interested in logging a bug?
Also, we are in the process of determining the release schedule for v1.3
going forward. Nothing is solid yet, but we are looking at a release of
v1.3 before the end of the year, with a beta release around late summer.
-Mark
> -Original
It is unclear to me what your singleton is providing over the basic Logger
class besides the Util.freeze() convenience.
If you want to do something for a monitor, look at using Chainsaw as a
client to "connect" to the remote services as needed.
-Mark
-Original Message-
From: rubble [mail
59 matches
Mail list logo
