conversionPattern parameters

configSections getting compiler message.

[jira] Created: (LOG4NET-185) Rolling files backups is not decreasing when updating MaxSizeRollBackups

Rolling files backups is not decreasing when updating MaxSizeRollBackups
------------------------------------------------------------------------

                 Key: LOG4NET-185
                 URL: https://issues.apache.org/jira/browse/LOG4NET-185
             Project: Log4net
          Issue Type: Bug
    Affects Versions: 1.2.10
         Environment: windows, all 
            Reporter: nir bon

When decreasing the MaxSizeRollBackups parameter at runtime.
the log4net is not deleting older files that has already written.

This means that if i change the MaxSizeRollBackups parameter repeadetly, i can reach to very large number
of old log files.

reconstruct scenario
^^^^^^^^^^^^^^^^^^^^^^
set number of backups to 10 files. wait till you have 10 files.
decrease number of backups to 2. 

result- 10 files will remain at disk. 8 files will never be deleted, 2 files will stay as retention.
expected - only 2 files will remain in disk.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (LOG4NET-184) Configuration Changes + XSD

Configuration Changes + XSD
---------------------------

                 Key: LOG4NET-184
                 URL: https://issues.apache.org/jira/browse/LOG4NET-184
             Project: Log4net
          Issue Type: Wish
          Components: Core, Documentation
    Affects Versions: 1.2.10
         Environment: n/a
            Reporter: Roger Knapp
            Priority: Minor

I'm a first-time user of log4net.  At first impression the configuration is very overwhelming.  Though I
recognize the strength by it's flexibility, I think it's one of the weakest points of log4net.  Some simple
changes could allow a real XSD to be created and thus to verify configuration and provide helpful context
help when tring to create them.  I've worked to understand the current configuration and after reading the
documentation and reverse engineering the code, I finally have an understanding what to do.  It was a long
and painful process and I wanted to share that experience with you only so that you could improve the
experience for others.

Namely, I want to suggest that the following change be allowed in future version.  Rather than having the
'type=' attribute used on elements (appenders, filters, and layouts) that reflect a built-in
component, I would recommend ADDING an alternative way of defining them by using the appender (or
fitler/layout) name as the element name much like you already do with the 'param' and class properties. 
This allows for us to now create full validating XSD files.

On the effort of creating an XSD file, I have made progress beyond what was previously available.  You can
find it at the following location:
http://csharptest.net/downloads/schema/log4net.xsd

I will be glad to transfer all rights to the project if and when it is distributed with the product.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

ApacheCon live video streaming available; keynotes and Apache 101 are free

Can't make ApacheCon this week in New Orleans?  You can still watch all
the keynotes, Apache 101 sessions, and system administration track in
live video streams:

   http://streaming.linux-magazin.de/en/program_apacheconus08.htm?ann

Keynotes and the Apache 101 lunchtime sessions are free; the full
sysadmin track, including httpd performance, security, and server stack
administration talks are available for a fee.

Keynotes include:
- David Recordon, Six Apart  (Wednesday 09:30)
   "Learning from Apache to create Open Specifications"

- Shahani Markus Weerawarana, Ph.D.  (Thursday 11:30)
   "Standing on the Shoulders of Giants"

- Sam Ramji, Microsoft  (Friday 11:30)
   "struct.new("future", :open, :microsoft)"

   Reminder: New Orleans is CST or UTC/GMT -6 hours.

Advance notice: ApacheCon EU 2009 returns to Amsterdam, 23-27 March.  We
had a great response to our CFP and look forward to announcing the
schedule in the next month.

Regards
--

-- 
Lars Eilebrecht  -  V.P., Conference Planning
lars <at> apache.org  -  http://www.us.apachecon.com

[jira] Created: (LOG4NET-183) Appender: RemoteSyslogAppender, semicolon persist if identity value is an empty string

Appender: RemoteSyslogAppender, semicolon persist if identity value is an empty string
--------------------------------------------------------------------------------------

                 Key: LOG4NET-183
                 URL: https://issues.apache.org/jira/browse/LOG4NET-183
             Project: Log4net
          Issue Type: Bug
          Components: Appenders
    Affects Versions: 1.2.10
         Environment: Windows XP, .Net 2.0
            Reporter: Victor Munoz
            Priority: Minor

Filename: RemolteSyslogAppender.cs
-------------------------------------------------------
// Identity
if (m_identity != null)
{
    m_identity.Format(writer, loggingEvent);
}
Else
{
    writer.Write(loggingEvent.Domain);
}
writer.Write(": ");  <------------------------------- ALWAYS include semicolon, even if identity is
an empty string.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (LOG4NET-182) LevelRangeFilter behavior doesn't match documentation; behavior and documentation are not as expected

LevelRangeFilter behavior doesn't match documentation; behavior and documentation are not as expected
-----------------------------------------------------------------------------------------------------

                 Key: LOG4NET-182
                 URL: https://issues.apache.org/jira/browse/LOG4NET-182
             Project: Log4net
          Issue Type: Bug
          Components: Appenders
    Affects Versions: 1.2.10
            Reporter: Chris Jerdonek
            Priority: Minor

The LevelRangeFilter's behavior doesn't match what the documentation says.  Also, neither the current
behavior nor the documentation seem right.

The log4net SDK Reference documentation says this about log4net.Filter.LevelRangeFilter:

"If there is a match between the range of priorities and the Level of the LoggingEvent, then the Decide
method returns Accept in case the AcceptOnMatch option value is set to true, if it is false then Deny is
returned. If there is no match, Deny is returned."

The actual behavior seems to differ from this in the case of a match.  If there is a match, it looks like the code
returns Accept when AcceptOnMatch is true, and Neutral if AcceptOnMatch is false.

I think both the documentation and behavior should be changed to the following:

"If there is a match between the range of priorities and the Level of the LoggingEvent, then the Decide
method returns Accept if the AcceptOnMatch option is true, and Deny if the AcceptOnMatch option is false. 
If there is no match, Neutral is returned."

This behavior seems more natural.  It also parallels the behavior of the LevelMatchFilter.

I believe this can be fixed simply by swapping occurrences of FilterDecision.Deny and
FilterDecision.Neutral in the code for LevelRangeFilter.Decide -- and also adjusting the
documentation as above.

Thanks.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (LOG4NET-181) Have PatternString recognize %n just as PatternLayout recognizes it

Have PatternString recognize %n just as PatternLayout recognizes it
-------------------------------------------------------------------

                 Key: LOG4NET-181
                 URL: https://issues.apache.org/jira/browse/LOG4NET-181
             Project: Log4net
          Issue Type: Improvement
          Components: Appenders
    Affects Versions: 1.2.10
            Reporter: Chris Jerdonek
            Priority: Minor

The log4net.Layout.PatternLayout class recognizes %n and %newline for newlines, but
log4net.Util.PatternString recognizes only %newline.  This may be a source of confusion for some people
(and was for me temporarily).

I don't know if there are other cases like this.  If so, it might make sense to have both classes recognize the
same conversion patterns -- for those patterns that would make sense in both contexts.  Thanks.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

log4net support for .NET framework 3.5

I just want to know that which version of log4net support Microsoft .NET
framework 3.5? Is there any such version exists at all till now?
--

-- 
View this message in context: http://www.nabble.com/log4net-support-for-.NET-framework-3.5-tp20164275p20164275.html
Sent from the Log4net - Dev mailing list archive at Nabble.com.

[jira] Commented: (LOG4NET-7) Detecting NoAppenderWarning

    [
https://issues.apache.org/jira/browse/LOG4NET-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642588#action_12642588
] 

Ron Grabowski commented on LOG4NET-7:
-------------------------------------

Everything gets passed up the chain and eventually ends up at the root logger if nothing matches. Can anyone
give me more info on what to detect?

> Detecting NoAppenderWarning
> ---------------------------
>
>                 Key: LOG4NET-7
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-7
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Core
>         Environment: From sourceforge - 785036
>            Reporter: Nicko Cadell
>            Assignee: Ron Grabowski
>             Fix For: 1.2.11
>
>
> It would be nice to be able to detect an event related
> to NoAppenderWarning. That is, one might want to take
> arbitrary actions when a logger category has no
> appenders attached to it, which is often caused by
> some kind of problem, usually related to configuration.
> Thanks for considering this suggestion. 
> Anonymous 

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (LOG4NET-66) PreserveFileExtension with StaticFileName

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

Ron Grabowski resolved LOG4NET-66.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.11

Fixed as part of LOG4NET-64 in r707809.

> PreserveFileExtension with StaticFileName
> -----------------------------------------
>
>                 Key: LOG4NET-66
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-66
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: Windows Server 2003
>            Reporter: Mike Blake-Knox
>            Assignee: Ron Grabowski
>            Priority: Minor
>             Fix For: 1.2.11
>
>         Attachments: RollingFileAppender.diff, rollingFileAppender.diff
>
>
> I found that the patch to make all RollingFileAppender log files have the same file extension (provided by
Joshua Bassett) didn't work properly if the log4net configuration used a static file name.
> I've attached a patch to version 312319 with his changes and mine merged.
> Mike

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.