headers
Iso Su (Updated) (JIRA | 1 Feb 2012 20:06
Picon
Favicon

[jira] [Updated] (LOG4NET-322) Conditional compilation symbols for .net4 Release


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

Iso Su updated LOG4NET-322:
---------------------------

    Attachment: ReleaseConditionalSymbols.patch

Here's the change I used to fix it for myself

> Conditional compilation symbols for .net4 Release
> -------------------------------------------------
>
>                 Key: LOG4NET-322
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-322
>             Project: Log4net
>          Issue Type: Bug
>          Components: Builds
>    Affects Versions: 1.2.11
>         Environment: log4net.vs2010 project
>            Reporter: Iso Su
>         Attachments: ReleaseConditionalSymbols.patch
>
>
> While Debug configuration has a proper list of Conditional compilation symbols
("NET;NET_2_0;NET_4_0"), the Release configuration has them set to "STRONG;NET;NET_1_0;". This
causes problems with a lot of appenders and LogicalThreadContext is not working, since it uses
SetData(), not LogicalSetData()
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stefan Bodewig (Resolved) (JIRA | 2 Feb 2012 05:47
Picon
Favicon

[jira] [Resolved] (LOG4NET-322) Conditional compilation symbols for .net4 Release


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

Stefan Bodewig resolved LOG4NET-322.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.12

Thanks!

Patch applied in svn revision 1239458

> Conditional compilation symbols for .net4 Release
> -------------------------------------------------
>
>                 Key: LOG4NET-322
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-322
>             Project: Log4net
>          Issue Type: Bug
>          Components: Builds
>    Affects Versions: 1.2.11
>         Environment: log4net.vs2010 project
>            Reporter: Iso Su
>             Fix For: 1.2.12
>
>         Attachments: ReleaseConditionalSymbols.patch
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jim Moore (Commented) (JIRA | 8 Feb 2012 23:16
Picon
Favicon

[jira] [Commented] (LOG4NET-178) Log4Net stops logging after appdomain recycle of aps.net2.0 application


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

Jim Moore commented on LOG4NET-178:
-----------------------------------

I see this issue as well.  Exactly the same, IIS 6, asp.net 4.0.

                
> Log4Net stops logging after appdomain recycle of aps.net2.0 application
> -----------------------------------------------------------------------
>
>                 Key: LOG4NET-178
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-178
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: Windows server 2003
>            Reporter: Richard Nijkamp
>             Fix For: 1.2 Maintenance Release
>
>
> Dear sir/madam,
>  We are using Log4Net 1.2.10. We encounter the problem that Log4net doesn't continue logging after an
event that triggers an appdomain recycle/restart.
>  In the global.asax we start the logging with:
>  private static readonly ILog log = LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jim Moore (Issue Comment Edited) (JIRA | 8 Feb 2012 23:25
Picon
Favicon

[jira] [Issue Comment Edited] (LOG4NET-178) Log4Net stops logging after appdomain recycle of aps.net2.0 application


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

Jim Moore edited comment on LOG4NET-178 at 2/8/12 10:24 PM:
------------------------------------------------------------

I see this issue as well.  Exactly the same, IIS 6, asp.net 4.0, log4Net 1.2.11.

                
      was (Author: reallyjim):
    I see this issue as well.  Exactly the same, IIS 6, asp.net 4.0.

                  
> Log4Net stops logging after appdomain recycle of aps.net2.0 application
> -----------------------------------------------------------------------
>
>                 Key: LOG4NET-178
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-178
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: Windows server 2003
>            Reporter: Richard Nijkamp
>             Fix For: 1.2 Maintenance Release
>
>
> Dear sir/madam,
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jim Moore (Issue Comment Edited) (JIRA | 8 Feb 2012 23:25
Picon
Favicon

[jira] [Issue Comment Edited] (LOG4NET-178) Log4Net stops logging after appdomain recycle of aps.net2.0 application


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

Jim Moore edited comment on LOG4NET-178 at 2/8/12 10:24 PM:
------------------------------------------------------------

I see this issue as well.  Exactly the same, IIS 6, asp.net 4.0, log4Net 1.2.11.  I'm using the standard RollingFileAppender.

                
      was (Author: reallyjim):
    I see this issue as well.  Exactly the same, IIS 6, asp.net 4.0, log4Net 1.2.11.

                  
> Log4Net stops logging after appdomain recycle of aps.net2.0 application
> -----------------------------------------------------------------------
>
>                 Key: LOG4NET-178
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-178
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: Windows server 2003
>            Reporter: Richard Nijkamp
>             Fix For: 1.2 Maintenance Release
>
>
> Dear sir/madam,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Johnson, Thomas | 8 Feb 2012 23:59

RE: [jira] [Issue Comment Edited] (LOG4NET-178) Log4Net stops logging after appdomain recycle of aps.net2.0 application

Fyi we haven't seen this on any of our IIS7 apps

-----Original Message-----
From: Jim Moore (Issue Comment Edited) (JIRA) [mailto:jira <at> apache.org] 
Sent: Wednesday, February 08, 2012 3:25 PM
To: log4net-dev <at> logging.apache.org
Subject: [jira] [Issue Comment Edited] (LOG4NET-178) Log4Net stops logging after appdomain recycle of
aps.net2.0 application


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

Jim Moore edited comment on LOG4NET-178 at 2/8/12 10:24 PM:
------------------------------------------------------------

I see this issue as well.  Exactly the same, IIS 6, asp.net 4.0, log4Net 1.2.11.  I'm using the standard RollingFileAppender.

                
      was (Author: reallyjim):
    I see this issue as well.  Exactly the same, IIS 6, asp.net 4.0, log4Net 1.2.11.

                  
> Log4Net stops logging after appdomain recycle of aps.net2.0 application
> -----------------------------------------------------------------------
>
>                 Key: LOG4NET-178
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-178

>             Project: Log4net
(Continue reading)

Permalink | Reply | 0 comments |
headers
Matthew Gabeler-Lee (Created) (JIRA | 9 Feb 2012 21:04
Picon
Favicon

[jira] [Created] (LOG4NET-323) AbsoluteTimeDateFormatter caches string representation of now too aggressively

AbsoluteTimeDateFormatter caches string representation of now too aggressively
------------------------------------------------------------------------------

                 Key: LOG4NET-323
                 URL: https://issues.apache.org/jira/browse/LOG4NET-323
             Project: Log4net
          Issue Type: Bug
          Components: Other
    Affects Versions: 1.2.11
            Reporter: Matthew Gabeler-Lee
            Priority: Minor

The AbsoluteTimeDateFormatter class caches the string representation of the most recent timestamp it
has seen, down to the second.

The problem is, this cache is inherited by other formatter classes, which represent that value in
different ways.

This causes the formatted date/time generated by layouts and thus appended to logs to be inconsistent if
there are multiple date/time formats in use in different appenders.  For example, I have a debug appender
which uses the %date{ABSOLUTE} format, and a log file appender which uses the %date{ISO8601} format. 
Because the debug appender sees most messages first, most (but not all!) entries in the log file get the
ABSOLUTE format, even though ISO8601 was specified.

The cache of the string representation needs to be specific to a particular date format.

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

Permalink | Reply | 1 comment |
headers
Jochen Kühner (Updated) (JIRA | 10 Feb 2012 19:11
Picon
Favicon

[jira] [Updated] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files.


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

Jochen Kühner updated LOG4NET-27:
---------------------------------

    Attachment: RollingFileAppender.cs

Patched the patch to work with the newest source, and changed the file deletion a little bit (I use the
lastwritedate to find the oldest file!)

> Rolling files on date/time boundaries doesn't support a maximum number of backup files.
> ---------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-27
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-27
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 1.2.11
>            Reporter: Florian Ramillien
>            Priority: Minor
>             Fix For: 1.2 Maintenance Release
>
>         Attachments: LOG4NET-27.patch, RollingFileAppender.cs, RollingFileAppender.cs,
RollingFileAppender.cs, RollingFileAppender.cs.patch, RollingFileAppender.patch
>
>
> A maximum of backup files exist when rolling files on file size, but not for rolling on date/time.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sergei Vorobyov | 21 Feb 2012 17:04

lots of DeletePending files

Greetings!

Why does log4net-1.2.11 create so many "DeletePending" files in the
RollingFileAppender mode with

  <appender name="File1Appender" type="log4net.Appender.RollingFileAppender">
    <file value="ylog-file-1.txt" />
    <appendToFile value="true" />

    <rollingStyle value="Size"/>
    <maximumFileSize value="100"/>
    <maxSizeRollBackups value="10"/>

    <staticLogFileName value="true"/>

    <lockingModel type="log4net.Appender.FileAppender+MinimalLock" />

    <layout type="log4net.Layout.PatternLayout">
      <conversionPattern value="%date %message%newline" />
    </layout>
  </appender>

???

Thanks!

PS why dont you people have the simple search engine to search through
the mail archives?

-rwxr-xr-x+ 1 Sergei None     131 Feb 21 16:41 ylog-file-1.txt*
(Continue reading)

Permalink | Reply | 0 comments |

Gmane