bugzilla | 2 Feb 08:08 2009
Picon

Bug report for Log4j [2009/02/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|Ass|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                                   |
|28647|Ass|Enh|2004-04-28|Add "Flush on Level" capability to FileAppender   |
|29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM|
|29304|New|Nor|2004-05-30|Starting XMLSocketAppender from config file       |
|29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe|
|29735|New|Nor|2004-06-22|Receiver list display error  when receiver has no |
|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|New|Maj|2004-08-27|Chainsaw mixes files in same panel                |
|30890|New|Min|2004-08-27|Newly opened log file should get focus            |
|30892|New|Min|2004-08-27|Log files cannot be closed                        |
(Continue reading)

Matt Hogstrom | 3 Feb 01:40 2009

Re: Bug report for Log4j [2009/02/01]


On Feb 2, 2009, at 2:08 AM, bugzilla <at> apache.org wrote:

> +
> ---------------------------------------------------------------------------+
> | 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                                      |
> |     |   |   |           
> |                                                  |
(Continue reading)

Matt Hogstrom | 3 Feb 02:30 2009

Re: Bug report for Log4j [2009/02/01]

Apologies for replying to the bug report.  I was in the process of  
moderating for some other lists and my fingers we're apparently in  
auto drive.  Sorry for the noise.

On Feb 2, 2009, at 7:40 PM, Matt Hogstrom wrote:

>
> On Feb 2, 2009, at 2:08 AM, bugzilla <at> apache.org wrote:
>
>> +
>> ---------------------------------------------------------------------------+
>> | Bugzilla Bug  
>> ID                                                           |
Curt Arnold | 3 Feb 18:53 2009
Picon

Re: Help: apache-log4j-1.2.15 does not support extras


On Feb 3, 2009, at 2:46 AM, Zhao, Frank wrote:

> Hi,
> Can anyone of you help me resolve below issue?
>
> I am using apache-log4j-1.2.15 and apache-log4j-extras-1.0.jar. here  
> is the error message.
>
> 16:04:59,801 INFO  [WebService] Using RMI server codebase: http://localhost:8083/
> 16:04:59,817 INFO  [Log4jService$URLWatchTimerTask] Configuring from  
> URL: resource:log4j.xml
> log4j:WARN Continuable parsing error 50 and column 15
> log4j:WARN The content of element type "appender" must match  
> "(errorHandler 
> ?,param 
> *,rollingPolicy 
> ?,triggeringPolicy?,connectionSource?,layout?,filter*,appender-ref*)".
> log4j:WARN Unrecognized element rollingPolicy
>
>
> I found Log4j does not recognize elements <rollingPolicy/> and  
> <triggeringPolicy/>. But there DTD, log4j.dtd, had these elemets. On  
> looking into the log4j code, specifically,  
> org.apache.log4j.xml.DOMConfigurator, the two elements are not there.
>
> Any suggestions are really appreciated.

The first warning suggests that your configuration file may have other  
problems.  Specifically, that you have an appender element nested  
(Continue reading)

bugzilla | 6 Feb 22:52 2009
Picon

DO NOT REPLY [Bug 46668] New: Level.ALL does not include Level.TRACE

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

           Summary: Level.ALL does not include Level.TRACE
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Appender
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: asf-bugzilla <at> rodneybeede.com

When I setup an appender to have a threshold of Level.ALL any log.trace() calls
do not get logged.

Should Level.ALL include that level as well.  If not then the api doc should be
updated to indicate so.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 6 Feb 23:04 2009
Picon

DO NOT REPLY [Bug 46668] Level.ALL does not include Level.TRACE

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

Rodney <asf-bugzilla <at> rodneybeede.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Rodney <asf-bugzilla <at> rodneybeede.com>  2009-02-06 14:04:37 PST ---
Logger.getRootLogger().setLevel(Level.ALL);

That fixed the issue.  Setting an individual appender to trace doesn't work
unless the root logger has that set first.

Perhaps some note in the api doc would be useful.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 9 Feb 08:08 2009
Picon

Bug report for Log4j [2009/02/08]

+---------------------------------------------------------------------------+
| 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|Ass|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                                   |
|28647|Ass|Enh|2004-04-28|Add "Flush on Level" capability to FileAppender   |
|29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM|
|29304|New|Nor|2004-05-30|Starting XMLSocketAppender from config file       |
|29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe|
|29735|New|Nor|2004-06-22|Receiver list display error  when receiver has no |
|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|New|Maj|2004-08-27|Chainsaw mixes files in same panel                |
|30890|New|Min|2004-08-27|Newly opened log file should get focus            |
|30892|New|Min|2004-08-27|Log files cannot be closed                        |
(Continue reading)

bugzilla | 9 Feb 10:44 2009
Picon

DO NOT REPLY [Bug 46675] New: Compatibility

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

           Summary: Compatibility
           Product: Log4j
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: critical
          Priority: P4
         Component: Other
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: dt.wagh <at> tcs.com

Is log4j.jar vversion 1.2.15 compatible with JDK 1.5 ?
What is new version of log4j.jar? Is this compatible with JDK 1.5

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 11 Feb 06:14 2009
Picon

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

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

           Summary: log4j file rolling over on restart of the server
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: AIX
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: paulindu <at> gmail.com

I have log4j for logging in my struts application.The rolling over is given as
midnight.But if i restart my server before it got rolled over and at midnight
the rolling over got failed since the same file exists already.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Mark Wallis | 12 Feb 11:43 2009

[PATCH] New option to disable DNS caching on SyslogAppender

Hi everyone,

While deploying log4j in our application we noticed that the  
SyslogAppender was resolving our SyslogHost value once upon  
construction and then caching that value until the JVM was restarted.  
We occasionally have to change the DNS resolution of our syslog server  
and would prefer not to have to restart our applications each time  
this occurs.

Attached is a patch that adds a new parameter for the SyslogAppender  
called "ResolveOnce". This parameter defaults to true (retaining  
existing behavior) but allows you to disable this cache by setting the  
parameter to false. With ResolveOnce=false the appender will ask the  
JVM to resolve the SyslogHost each time a message is sent. The JVM  
itself will cache the DNS resolution internally using its own rules  
(generally 30 seconds under a 1.6 JDK on Windows). I feel its  
important to keep this as optional functionality as in high-load  
situations its probably beneficial to keep the existing caching  
behaviour.

Any questions or comments, let me know.

Regards,
Mark Wallis
mwallis <at> serialmonkey.com

Attachment (syslog_dns_cache.patch): application/octet-stream, 3258 bytes

(Continue reading)


Gmane