On May 19, 2008, at 10:22 AM, Jess Holle wrote:
Jess Holle wrote:
Thanks.
I'm also starting to ponder whether there's a mostly compatible way
to reduce locking in AppenderSkeleton and WriterAppender.
For instance, we could add a special Layout interface that would
allow the String to be
On May 16, 2008, at 9:01 AM, Jess Holle wrote:
I grabbed the 1.2.15 sources, built them, and then tried to run the
regression tests -- in preparation for making changes and then
verifying no tests fail.
Unfortunately, I get the following failure:
Minimum:
[junit] Running org.apache.log
I sorry that I haven't had time to look at your proposal but hope to
on Monday.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Components: Layouts
Reporter: Curt Arnold
In http://marc.info/?l=log4j-user&m=120898200413495&w=2, Robert Pepersack
essentially asks for a method of overriding the use of
Exception.printStackTrace() to capture the stack trace of the associated
exception. This can partially be
I've logged a Infrastructure request (https://issues.apache.org/jira/browse/INFRA-1559
) to create a new JIRA project for log4j 2.0 development. Initially,
it would be used to gather requirements and document the development
decisions. I would not expect the request to be controversial.
H
On Feb 20, 2008, at 4:14 AM, Stefan Fleiter wrote:
Hello Curt,
[Offer to provide TimedDailyRollingFileAppender or
CronExpressionFileAppender]
Thanks a lot for your answers and four your Pointing to the
companions.
I do not think that this is the right place for such a
functionality, th
On Feb 10, 2008, at 8:35 PM, Katherine Hale wrote:
Curt -
Thanks for the fly-by-night introduction. This is what I was
thinking in more detail. Again I know this is Java 5, so this would
be for Log4J 2.0, although perhaps something comparable could be
devised for the current Log4J. I'll
On Feb 9, 2008, at 11:05 AM, Katherine Hale wrote:
Hello! I have checked out the sandbox via SVN, I'm familiar with ANT
& test cases and all that good stuff. The readme said I should post
here to contribute. If anyone wants to send me information about
exactly where to submit a contributio
On Feb 6, 2008, at 9:32 AM, Dominique Laurent wrote:
Hi,
Just to let you know that the manifest (MANIFEST.MF) in
log4j-1.2.15.jar uses:
Name: org.apache.log4j
instead of
Name: org/apache/log4j/
Note the dot '.' instead of the slash '/'.
It means that the following piece of code:
On Jan 28, 2008, at 7:54 PM, Jacob Kjome wrote:
I think it would be better to avoid adding a dependency to pick up
the CronExpression since that would likely force the Policy off
into a yet another companion since we would not want to force
everyone who uses extras to pick up quartz.
Why
On Jan 28, 2008, at 10:30 AM, Stefan Fleiter wrote:
Hello,
we think that Log4j is missing a possibility to rollover at a fixed
time of the day
and have developed a TimedDailyRollingFileAppender class which does
this.
We would like to contribute the solution to the log4j project.
If ther
On Jan 20, 2008, at 3:42 PM, Manish Marathe wrote:
Hello All,
Currently the Appender, DailyRollingFileAppender, rolls over the log
file as per the "datePattern" set in the configuration file,
although the rolled-over files never get deleted unlike if we use
RollingFileAppender but in cas
On Jan 17, 2008, at 3:28 PM, Paul Smith wrote:
Just returned to work after the birth of our first child (boy,
William, everyone's healthy). Since just before Xmas I've moved
house, had a decent car accident and had a baby, so I've been quite
distracted. Apologies for disappearing!
chee
On Dec 9, 2007, at 11:46 AM, Paul Duffy wrote:
The sequence number that was implemented in log4j 1.3 was
problematic on several fronts. In the implementation in the last
release, the same sequence number could be repeated since it wasn't
guarded with a synchronization block. I believ
On Dec 9, 2007, at 11:55 AM, Jess Holle wrote:
Paul Duffy wrote:
For the big picture:
log4j 2.0 intends to target Java 5 and later and follow modern
concurrency best practices, but currently it is only a concept and
some very early experimental code. While I'd love to flesh out
the fra
On Dec 7, 2007, at 1:12 PM, Paul Duffy wrote:
Folks,
Scenario is app running on multi core hardware at high clock rates.
Millisecond time resolution for LoggingEvent is not going to cut
it. Need a monotonically increasing sequence number in the
LoggingEvent to distinguish order for eve
On Dec 4, 2007, at 3:12 AM, tststs wrote:
I am using log4j for logging. I am working on a huge application and
there
would be lots of logs each day. Thereby it is requried that the log
files be
stored and renamed each day. The date is appended to the log file
and that
day's log file is
On Nov 15, 2007, at 3:35 PM, Paul Smith wrote:
actually I've found a problem with the commit.
If ZeroconfSocketHubAppender class calls super.activateOptions()
which then creates the SocketServer, the actual creation of the
ServerSocket is done by another thread (see the SocketMonitor
con
On Nov 15, 2007, at 2:02 PM, Scott Deboy wrote:
Can we get the maven dependencies corrected so we don't break maven
and
others?
See
http://www.1060.org/blogxter/entry?
publicid=9FDCA6751DE11295AD0049F5DB17
F461&token=
Its fixed in the subversion repo. All that would be necessary is to
I've logged a bug report (43874) for the SocketHubAppender
enhancement and committed the createServerSocket() patch and updated
the changes.xml for 1.2.16. I'm not saying that has to be the final
approach, but I think there is general agreement that we can do
something minimal and safe in
On Nov 15, 2007, at 4:36 AM, Paul Smith wrote:
Ok, i'm a bit tired, so I ended up just going simple and pretty
much following Curt's idea, see below. Thoughts?
Index: src/main/java/org/apache/log4j/net/SocketHubAppender.java
On Nov 13, 2007, at 8:43 AM, Mak, Howard wrote:
Hello,
I would like to suggest the following changes to
DailyRollingFileAppender. If this is not the appropriate forum for
this email, please direct me to the proper channels as I'm new to
Log4j. ;)
Feature:
- Allow date p
On Nov 7, 2007, at 10:22 PM, Will Sargent wrote:
Curt Arnold wrote:
I did take a scan of the code, it does appear to conform to ASF
source header policy (http://www.apache.org/legal/src-headers.html).
It also stated that it was based on log4j 1.3. log4j 1.3
development has been
On Nov 7, 2007, at 1:55 AM, Curt Arnold wrote:
Okay, I'm about ready to fall over, but I looked at zeroconf and
see your motivation for moving the binding onto the main thread so
you continue the set up in
ZeroConfSocketHubAppender.activateOptions. However instead of
changin
On Nov 5, 2007, at 6:55 PM, Paul Smith wrote:
I'd like to propose a change to SocketHubAppender code to allow it
automatically choose a free port on the local host if the Port
property is configured with 0.
This will allow the Zeroconf module to be more useful, and allow
simpler configur
On Nov 5, 2007, at 2:55 PM, Will Sargent wrote:
Hi all,
I have a layered configurator that I'd like to contribute to log4j,
either as a companion or in the core code. I've read through the
wiki on
http://wiki.apache.org/logging-log4j/ContributingCode
and a description and zip of the co
ApacheCON US (http://www.us.apachecon.com/) is less than two weeks
away. I'm not going this year (at least at the moment), but have
enjoyed the last 3 ApacheCON US's.
The monthly board meeting is in the middle of ApacheCON and Logging
Services quarterly report is due for the meeting. In t
On Oct 30, 2007, at 3:01 PM, Simon Park wrote:
Hi,
I've posted code (Apache license, Log4J coding standards) that I
hope will offer an alternative to the standard Log4J
AsyncAppender. The design intention is to facilitate reduced
blocking for logging operations, thereby allowing higher
As far as I recall, the current JMX code was added in one commit long
time ago by a single developer with no preceding discussion about use
cases, design strategies, etc, little or no feedback after it was
introduced and no unit tests. Since it has been present in log4j
releases, the proje
On Oct 13, 2007, at 5:57 PM, Lilianne E. Blaze wrote:
Hello,
I wrote a simple patch which makes property resolving pluggable. It
can
be used, for example, to check JNDI env-entries in addition to system
properties, or to specify the priority in which they are resolved
(allowing or disallowin
On Oct 12, 2007, at 8:40 PM, Lilianne E. Blaze wrote:
Hello,
Is DOMConfigurator.props (line 127) actually used anywhere? It looks
like it never gets initialized.
Greetings, Lilianne E. Blaze
There is an open bug involving property substitution (http://
issues.apache.org/bugzilla/show_bug.c
On Oct 11, 2007, at 11:20 PM, Lilianne E. Blaze wrote:
Looks like it's not enough. Is there any simple way to just tell maven
to skip the tests? There is an option in NB that says just that,
but it
doesn't work. Probably having something to do with three different
build
scripts.
For now I
On Oct 11, 2007, at 7:28 PM, Lilianne E. Blaze wrote:
Hello,
I had major problems getting Log4j compiled on Netbeans 6.0 / WinXP.
It was constantly bitching about lack of NTEventLogAppender.dll, even
when I did everything I could think of to turn off the tests during
compilation.
The patch be
The Logging Services project is pleased to announce the release of
Apache log4j 1.2.15.
Apache log4j 1.2.15 is a maintenance release of log4j 1.2 (http://
logging.apache.org/log4j/1.2).
The list of fixed issues is available at http://logging.apache.org/
log4j/1.2/changes-report.html.
The rele
On Aug 31, 2007, at 9:23 PM, Scott Deboy wrote:
It looks like Chainsaw is still at:
http://logging.apache.org/chainsaw/download.html
That is expected. The "new" Maven generated chainsaw content is
below http://logging.apache.org/chainsaw.
On http://logging.apache.org/chainsaw/download.ht
On Aug 30, 2007, at 5:47 PM, Scott Deboy wrote:
Great!
One thing I notice: the path to Chainsaw is a bit different now.
That's
not a bad thing, but could we redirect the old site & Chainsaw
webstart
link to the new locations?
Scott Deboy
Chainsaw downloads should be fixed now. The
FYI: There has been a posting with the board's feedback on the issue
of signing Java jars (http://marc.info/?l=incubator-
general&m=118845647414234&w=2).
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-
On Aug 30, 2007, at 5:47 PM, Scott Deboy wrote:
Great!
One thing I notice: the path to Chainsaw is a bit different now.
That's
not a bad thing, but could we redirect the old site & Chainsaw
webstart
link to the new locations?
It wasn't intentional, but looks like I just overlooked the
PluginConfiguration was getting a little stale relative to 1.2.15's
DOMConfigurator. I could have updated PluginConfigurator or added a
dependency to extras and replaced PluginConfigurator with
org.apache.log4j.extras.DOMConfigurator, however the value of using
component with pre-1.2.15 ve
Vote called 2007-08-25 at 9:58 PM CDT, vote concluded 2007-08-29,
11:35 CDT.
+1 from Curt Arnold, Scott Deboy, Paul Smith
+0 from Jacob Kjome
all PMC members, no other votes.
Proceeding to place releases on distribution servers. Will update
web site tomorrow after releases have had time
This is a vote on publishing the following artifacts as log4j 1.2.15
and log4j-extras 1.0:
http://people.apache.org/builds/logging/log4j/1.2.15/apache-
log4j-1.2.15_rc6.tar.gz (also .zip)
http://people.apache.org/builds/logging/log4j/companions/extras/1.0/
apache-log4j-extras-1.0_rc5.tar.gz
log4j 1.2.15 rc6 is available for review at http://people.apache.org/
builds/logging/log4j/1.2.15. rc5 was abandoned during preparation.
I believe this is as good as it is going to get. Corresponding jar
files are also available in the staging Maven repo at http://
people.apache.org/builds
I added javamail and activation to the Gump descriptor in my local
copy days ago but forgot to commit it. Hopefully the next Gump run
will be clean.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
Started the process before the mention of the XSLTLayout test
failures on Windows. I've posted rc2 at http://people.apache.org/
builds/logging/log4j/companions/extras/1.0. Jars are also available
in the staging Maven repo at http://people.apache.org/builds/logging/
repo. Any comments are a
On Aug 23, 2007, at 12:02 PM, Scott Deboy wrote:
Basically, the reason behind the remotehost and application properties
in 1.3 is to provide the user with an easy way to distinguish between
various event sources (running on one or more machines).
For the 'application' property, users COULD use
This change should eliminate the need to provide logger.dtd with no
degradation of behavior (actually should be a tad faster).
On Aug 23, 2007, at 12:07 PM, [EMAIL PROTECTED] wrote:
Author: carnold
Date: Thu Aug 23 10:06:59 2007
New Revision: 569073
URL: http://svn.apache.org/viewvc?rev=569
On Aug 23, 2007, at 8:38 AM, [EMAIL PROTECTED] wrote:
Author: sdeboy
Date: Thu Aug 23 06:38:12 2007
New Revision: 568980
URL: http://svn.apache.org/viewvc?rev=568980&view=rev
Log:
Moved Constants out of component & extras
Added application property & remote host now available as
properties v
On Aug 23, 2007, at 12:19 AM, Scott Deboy wrote:
Looks good -
A few things:
1. helpers/Constants.java is in both extras & component. I looked
in helpers for other dups, but didn't see any - not sure if we have
other dups..
Without Constants in extras, TimestampEqualsRule and
Timest
On Aug 23, 2007, at 1:59 AM, Paul Smith wrote:
Right now, with svn updated in log4j/trunk, a 'mvn clean install'
fails:
...
[junit] Testcase: testProblemCharacters took 0.016 sec
[junit] Testcase: testNDCWithCDATA took 0.008 sec
[junit] FAILED
[junit] expected:<...> but
On Aug 23, 2007, at 12:22 AM, Scott Deboy wrote:
It looks like my most recent commit isn't sufficient. I'll see if
I can improve it before you cut a RC.
-Original Message-
From: Scott Deboy [mailto:[EMAIL PROTECTED]
Sent: Wed 8/22/2007 10:19 PM
To: Log4J Developers List
Subject: R
I don't know what possessed me, but I think I've reviewed all the
open log4j bugs today and fixed several of them. I didn't see any of
the other ones that seemed ready for log4j 1.2.15. The big clusters
of bugs seemed to be:
1) Tomcat shutdown/restart breaking what were intended to be
On Aug 21, 2007, at 2:50 PM, Scott Deboy wrote:
The ability to run the latest version of Chainsaw via Web Start is a
service our users have come to expect and value.
Taking away this service due to deployment/infrastructure issues isn't
an answer. If we need to, let's talk to infra@ and figur
On Aug 21, 2007, at 7:12 PM, Scott Deboy wrote:
I thought it would be a good idea to put it in the same location as
log4j.dtd.
Scott
The file looks identical to http://java.sun.com/dtd/logger.dtd, but
with the copyright notice removed. Is it essential to do a
validating parse of the JU
On Aug 8, 2007, at 11:41 AM, Curt Arnold wrote:
On Aug 7, 2007, at 1:49 AM, [EMAIL PROTECTED] wrote:
Author: sdeboy
Date: Mon Aug 6 23:49:24 2007
New Revision: 563405
URL: http://svn.apache.org/viewvc?view=rev&rev=563405
Log:
- added logger.dtd to support processing of java.util.log
On Aug 20, 2007, at 10:56 PM, Paul Smith wrote:
I had a crack at working out how to create 2 separate artifacts for
the log4j-receivers module, 1 for the primary artifact (as current)
and one a chainsaw-specific artifact that excludes the JMS, DB and
VFS-based Receivers. This is needed fo
On Aug 21, 2007, at 4:28 AM, Paul Smith wrote:
Do you think it's worth publishing some of the latest log4j-*
snapshots to the snapshot repo?
http://people.apache.org/repo/m2-snapshot-repository/
Paul
Artifacts that are intended or expected to be used outside of the
development team are
The ASF board meeting that was originally scheduled for day was
pushed back to the 29th. We've had increasing traffic on the user's
list about the extras companion and new users jumping into log4j 1.3
since it appears to be the latest and greatest. I think it would be
good if we could get
On Aug 12, 2007, at 7:42 PM, Scott Deboy wrote:
Do we need this class? Can we remove it/other slf4j references?
Sorry, I don't see ULogger or any slf4j references on the log4j 1.2
branch. I haven't moved the branches around as discussed last week,
so trunk is still log4j 1.3.
The log
On Aug 7, 2007, at 5:23 PM, Paul Smith wrote:
On 08/08/2007, at 7:22 AM, Curt Arnold wrote:
The log4j 1.2 layout can produce non well formed content for some
atypical content (a message with an embedded -->, threads
containing & or >, etc). Plus it does not output MDC conten
On Aug 7, 2007, at 1:49 AM, [EMAIL PROTECTED] wrote:
Author: sdeboy
Date: Mon Aug 6 23:49:24 2007
New Revision: 563405
URL: http://svn.apache.org/viewvc?view=rev&rev=563405
Log:
- added logger.dtd to support processing of java.util.logging dtd-
formatted events
- added locationInfo support
Log4j/trunk is no longer the main development branch. Renaming it
log4j/branches/v1_3-branch would eliminate mistaking it for the latest
and greatest. It may disrupt someone (we'd address gump as part of
the change), but I think they'd eventually have to deal with it.
I'm not sure if we s
The log4j 1.2 layout can produce non well formed content for some
atypical content (a message with an embedded -->, threads containing &
or >, etc). Plus it does not output MDC content (log4j 1.3 does, but
shares the other shortcomings). I've been tempted to overhaul it but
am hesitant to
On Jul 27, 2007, at 2:47 PM, Marcos Sanz/Denic wrote:
All,
I never got an answer to my mail from last week. Here is a repost.
Best,
Marcos
Thanks for the contribution. Sorry no one responded. Could you
create a bug report for the issue (http://issues.apache.org/bugzilla)
and then at
I've hacked the Maven builds so that they commit the generated web
content to the Subversion repository instead of directly uploading to
people.apache.org since the incubator demands and infrastructure
requests that web content be checked out from Subversion. I've built
all of the anticipa
I hacked the log4j 1.2 maven pom for log4j 1.3. The FileWatchdogTest
fails when run under Maven. I don't know why and I'm not planning on
researching further. Having the Maven build does make it a lot
simpler to create IDE projects however and I wanted one to write some
tests around AndF
On Jun 28, 2007, at 1:03 AM, Scott Deboy wrote:
I pulled everything about 2 weeks ago and ran everything through
Chainsaw.
The backported receivers which set properties on events (all of the
new network appenders) are throwing NPEs - around the property
setting code if I recall.
We sho
On Jul 1, 2007, at 5:29 PM, Paul Smith wrote:
On 30/06/2007, at 7:15 AM, Curt Arnold wrote:
There is a splash screen that shows Chainsaw history. That should
be integrated into src/changes/changes.xml.
Is this is the Release Notes section you're referring to? Yes I
think trackin
On Jul 1, 2007, at 5:27 PM, Paul Smith wrote:
I used the assembly:assembly plug to create a distribution,
however the descriptor (src/assembly/bin.xml) needs to be tweaked
to drop out non-re-distributable jars. Hopefully, all the non-re-
distributable jars are not essential to operation
-1.0_rc1.tar.gz
and jars in staging maven repo.
On Jun 29, 2007, at 6:12 PM, Curt Arnold wrote:
I've labeled a rc 1 for an "extras" companion that contains the
combined features of the filters, logmf, logsf, pattern-layout,
rolling and sound companions. I'd envision "
I've labeled a rc 1 for an "extras" companion that contains the
combined features of the filters, logmf, logsf, pattern-layout,
rolling and sound companions. I'd envision "extras" as the home for
any little incremental functionality that works with previous log4j
1.2 releases and does not
JmDNS referenced by the zeroconf companion uses a javax.jmdns
namespace but does not seem to be defined by the Java Community
Process. When i first say an unresolved reference on it, I first
went to the Sun site looking for a hit, but came up empty. I haven't
researched the issue and don'
There is a splash screen that shows Chainsaw history. That should be
integrated into src/changes/changes.xml.
I placed an empty development roadmap in src/site/apt/roadmap.apt.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
I made a fairly big set of changes to the Chainsaw POM in rev 552026
to harmonize the Chainsaw build with the companions. I added a
(temporary) reference to the staging repo, so you don't need to build
log4j 1.2.15 or the companions to build Chainsaw.
I used the assembly:assembly plug to c
On Jun 28, 2007, at 6:06 PM, Paul Smith wrote:
Hi Curt,
I have not yet worked out how to do this yet, but I thought I'd
mention it before we perform a release of the Receivers module.
Chainsaw will need to be shipped with a cut-down version of the
receivers package due to Classloading ru
Lets add another companion release candidate to the mix.
ZeroConfSocketHubAppender was extracted from Chainsaw and repacked
for use with log4j 1.2.9. I changed the name from log4j-zeroconf to
apache-log4j-zeroconf (will update Chainsaw's POM shortly).
Zeroconf 1.0 RC 1 (log4j 1.2.9, JmDNS
On Jun 28, 2007, at 1:03 AM, Scott Deboy wrote:
I pulled everything about 2 weeks ago and ran everything through
Chainsaw.
The backported receivers which set properties on events (all of the
new network appenders) are throwing NPEs - around the property
setting code if I recall.
We sho
As you could probably tell from the flurry of commit messages, I've
been prepping another round of release candidates. This time it
includes log4j 1.2.15 and a flock of companions. If they pass an
initial sanity check, I'd like to proceed to a release vote on them.
If anyone else wants t
On Jun 26, 2007, at 8:24 AM, Mark Modrall wrote:
We’ve cobbled together a 64-bit version of NTEventLogAppender by
changing the handle types to jlong in the jni glue and the cpp and
it seems to work okay. I don’t know what the best/standard way to
make conditional compilation in the jni ja
On Jun 24, 2007, at 3:47 AM, Paul Smith wrote:
I haven't been tracking the JUL <-> log4j stuff as well as I would
like, but there are enough things that I'm unsettled with that I'm
not ready to see them in an imminent release.
If you're feeling unsettled, I would appreciate it if you coul
On Jun 23, 2007, at 11:32 AM, Scott Deboy wrote:
The test case looks fine.
Anyone opposed to me merging this into the 1.2 branch, added to a
new org.apache.log4j.jul package.
Yes, I am opposed at the moment. log4j 1.2.15's release is imminent
and would really like to avoid adding a n
After further review, it looks like the JDiff plugin for Maven 2
isn't available, there are no jars for it in the master Maven repo.
A CLIRR plugin is available and is functional, but throws a NPE when
evaluating log4j when it runs into an interface that it can't load
(typically javax.jms.
On Jun 21, 2007, at 12:56 PM, Scott Deboy wrote:
I'd like to finish implementing repository-wide property support - I
think what would solve both issues is to have
LoggingEvent.getProperties
just return the repository properties, not the MDC properties.
LoggingEvent.getMDC would continue to
On Jun 21, 2007, at 1:18 AM, Scott Deboy wrote:
I'd still like us to consider finishing the property support
included in LoggerRepositoryEx (mostly requiring new functionality
being added to LoggingEvent). It would make finishing up the
backporting of the appenders & receivers essentially
On Jun 21, 2007, at 8:16 AM, Sagi Mann wrote:
Still, same error. Any advice? Can I get SVN to produce more error
detail?
I use the cmdline:
svn checkout http://svn.apache.org/repos/asf/logging/log4j/branches/
v1_2-branch/
Thanks,
Sagi Mann
Try https: instead of http:. Firewalls and c
I've cut a release candidate for apache-log4j-component. Jars are
available in the staging Maven repository at http://
people.apache.org/builds/logging/repo, distributions are at http://
people.apache.org/builds/logging/log4j/companions/component/1.0 and
documentation is online at http://lo
On Jun 20, 2007, at 10:37 PM, Paul Smith wrote:
On 21/06/2007, at 1:27 PM, Curt Arnold wrote:
I've just pushed another release candidate out. This won't be the
last since I forgot to update the release date and another tweak
to the POM that I'd like to do. I'
On Jun 20, 2007, at 11:55 PM, Paul Smith wrote:
I've done the following quick test to compare 1.2.14->1.2.15.
After unpacking both, I compared the contents of the respective
jars. One way to see missing/additional files was this:
unzip -l log4j-1.2.14.jar > /tmp/log4j.1.2.14.txt
..
unzip
On Jun 20, 2007, at 9:10 PM, Paul Smith wrote:
I've been tweaking the jul-log4j-bridge pom to experiment with the
distribution mechanism, and have placed a site and repo sample here:
http://people.apache.org/~psmith/logging.apache.org/
I'm not sure why the source distribution doesn't go wit
I've just pushed another release candidate out. This won't be the
last since I forgot to update the release date and another tweak to
the POM that I'd like to do. I'll likely refresh it tomorrow, but I
thought I would leave it up overnight for any immediate feedback.
The distributions ar
On Jun 18, 2007, at 11:26 PM, Paul Smith wrote:
Hi,
I have been in the background working on a companion to log4j that
I'm initially calling 'pinpoint'. It is designed as a log context
tool to facilitate production queries.
Logging events to a DB for querying is fine, except SQL queries
On Jun 13, 2007, at 1:37 PM, Mark Modrall wrote:
Hi…
We’re trying to move a java program to a Windows 64-bit
os environment with the 64-bit jvm. The latest problem we ran into
was that the nteventlogappender.dll is build 32-bit, so it’s barfing.
I went to see
On Jun 10, 2007, at 2:57 AM, Scott Deboy wrote:
log4j 1.3 included the ability to set properties at the logger
repository level (if it was a loggerrepositoryex) - logger
repository properties would be added to all events associated with
the repository.
That feature isn't currently availa
On Jun 10, 2007, at 3:28 AM, Scott Deboy wrote:
If I recall, we added support in 1.3 PatternLayout for more-than-
one character pattern names (like %properties).
We use this feature in Chainsaw to display ALL of the properties on
the event.
I'm not sure how much work it is to bring that i
I'm probably not going to get to it in the next day or so, but I've
been thinking about looking at the Chainsaw POM and seeing what if
any of the stuff from the other log4j POM's, src/site, src/assembly.
src/changes et al should be copied over. However, would not want to
conflict with anyt
On Jun 8, 2007, at 3:28 AM, Ortwin Glück wrote:
Hi,
I have implemented an asynchronous appender that greatly reduces
synchronization. It contains not a single synchronized statement,
relies on naturally thread-safe operations and just uses two
classes from the java.util.concurrent packag
On Jun 6, 2007, at 5:14 PM, Paul Smith wrote:
I've found in 'nix machines that some socket openings mixup the
localhost vs real IP address ethernet interfaces. The ERFA might
be listening on one, but the testcase tries to contact it on the
other?
I usually confirm this by doing somethin
I've been experimenting with Ubuntu 6.0.6.1 (aka Dapper Drake) as a
possible release build environment, but I'm running into a
"Connection Refused" exception on a New Socket((String) null, 5500)
call around line 70 in ERFATestCase when attempting to send a message
to the ExternallyRolledFil
On Jun 4, 2007, at 11:13 PM, Scott Deboy wrote:
Here are a few things we need to look into before we put out a
1.2.15 RC:
1. I couldn't configure a ConnectionSource for CustomSQLDBReceiver
- unrecognized element (unless I'm configuring it wrong, it means
DBReciever and DBAppender won't w
On Jun 5, 2007, at 12:21 AM, Scott Deboy wrote:
pom lists one of component's dependencies as log4j 1.2.8.
Is that correct?
Only the receivers companion requires features that were added in
1.2.15. The other companions should be usable with substantially
earlier versions of log4j. I'v
I've put up a log4j 1.2.15_rc2 build with Maven to http://
people.apache.org/builds. I'm not pushing to have a vote on it at
the moment, but to get any feedback on issues with the build.
Documentation for the build should shortly be at http://
logging.apache.org/log4j/1.2/. Distributions ar
201 - 300 of 772 matches
Mail list logo
