gmane.comp.jakarta.log4j.devel

log4j configuration for multiple WARs

rjkoop — 2012-05-16T12:39:00

I'm having trouble configuring log4j in a multi-WAR environment.  I have a
single log4.xml specified by using  the
log4j.configuration=http://..../log4j.xml option.  Each WAR has it's own
log4j.jar in it's WEB-INF/lib directory.  I want all these WARs to write the
logs to a single file (based on the common log4j.xml file).

Even though all WARs are deployed in a single JVM process, I'm getting
strange behavior where logging will stop for some WARs, the daily rollover
doesn't work correctly, some WARs write to old log file once it's rolled
over, log file entries aren't in order, ....  From the docs log4j is thread
safe so I think this should work.  Any ideas?

[jira] [Resolved] (LOG4J2-60) Ability to configure log level filtering on a per basis

Ralph Goers (JIRA — 2012-05-16T06:26:11

     [ https://issues.apache.org/jira/browse/LOG4J2-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers resolved LOG4J2-60.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-alpha1
         Assignee: Ralph Goers

Log4j 2 has been enhanced to support both a level being specified on an appender-ref but a filter as well.  Thanks for the suggestion!
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (LOG4J2-60) Ability to configure log level filtering on a per basis

Shane Kelly (JIRA — 2012-05-15T04:24:45

[Bug 50486] Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

2012-05-14T19:49:32

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

--- Comment #27 from marcel< at >frightanic.com ---
(In reply to comment #26)

You need to follow the thread "[VOTE] Release log4j 1.2.17 RC3" at
http://mail-archives.apache.org/mod_mbox/logging-log4j-dev/201205.mbox/browser

[Bug 50486] Memoryleak - org.apache.log4j.helpers.ThreadLocalMap

2012-05-14T19:46:32

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

--- Comment #26 from john caron <caron< at >unidata.ucar.edu> ---
Hi: any word on this release? Would love to cross this problem off my list.
Thanks for your hard work! John

Re: [VOTE] Release log4j 1.2.17 RC3

Ralph Goers — 2012-05-13T21:11:40

Yes, this build is a bit odd. However, I was able to build it on my Mac successfully and I don't see any issues with it so 

+1

Ralph

On May 12, 2012, at 5:37 AM, Christian Grobmeier wrote:

Re: [VOTE] Release log4j 1.2.17 RC3

Ralph Goers — 2012-05-13T02:20:41

Anyone can vote. In fact, everyone is encouraged to validate the release candidate and vote on it.  Only Logging PMC members votes are binding but if someone who isn't a PMC member finds a serious problem it is probably just as likely to get fixed.

Ralph

On May 12, 2012, at 5:27 PM, Tushar Kapila wrote:

Re: [VOTE] Release log4j 1.2.17 RC3

Tushar Kapila — 2012-05-13T00:27:22

Do all of us have a vote? If so
I will try how far i can get on windows. You want a few of us to get
the src files from the links you provided. Build, run in built tests
is all right? Then post back here with a + or - ?
Or should we also use new jars on existing project as smoke test ?


On 5/13/12, Gary Gregory <ggregory< at >apache.org> wrote:

Re: [VOTE] Release log4j 1.2.17 RC3

Scott Deboy — 2012-05-12T21:19:07

I will check it out this week as well. 

Scott



On May 12, 2012, at 1:42 PM, Gary Gregory <ggregory< at >apache.org> wrote:

Re: [VOTE] Release log4j 1.2.17 RC3

Gary Gregory — 2012-05-12T20:42:10

I just installed virtual box with ubuntu in it but have not got
further. Maybe this week...

On Sat, May 12, 2012 at 8:37 AM, Christian Grobmeier <grobmeier< at >gmail.com>wrote:

Re: [VOTE] Release log4j 1.2.17 RC3

Ralph Goers — 2012-05-12T13:04:14

I should have time to review this during the next 36 hours.

Ralph

On May 12, 2012, at 5:37 AM, Christian Grobmeier <grobmeier< at >gmail.com> wrote:

Re: [VOTE] Release log4j 1.2.17 RC3

Christian Grobmeier — 2012-05-12T12:37:21

Fellows, any ideas what we can do now?
6 days past and we have no vote (except my implicit one).
We now know we need to improve our build. But I really would like to
start with that after 1.2.17

Suggestion: please let me know if you have a chance to vote or not. I
will gladly wait for another while, but if it is definitely not
possible, we need to see if we can cancel this vote and instead
working towards an improved build.


On Wed, May 9, 2012 at 7:27 AM, Curt Arnold <carnold< at >apache.org> wrote:

Re: [VOTE] Release log4j 1.2.17 RC3

Curt Arnold — 2012-05-09T05:27:55

On May 7, 2012, at 2:20 PM, Gary Gregory wrote:


A cloud provider (Amazon Web Services, for example), a bootable USB or CD would be another. A cloud provider could be problematic since you would not want to have your code signing key on a machine you don't control.



I haven't followed Ant for a long time. Ant properties since time began have been immutable once set. it was once acceptable style to take advantage of this documented behavior and, for example, set properties to a default value that would be ignored if the called provided an explicit value. Apparently, that fell out of style and hence this warning. I think the Nant didn't follow that lead and lots of confusion ensued.   

I can't hit the 72 hour mark, but can try to review and build within 24 hours.

Re: [VOTE] Release log4j 1.2.17 RC3

Christian Grobmeier — 2012-05-09T05:12:46

To my knowledge, yes. I did not succeed to run this build under Mac
OSX. With Ubuntu the setup is still time consuming but doable.


+1
Actually there are some portions missing. For example: what to do with
the release artifacts after a successful vote?
My suggestion is we update this file after we have performed the
complete release cycle.


hm didn't see this, but definitely worth to check.

Others: anybody else with some time who can give a +1?

Cheers
Christian

Re: [VOTE] Release log4j 1.2.17 RC3

Gary Gregory — 2012-05-07T19:20:33

Hi All:

Because I could not get the full build to run on Windows 7 with Maven 2 or
3. I feel reluctant to VOTE +1 here. This is a know issue due to the use
the GNU app Winres. I get bits and pieces of the build to work but nothing
like the level of confidence I have running Commons builds for different
components. I can build the site (with the Maven stack trace noted in other
RC votes), I can run the tests. The changes seems OK, but... as a new
committer here I need to learn the code some more.

Is the only way to get this to build is to install VirtualBox and a Linux
distro?

I will note the following nits though:

The build instructions use both version 1.2.16 and 1.2.17 in text and
examples, see "
http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/building.html

This is not critical but should be fixed in SVN. I would like to see
version agnostic instructions or use the latest version (the one being
built).

I see this warning from M3 and M2:

prepare:
[available] DEPRECATED - <available>

Re: [VOTE] Release log4j 1.2.17 RC2

Christian Grobmeier — 2012-05-07T08:36:19


OK I am fine with that also. I wrote what I mentioned above into
building.xml but will change it once the release passed (or before the
next RC).



I am not speaking of removing it completely. I just speak of making
two builds out of one. I consider it "maintenance" to improve the
software build too. We need to do something more in that area after
1.2.17, because for example the companions need a release (they block
chainsaw). Anyway, if we would have an easier build probably more
people would be able to serve as release manager.



Sure! Even when I suffer at the moment every time you bring up a new
improvement, I will be glad afterwards, because everything has become
better :-)
Lets see if RC3 will do the trick.

Cheers
Christian

Re: [VOTE] Release log4j 1.2.17 RC2

Gary Gregory — 2012-05-06T15:52:53


Ah, I did not mean to misrepresent what we do in Commons :) I describe what
I've done and see other Commons RM do ;)

Gary

Re: [VOTE] Release log4j 1.2.17 RC2

Ralph Goers — 2012-05-06T14:46:54

On May 6, 2012, at 7:12 AM, Gary Gregory <ggregory< at >apache.org> wrote:



That is not what I have done in commons :-)  

Ralph

Re: [VOTE] Release log4j 1.2.17 RC2

Gary Gregory — 2012-05-06T14:12:34

 On Sun, May 6, 2012 at 5:41 AM, Christian Grobmeier <grobmeier< at >gmail.com

    > Hi,
    >
    > On Sun, May 6, 2012 at 12:28 AM, Gary Gregory <ggregory< at >apache.org>
wrote:
    > > One of the reason I voted -1 on RC1 is because the release notes
where
    > > incomplete. They still are in RC2; still missing under "Release
1.2.17",
    > is
    > > an entry for
https://issues.apache.org/bugzilla/show_bug.cgi?id=52913 I
    > > added the missing entry to changes.xml.
    >
    > ah now I understand the problem. First, when you send this issue in
    > the first mail, I was not able to open it. Somewhat happend to the
    > link which made it crap for me. I asked you about it with my response
    > to that mail, but you didn't respond. I thought it was because of the
    > other issues you mentioned. I fixed them and went ahead.
    >
    > I was in doubt about this issue, because I didn't knew why it should
    > be on the list. I missed that you have committed it. Usually we fix
    > something and then the on

[VOTE] Release log4j 1.2.17 RC3

Christian Grobmeier — 2012-05-06T12:28:05

Hello,

please vote to release log4j 1.2.17 RC3.

Changes since last RC:
- missing issue in changes.xml finally appeared there
- moved BUILD-INFO.txt to a new page on the site
- added some new build instructions

Artifacts:
http://people.apache.org/builds/logging/repo/log4j/log4j/

Sources are included in the .zip files aswell.

Tag:
http://svn.apache.org/repos/asf/logging/log4j/tags/v1_2_17_rc3/

Website:
http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html

[] +1, release the artifacts
[] -1, don't release because

The vote will remain open for the usual 72 hours.

Thanks,
Christian

[Bug 50369] missing comma in class header javadoc for Level

2012-05-06T12:12:47

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

grobmeier <grobmeier< at >gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|1.2.18                      |1.2
   Target Milestone|---                         |1.2.18