headers
Curt Arnold | 1 Nov 2010 02:06
Picon
Favicon

Apache Project Branding requirements

I worked several hours on preparing the extras companion for release today, specifically around the new
Apache Project Branding requirements (http://www.apache.org/foundation/marks/pmcs).  I made some
progress, but fell short of completing. 

Among the issues:

Consistent letter case for log4j.  log4j is exclusively rendered as "log4j" in our text content, but is
LOG4J in our logo.  I committed changes to the extras companion to use LOG4J since it was easier to change
than the logo, but I am expecting to revert as the lower case log4j occurs so much more frequently in our content.

Logging Services and LOG4J logos:  Both need to have TM added to them, but I do not think that we have the
original vector files in our archives.  The earlier commit of logo.jpg that I've been able to find is
2001-05-18 just prior to the log4j 1.1 release
(http://svn.apache.org/viewvc?view=revision&revision=309144), but no vector files were
committed.  Should be able to tolerably superimpose a TM on them, but changing the casing of the LOG4J in the
foreground may be more difficult without the vector originals.  Fortunately my wife does that type of
stuff and I'll see if she can help out.

Adding the required trademark notices required providing an alternative site template.  Will explore if
Maven 3 gives us some help.

Sorry I can't make ApacheCON this year.  Post anything interesting to the list.
Permalink | Reply | 1 comment |
headers
Ralph Goers | 1 Nov 2010 05:17
Favicon

Re: Apache Project Branding requirements

That is interesting. I've always used Log4j or Log4J (the second is what shows up in my email client as the
addressee on the dev list.

Ralph

On Oct 31, 2010, at 6:06 PM, Curt Arnold wrote:

> I worked several hours on preparing the extras companion for release today, specifically around the new
Apache Project Branding requirements (http://www.apache.org/foundation/marks/pmcs).  I made some
progress, but fell short of completing. 
> 
> Among the issues:
> 
> Consistent letter case for log4j.  log4j is exclusively rendered as "log4j" in our text content, but is
LOG4J in our logo.  I committed changes to the extras companion to use LOG4J since it was easier to change
than the logo, but I am expecting to revert as the lower case log4j occurs so much more frequently in our content.
> 
> Logging Services and LOG4J logos:  Both need to have TM added to them, but I do not think that we have the
original vector files in our archives.  The earlier commit of logo.jpg that I've been able to find is
2001-05-18 just prior to the log4j 1.1 release
(http://svn.apache.org/viewvc?view=revision&revision=309144), but no vector files were
committed.  Should be able to tolerably superimpose a TM on them, but changing the casing of the LOG4J in the
foreground may be more difficult without the vector originals.  Fortunately my wife does that type of
stuff and I'll see if she can help out.
> 
> Adding the required trademark notices required providing an alternative site template.  Will explore if
Maven 3 gives us some help.
> 
> Sorry I can't make ApacheCON this year.  Post anything interesting to the list.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla | 4 Nov 2010 15:50
Picon
Favicon

DO NOT REPLY [Bug 50213] New: Category callAppenders synchronization causes java.lang.Thread.State: BLOCKED - synchronization can be avoided by using immutable AppenderAttachableImpl

https://issues.apache.org/bugzilla/show_bug.cgi?id=50213

           Summary: Category callAppenders synchronization causes
                    java.lang.Thread.State: BLOCKED - synchronization can
                    be avoided by using immutable AppenderAttachableImpl
           Product: Log4j
           Version: 1.2
          Platform: HP
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: dave <at> daveboden.com

Using log4j 1.2.16 on Linux.

When logging from 10 threads almost simultaneously, I'm seeing intermittent
deadlocking. Doing a kill -3 on Linux shows the thread dump and shows
java.lang.Thread.State: BLOCKED -  waiting to lock <0xd42e9a78> (a
org.apache.log4j.spi.RootLogger)

Looking at the Category code, I can see how threads could potentially deadlock:

Method: callAppenders(LoggingEvent event)
...

    for(Category c = this; c != null; c=c.parent) {
      // Protected against simultaneous call to addAppender, removeAppender,...
(Continue reading)

Permalink | Reply | 7 comments |
headers
bugzilla | 4 Nov 2010 18:04
Picon
Favicon

DO NOT REPLY [Bug 50213] Category callAppenders synchronization causes java.lang.Thread.State: BLOCKED - synchronization can be avoided by using immutable AppenderAttachableImpl

https://issues.apache.org/bugzilla/show_bug.cgi?id=50213

--- Comment #1 from Dave Boden <dave <at> daveboden.com> 2010-11-04 13:04:42 EDT ---
Created an attachment (id=26254)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=26254)
Patch to remove synchronization from Category but still keep thread safety

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Permalink | Reply | 0 comments |
headers
carnold | 5 Nov 2010 02:35
Picon
Favicon

svn commit: r1031390 - in /logging/log4j/companions/extras/trunk/src/site/resources/images: logo.jpg ls-logo.jpg

Author: carnold
Date: Fri Nov  5 01:35:28 2010
New Revision: 1031390

URL: http://svn.apache.org/viewvc?rev=1031390&view=rev
Log:
Bug 50188: Add trademark sign to logos

Modified:
    logging/log4j/companions/extras/trunk/src/site/resources/images/logo.jpg
    logging/log4j/companions/extras/trunk/src/site/resources/images/ls-logo.jpg

Modified: logging/log4j/companions/extras/trunk/src/site/resources/images/logo.jpg
URL: http://svn.apache.org/viewvc/logging/log4j/companions/extras/trunk/src/site/resources/images/logo.jpg?rev=1031390&r1=1031389&r2=1031390&view=diff
==============================================================================
Binary files - no diff available.

Modified: logging/log4j/companions/extras/trunk/src/site/resources/images/ls-logo.jpg
URL: http://svn.apache.org/viewvc/logging/log4j/companions/extras/trunk/src/site/resources/images/ls-logo.jpg?rev=1031390&r1=1031389&r2=1031390&view=diff
==============================================================================
Binary files - no diff available.
Permalink | Reply | 0 comments |
headers
carnold | 5 Nov 2010 14:07
Picon
Favicon

[GUMP <at> vmgump]: Project logging-log4j-12-tests (in module logging-log4j-12) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project logging-log4j-12-tests has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 7 runs.
The current state of this project is 'Failed', with reason 'Build Timed Out'.
For reference only, the following projects are affected by this:
    - logging-log4j-12-tests :  Fast and flexible logging package for Java

Full details are available at:
    http://vmgump.apache.org/gump/public/logging-log4j-12/logging-log4j-12-tests/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Made directory [/srv/gump/public/workspace/logging-log4j-12/tests/classes]
 -INFO- Failed with reason build timed out

The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4j-12/logging-log4j-12-tests/gump_work/build_logging-log4j-12_logging-log4j-12-tests.html
Work Name: build_logging-log4j-12_logging-log4j-12-tests (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 hour 10 secs
Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true
-Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla | 6 Nov 2010 15:59
Picon
Favicon

DO NOT REPLY [Bug 50213] Category callAppenders synchronization causes java.lang.Thread.State: BLOCKED - synchronization can be avoided by using immutable AppenderAttachableImpl

https://issues.apache.org/bugzilla/show_bug.cgi?id=50213

--- Comment #2 from Curt Arnold <carnold <at> apache.org> 2010-11-06 10:59:27 EDT ---
The deadlock that you are experiencing isn't likely due to the lock on
category.  There are likely two other locks in conflict that result in cascade
of blocks.  Could you attach a full dump to see if we can pick out the blocks
that start the problem.

I am assuming that you've used you modified version of log4j and you saw an
improved experience.  It might possibly isolate the threads where you might
still have the initiating deadlock but it doesn't spread to any other thread
that logs on the same logger which would be a very beneficial change.

Changing the result type of Category.removeAppender(Appender) and
removeAppender(String) breaks compatibility with any compiled app that calls
either method as they will now could throw a NoSuchMethodException, see
http://java.sun.com/docs/books/jls/second_edition/html/binaryComp.doc.html#45208.
 Also, as you saw with NOPLogger, it requires any extended Logger (discouraged,
but not prevented) to be modified.

Replacing the lazy construction of AppenderAttachableImpl might have some, but
likely small, performance impact.  It likely was a big deal in the JDK 1.1 days
when object creation was substantially more expensive.  The member is package
visible (no explicit public, private or protected) so the only way that it
could become null again is if something in org.apache.log4j set it null and
scanning the rest of the source shows no place that that could occur.

Touching synchronization in Category is a minefield.  It could be safer to
approach this by introducing a new class extended from Logger that is
inherently thread-safe and then allowing the user to configure to use the
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla | 6 Nov 2010 22:19
Picon
Favicon

DO NOT REPLY [Bug 50225] New: Filesystem placeholder not working with PropertyConfigurator

https://issues.apache.org/bugzilla/show_bug.cgi?id=50225

           Summary: Filesystem placeholder not working with
                    PropertyConfigurator
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Configurator
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: pjmv1986 <at> gmail.com

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Permalink | Reply | 0 comments |
headers
bugzilla | 7 Nov 2010 01:14
Picon
Favicon

DO NOT REPLY [Bug 50226] New: Problem with placeholders and PropertyConfigurator

https://issues.apache.org/bugzilla/show_bug.cgi?id=50226

           Summary: Problem with placeholders and PropertyConfigurator
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Configurator
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: pjmv1986 <at> gmail.com

Created an attachment (id=26264)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=26264)
Code snippet for PropertyConfigurator

Hello and well met. I'm having problems while trying PropertyConfigurator to
find configuration files with system placeholders in their names. I'll
ellaborate on this issue:

I'm trying to set up the logging engine for a Web App. In order to give more
flexibility in the configuration and deployment process, I have a properties
file where the administrator can set the location of the main log4j
configuration file. In my application code, I load the first file as a
java.util.Properties instance, get the location of the log4j.properties file
via Properties.getProperty, and then call PropertyConfigurator.configure with
that value as the String parameter. The problem comes when I set the location
as a file name with filesystem placeholders, e.g.
(Continue reading)

Permalink | Reply | 0 comments |
headers
carnold | 7 Nov 2010 04:46
Picon
Favicon

[GUMP <at> vmgump]: Project logging-log4j-12-tests (in module logging-log4j-12) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project logging-log4j-12-tests has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - logging-log4j-12-tests :  Fast and flexible logging package for Java

Full details are available at:
    http://vmgump.apache.org/gump/public/logging-log4j-12/logging-log4j-12-tests/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Made directory [/srv/gump/public/workspace/logging-log4j-12/tests/classes]
 -INFO- Failed with reason build failed

The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4j-12/logging-log4j-12-tests/gump_work/build_logging-log4j-12_logging-log4j-12-tests.html
Work Name: build_logging-log4j-12_logging-log4j-12-tests (Type: Build)
Work ended in a state of : Failed
Elapsed: 46 mins 36 secs
Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true
-Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml
-Dbuild.sysclasspath=only regression
(Continue reading)

Permalink | Reply | 0 comments |

Gmane