headers
bugzilla | 1 May 2011 09:15
Picon
Favicon

Bug report for Log4j [2011/05/01]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
|     |   |           MIN=Minor   NOR=Normal    ENH=Enhancement TRV=Trivial |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|13099|Opn|Nor|2002-09-27|DOMConfigurator ignores category factory setting  |
|17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads  |
|20395|Inf|Enh|2003-06-01|PreparedStatementAppender Enhancement             |
|23329|New|Enh|2003-09-22|<logger> element in XML config should support reso|
|26084|Inf|Nor|2004-01-13|Log Event detail panel does not show special chara|
|27363|Inf|Enh|2004-03-02|JNI based SyslogAppender                          |
|27367|Inf|Enh|2004-03-02|NetSendAppender                                   |
|29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM|
|29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe|
|30055|New|Nor|2004-07-12|Problem with registering Appenders with the same n|
|30407|Inf|Maj|2004-07-30|Externally rolled file problem                    |
|30888|Inf|Maj|2004-08-27|Chainsaw mixes files in same panel                |
|30892|New|Min|2004-08-27|Log files cannot be closed                        |
|31089|New|Nor|2004-09-07|Does not accept ISO8601 dates in focus field      |
|31178|Inf|Cri|2004-09-11|Exception using Chainsaw for simple debugging     |
|31179|Ass|Enh|2004-09-11|Implement Chainsaw as Eclipse stand-alone applicat|
|33278|New|Min|2005-01-27|NPE thrown durring daily log file rollover        |
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tiago Veloso | 3 May 2011 13:09
Picon
Gravatar

Problems compiling with maven

Hi,

I am having trouble building log4j from source with maven. I get the following error:

[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project log4j:log4j:1.2.17-SNAPSHOT (/Users/fork/log4j/pom.xml) has 1 error
[ERROR]    
'build.plugins.plugin[org.apache.maven.plugins:maven-antrun-plugin].dependencies.dependency.scope'
for junit:junit:jar must be one of [compile, runtime, system] but is 'test'.  <at>  line 321, column 20
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.

I don't much of maven, is there anything I need to do other than 'mvn install'?

Tiago Veloso
ti.veloso <at> gmail.com
Permalink | Reply | 0 comments |
headers
Ashwine | 4 May 2011 09:38
Picon

Log4j- maxHistory property in TimeBasedRollingPolicy


We are using log4j-1.2.16.jar and apache-log4j-extras-1.1.jar to implement
the TimeBasedRollingPolicy logging functionality using the property File
approach.

We intend to use the maxHistory Feature but are getting the following
warning message. 

maxHistory that does not exist in
org.apache.log4j.rolling.TimeBasedRollingPolicy

1. we have checked several class files in the above mentioned jar files for
this property but we could'nt find the maxHistory property in the classes. 
2. We have taken the Property file approach and this is the syntax we've
used. 
 log4j.appender.GoopilAppender.RollingPolicy.maxHistory=180
3. The property file approach works fine for other properties like zipping
the log files, log file generation etc. but the maxHistory is having this
issue. 

--

-- 
View this message in context: http://old.nabble.com/Log4j--maxHistory-property-in-TimeBasedRollingPolicy-tp31539197p31539197.html
Sent from the Log4j - Dev mailing list archive at Nabble.com.
Permalink | Reply | 2 comments |
headers
Ralph Goers | 4 May 2011 12:57
Favicon

Re: Log4j- maxHistory property in TimeBasedRollingPolicy

What makes you think that maxHistory is a valid property?

Ralph

On May 4, 2011, at 12:38 AM, Ashwine wrote:

> 
> We are using log4j-1.2.16.jar and apache-log4j-extras-1.1.jar to implement
> the TimeBasedRollingPolicy logging functionality using the property File
> approach.
> 
> We intend to use the maxHistory Feature but are getting the following
> warning message. 
> 
> maxHistory that does not exist in
> org.apache.log4j.rolling.TimeBasedRollingPolicy
> 
> 1. we have checked several class files in the above mentioned jar files for
> this property but we could'nt find the maxHistory property in the classes. 
> 2. We have taken the Property file approach and this is the syntax we've
> used. 
> log4j.appender.GoopilAppender.RollingPolicy.maxHistory=180
> 3. The property file approach works fine for other properties like zipping
> the log files, log file generation etc. but the maxHistory is having this
> issue. 
> 
> -- 
> View this message in context: http://old.nabble.com/Log4j--maxHistory-property-in-TimeBasedRollingPolicy-tp31539197p31539197.html
> Sent from the Log4j - Dev mailing list archive at Nabble.com.
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
bugzilla | 5 May 2011 00:30
Picon
Favicon

DO NOT REPLY [Bug 51152] New: RollingFileAppender of companion/extras 1.1 contains possible race condition

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

             Bug #: 51152
           Summary: RollingFileAppender of companion/extras 1.1 contains
                    possible race condition
           Product: Log4j
           Version: 1.2
          Platform: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: grave <at> gmx.de
    Classification: Unclassified

Hi.

I'm using log4j 1.2.16 with the companion/extras 1.1 package to allow rolling
files based on time (at midnight) and perform gz compression. I also use an
non-blocking AsyncAppender that delegates to SMTPAppender, and FileAppender.

System:
- Quadcore Xeon 2,33 Ghz
- JDK 1.5.0_15
- about 20 custom parallel working threads
- about 800-1000mb log file per day

I encountered a strange behavior on that system, that compression sometimes
isn't performed. The file is renamed correctly though (from mylog.log to
(Continue reading)

Permalink | Reply | 6 comments |
headers
bugzilla | 5 May 2011 00:34
Picon
Favicon

DO NOT REPLY [Bug 51152] RollingFileAppender of companion/extras 1.1 contains possible race condition

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

Veit Guna <grave <at> gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Platform|PC                          |Other
         OS/Version|                            |Linux

--

-- 
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 | 5 May 2011 07:41
Picon
Favicon

DO NOT REPLY [Bug 46691] log4j file rolling over on restart of the server

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

--- Comment #1 from Lily <lilyj999 <at> gmail.com> 2011-05-05 05:41:28 UTC ---
We use log4j at our site http://www.alldiscountbooks.net and I found the
similar issue. Not sure, if this problem has been fixed. Thanks.

--

-- 
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 | 5 May 2011 07:52
Picon
Favicon

DO NOT REPLY [Bug 50844] DateFormat.getDateTimeInstance() is very expensive, we can cache it to improve performance

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

--- Comment #1 from Lily <lilyj999 <at> gmail.com> 2011-05-05 05:52:13 UTC ---
We faced the similar problem for performance of log4j. Basically we log a bunch
of messages for each http request. Then, we found that http response time gets
hits. So what we ended up was to first log each message to a StringBuffer,
after some messages are logged, i.e. 100, we then call log4j api to log. This
has improved the response time. However, we still see a response hit when the
chunk of messages
are written to file.

Lily
http://www.alldiscountbooks.net

--

-- 
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
Ashwine | 5 May 2011 08:12
Picon

Re: Log4j- maxHistory property in TimeBasedRollingPolicy


Hi Ralph, 

Figured out the problem. the log4j property for deleting old archived files
is maxBackupIndex and not maxHistory. 
I found this property in the RollingFileAppender class of the log4j jar.
We are however using TimeBasedRollingPolicy which uses the
apache-log4j-extras version of the RollingFileAppender which i figured out
does not contain this property. 

Ralph Goers wrote:
> 
> What makes you think that maxHistory is a valid property?
> 
> Ralph
> 
> On May 4, 2011, at 12:38 AM, Ashwine wrote:
> 
>> 
>> We are using log4j-1.2.16.jar and apache-log4j-extras-1.1.jar to
>> implement
>> the TimeBasedRollingPolicy logging functionality using the property File
>> approach.
>> 
>> We intend to use the maxHistory Feature but are getting the following
>> warning message. 
>> 
>> maxHistory that does not exist in
>> org.apache.log4j.rolling.TimeBasedRollingPolicy
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
bugzilla | 6 May 2011 22:33
Picon
Favicon

DO NOT REPLY [Bug 51164] New: log4j should not dump errors to stdout on interrupt

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

             Bug #: 51164
           Summary: log4j should not dump errors to stdout on interrupt
           Product: Log4j
           Version: unspecified
          Platform: PC
        OS/Version: Solaris
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: eschrock1 <at> yahoo.com
    Classification: Unclassified

In our environment, we make heavy use of log4j (1.2.15), as well as async
threads that are canceled through interrupt().  Every so often, we get the
following spam dumped to stdout:

java.io.InterruptedIOException
    at java.io.FileOutputStream.writeBytes(Native Method)
    at java.io.FileOutputStream.write(FileOutputStream.java:260)
    at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
    at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
    at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:276)
    at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122)
    at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212)
    at org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:58)
    ...
(Continue reading)

Permalink | Reply | 0 comments |

Gmane