RollingFileAppender BUG...

Hi
my log file is configured to be : log09032008.
my problem is that sometimes, the file is append to itself another date.
example : instead of "log09032008" i get this "log0903200809032008".
my config file look like this :

<appender name="GeneralLog" type="log4net.Appender.RollingFileAppender">	
	<file value="c:\log" />	
	<rollingStyle value="Date" />
	<appendToFile value="true" />
	<datePattern value="yyyyMMdd"/>
      <staticLogFileName value="false" />
      <layout type="log4net.Layout.PatternLayout">
        <conversionPattern value="%date [%thread] %-5level %logger
[%property{NDC}] -    message%newline"/>
      </layout>
    </appender>

thanks
--

-- 
View this message in context: http://www.nabble.com/RollingFileAppender-BUG...-tp15931291p15931291.html
Sent from the Log4net - Dev mailing list archive at Nabble.com.

Re: RollingFileAppender BUG...

A couple other people have experienced this in the past too, usually because they're using the
MinimalLock. Is another process trying to interact with the log file while you're writing to it? Are you
using ASP.Net?

----- Original Message ----
From: rockom <rockom <at> gmail.com>
To: log4net-dev <at> logging.apache.org
Sent: Sunday, March 9, 2008 10:34:38 AM
Subject: RollingFileAppender BUG...

Hi
my log file is configured to be : log09032008.
my problem is that sometimes, the file is append to itself another date.
example : instead of "log09032008" i get this "log0903200809032008".
my config file look like this :

<appender name="GeneralLog" type="log4net.Appender.RollingFileAppender">    
    <file value="c:\log" />    
    <rollingStyle value="Date" />
    <appendToFile value="true" />
    <datePattern value="yyyyMMdd"/>
      <staticLogFileName value="false" />
      <layout type="log4net.Layout.PatternLayout">
        <conversionPattern value="%date [%thread] %-5level %logger
[%property{NDC}] -    message%newline"/>
      </layout>
    </appender>

thanks
--

-- 

Re: RollingFileAppender BUG...

[jira] Created: (LOG4NET-144) Attempted to append to closed appender named <appenderName>.

Attempted to append to closed appender named <appenderName>.
------------------------------------------------------------

                 Key: LOG4NET-144
                 URL: https://issues.apache.org/jira/browse/LOG4NET-144
             Project: Log4net
          Issue Type: Bug
          Components: Appenders
    Affects Versions: 1.2.10
         Environment: .net 2.0, WinXP, VS2005
            Reporter: Andreas Aigner
            Priority: Critical

using following conifg-file:

<?xml version="1.0" encoding="utf-8" ?>
<!-- 
		.log4net configuration file	
-->
<configuration>
  <!-- This section contains the log4net configuration settings -->
   <log4net debug="true">
    <!-- Define some output appenders -->
    <appender name="ConsoleAppender" type="log4net.Appender.ConsoleAppender">
      <layout type="log4net.Layout.PatternLayout">
        <conversionPattern value="%date [%thread] %-5level %logger [%property{Auftrag}] -
%message%newline" />
      </layout>
    </appender>

    <appender name="BufferingForwardingAppender"
type="log4net.Appender.BufferingForwardingAppender" >
      <filter type="log4net.Filter.LevelRangeFilter">
        <levelMin value="INFO" />
        <levelMax value="FATAL" />
      </filter>
      <bufferSize value="5"/>
      <appender-ref ref="ConsoleAppender" />
    </appender>

    <!-- Setup the logger category, add the appenders and set the default priority -->

    <logger name="testLogger1">
      <additivity value="false" />
      <level value="DEBUG" />
      <appender-ref ref="BufferingForwardingAppender" />
    </logger>

   <logger name="testLogger2">
      <additivity value="false" />
      <level value="INFO" />
      <appender-ref ref="BufferingForwardingAppender" />
    </logger>

  </log4net>
</configuration>

all messages from testlogger1 and testLogger2 appear on the Console.
After deleting this section:

  <logger name="testLogger2">
      <additivity value="false" />
      <level value="INFO" />
      <appender-ref ref="BufferingForwardingAppender" />
    </logger>

this ErrorCode appear on the console:

log4net:ERROR [BufferingForwardingAppender] Attempted to append to closed appender named [BufferingForwardingAppender].

--

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

[jira] Updated: (LOG4NET-144) Attempted to append to closed appender named <appenderName>.

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

Andreas Aigner updated LOG4NET-144:
-----------------------------------

    Attachment: log4net.config

> Attempted to append to closed appender named <appenderName>.
> ------------------------------------------------------------
>
>                 Key: LOG4NET-144
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-144
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: .net 2.0, WinXP, VS2005
>            Reporter: Andreas Aigner
>            Priority: Critical
>         Attachments: log4net.config
>
>
> using following conifg-file:
> <?xml version="1.0" encoding="utf-8" ?>
> <!-- 
> 		.log4net configuration file	
> -->
> <configuration>
>   <!-- This section contains the log4net configuration settings -->
>    <log4net debug="true">
>     <!-- Define some output appenders -->
>     <appender name="ConsoleAppender" type="log4net.Appender.ConsoleAppender">
>       <layout type="log4net.Layout.PatternLayout">
>         <conversionPattern value="%date [%thread] %-5level %logger [%property{Auftrag}] -
%message%newline" />
>       </layout>
>     </appender>
>     <appender name="BufferingForwardingAppender"
type="log4net.Appender.BufferingForwardingAppender" >
>       <filter type="log4net.Filter.LevelRangeFilter">
>         <levelMin value="INFO" />
>         <levelMax value="FATAL" />
>       </filter>
>       <bufferSize value="5"/>
>       <appender-ref ref="ConsoleAppender" />
>     </appender>
>     <!-- Setup the logger category, add the appenders and set the default priority -->
>     <logger name="testLogger1">
>       <additivity value="false" />
>       <level value="DEBUG" />
>       <appender-ref ref="BufferingForwardingAppender" />
>     </logger>
>    <logger name="testLogger2">
>       <additivity value="false" />
>       <level value="INFO" />
>       <appender-ref ref="BufferingForwardingAppender" />
>     </logger>
>   </log4net>
> </configuration>
> all messages from testlogger1 and testLogger2 appear on the Console.
> After deleting this section:
>   <logger name="testLogger2">
>       <additivity value="false" />
>       <level value="INFO" />
>       <appender-ref ref="BufferingForwardingAppender" />
>     </logger>
> this ErrorCode appear on the console:
> log4net:ERROR [BufferingForwardingAppender] Attempted to append to closed appender named [BufferingForwardingAppender].

--

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

[GUMP <at> vmgump]: Project logging-log4net (in module logging-log4net) failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at general <at> gump.apache.org.

Project logging-log4net has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 194 runs.
The current state of this project is 'Failed', with reason 'Build Timed Out'.
For reference only, the following projects are affected by this:
    - logging-log4net :  Logging framework for .NET.

Full details are available at:
    http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -INFO- Failed with reason build timed out

The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/gump_work/build_logging-log4net_logging-log4net.html
Work Name: build_logging-log4net_logging-log4net (Type: Build)
Work ended in a state of : Failed
Elapsed: 60 mins
Command Line: NAnt.exe -D:java.awt.headless=true
-D:gump.merge=/srv/gump/public/gump/work/merge.xml -D:build.sysclasspath=only
-buildfile:log4net.build 
[Working Directory: /srv/gump/public/workspace/logging-log4net]
DEVPATH: 
---------------------------------------------
  at log4net.LogManager.GetLogger (System.Reflection.Assembly,string) <0x0001c>
  at log4net.LogManager.GetLogger (System.Type) <0x00029>
  at NAnt.Console.ConsoleStub..cctor () <0x0001c>
  at (wrapper runtime-invoke) System.Object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

	/usr/bin/cli [0x818f7de]
	/usr/bin/cli [0x8171c4b]
	[0xffffe440]
	/usr/bin/cli [0x8108fa8]
	/usr/bin/cli(mono_method_signature+0x22) [0x8109279]
	/usr/bin/cli [0x80d1c8b]
	/usr/bin/cli [0x8171a51]
	/usr/bin/cli(mono_runtime_invoke+0x27) [0x80b038f]
	/usr/bin/cli(mono_runtime_class_init+0x3e6) [0x80b3999]
	/usr/bin/cli [0x8171292]
	/usr/bin/cli [0x81714fd]
	/usr/bin/cli [0x81715f7]
	/usr/bin/cli(mono_compile_method+0x3b) [0x80b0c1d]
	/usr/bin/cli [0x808f552]
	[0xb7bee032]
	[0xb6fefd28]
	[0xb6fefcce]
	[0xb6fefbea]
	[0xb6fef9a2]
	[0xb7427e85]
	[0xb7426752]
	[0xb74261b5]
	[0xb742610e]
	/usr/bin/cli [0x8171aaf]
	/usr/bin/cli(mono_runtime_invoke+0x27) [0x80b038f]
	/usr/bin/cli(mono_runtime_class_init+0x3e6) [0x80b3999]
	/usr/bin/cli [0x8171a81]
	/usr/bin/cli(mono_runtime_invoke+0x27) [0x80b038f]
	/usr/bin/cli(mono_runtime_exec_main+0x109) [0x80b4b9b]
	/usr/bin/cli(mono_runtime_run_main+0x27e) [0x80b4e84]
	/usr/bin/cli(mono_jit_exec+0xbd) [0x805a55b]
	/usr/bin/cli [0x805a638]
	/usr/bin/cli(mono_main+0x1666) [0x805be3c]
	/usr/bin/cli [0x80596c6]
	/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7d43ebc]
	/usr/bin/cli [0x8059621]

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/rss.xml
- Atom: http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 33010010032008, vmgump:vmgump-public:33010010032008
Gump E-mail Identifier (unique within run) #2.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

RE: [GUMP <at> vmgump]: Project logging-log4net (in module logging-log4net) failed

Hey,

Anyone happen to know if an upgrade of Mono or NAnt was done prior to this
failure?

Gert

-----Original Message-----
From: carnold <at> apache.org [mailto:carnold <at> apache.org] 
Sent: maandag 10 maart 2008 10:03
To: log4net-dev <at> logging.apache.org
Subject: [GUMP <at> vmgump]: Project logging-log4net (in module logging-log4net)
failed

To whom it may engage...

This is an automated request, but not an unsolicited one. For more
information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general <at> gump.apache.org.

Project logging-log4net has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 194 runs.
The current state of this project is 'Failed', with reason 'Build Timed
Out'.
For reference only, the following projects are affected by this:
    - logging-log4net :  Logging framework for .NET.

Full details are available at:

http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/index.h
tml

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were
provided:
 -INFO- Failed with reason build timed out

The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/gump_wo
rk/build_logging-log4net_logging-log4net.html
Work Name: build_logging-log4net_logging-log4net (Type: Build) Work ended in
a state of : Failed
Elapsed: 60 mins
Command Line: NAnt.exe -D:java.awt.headless=true
-D:gump.merge=/srv/gump/public/gump/work/merge.xml
-D:build.sysclasspath=only -buildfile:log4net.build [Working Directory:
/srv/gump/public/workspace/logging-log4net]
DEVPATH: 
---------------------------------------------
  at log4net.LogManager.GetLogger (System.Reflection.Assembly,string)
<0x0001c>
  at log4net.LogManager.GetLogger (System.Type) <0x00029>
  at NAnt.Console.ConsoleStub..cctor () <0x0001c>
  at (wrapper runtime-invoke) System.Object.runtime_invoke_void
(object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

	/usr/bin/cli [0x818f7de]
	/usr/bin/cli [0x8171c4b]
	[0xffffe440]
	/usr/bin/cli [0x8108fa8]
	/usr/bin/cli(mono_method_signature+0x22) [0x8109279]
	/usr/bin/cli [0x80d1c8b]
	/usr/bin/cli [0x8171a51]
	/usr/bin/cli(mono_runtime_invoke+0x27) [0x80b038f]
	/usr/bin/cli(mono_runtime_class_init+0x3e6) [0x80b3999]
	/usr/bin/cli [0x8171292]
	/usr/bin/cli [0x81714fd]
	/usr/bin/cli [0x81715f7]
	/usr/bin/cli(mono_compile_method+0x3b) [0x80b0c1d]
	/usr/bin/cli [0x808f552]
	[0xb7bee032]
	[0xb6fefd28]
	[0xb6fefcce]
	[0xb6fefbea]
	[0xb6fef9a2]
	[0xb7427e85]
	[0xb7426752]
	[0xb74261b5]
	[0xb742610e]
	/usr/bin/cli [0x8171aaf]
	/usr/bin/cli(mono_runtime_invoke+0x27) [0x80b038f]
	/usr/bin/cli(mono_runtime_class_init+0x3e6) [0x80b3999]
	/usr/bin/cli [0x8171a81]
	/usr/bin/cli(mono_runtime_invoke+0x27) [0x80b038f]
	/usr/bin/cli(mono_runtime_exec_main+0x109) [0x80b4b9b]
	/usr/bin/cli(mono_runtime_run_main+0x27e) [0x80b4e84]
	/usr/bin/cli(mono_jit_exec+0xbd) [0x805a55b]
	/usr/bin/cli [0x805a638]
	/usr/bin/cli(mono_main+0x1666) [0x805be3c]
	/usr/bin/cli [0x80596c6]
	/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7d43ebc]
	/usr/bin/cli [0x8059621]

=================================================================
Got a SIGABRT while executing native code. This usually indicates a fatal
error in the mono runtime or one of the native libraries used by your
application.
=================================================================

---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS:
http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/rss.xml
- Atom:
http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/atom.xm
l

============================== Gump Tracking Only === Produced by Gump
version 2.3.
Gump Run 33010010032008, vmgump:vmgump-public:33010010032008
Gump E-mail Identifier (unique within run) #2.

--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

Re: [GUMP <at> vmgump]: Project logging-log4net (in module logging-log4net) failed

On Mon, 10 Mar 2008, Gert Driesen <gert.driesen <at> telenet.be> wrote:

> Anyone happen to know if an upgrade of Mono or NAnt was done prior
> to this failure?

We should be building against a hand-installed Mono 1.2.4, but I see
there also is a system installed mono 1.2.3 on vmgump.  I don't recall
installing it and it may have been a side-effect of anybody else doing
an apt-get upgrade.

I will remove the system installed one and we'll see whether it fixes
the problem.

Stefan

Re: [GUMP <at> vmgump]: Project logging-log4net (in module logging-log4net) failed

On Tue, 11 Mar 2008, Stefan Bodewig <bodewig <at> apache.org> wrote:

On Mon, 10 Mar 2008, Gert Driesen <gert.driesen <at> telenet.be> wrote:

>> Anyone happen to know if an upgrade of Mono or NAnt was done prior
>> to this failure?
> 
> We should be building against a hand-installed Mono 1.2.4, but I see
> there also is a system installed mono 1.2.3 on vmgump.  I don't
> recall installing it and it may have been a side-effect of anybody
> else doing an apt-get upgrade.

Given how short the list for apt-get upgrade is, this has probably
been done pretty recently.

> I will remove the system installed one and we'll see whether it
> fixes the problem.

Well, I can't do so easily because mono is required by the system
installed nant that is used to build log4net.

I don't recall the details of why we are using a system installed NAnt
instead of the Gump built one, Curt was the one behind it IIRC.

Stefan

Re: RollingFileAppender BUG...

hi 
first i am using asp.net.
second' i tried to set the staticLogFileName property to true but then the
file does not append the date

Ron Grabowski wrote:
> 
> A couple other people have experienced this in the past too, usually
> because they're using the MinimalLock. Is another process trying to
> interact with the log file while you're writing to it? Are you using
> ASP.Net?
> 
> ----- Original Message ----
> From: rockom <rockom <at> gmail.com>
> To: log4net-dev <at> logging.apache.org
> Sent: Sunday, March 9, 2008 10:34:38 AM
> Subject: RollingFileAppender BUG...
> 
> 
> Hi
> my log file is configured to be : log09032008.
> my problem is that sometimes, the file is append to itself another date.
> example : instead of "log09032008" i get this "log0903200809032008".
> my config file look like this :
> 
> <appender name="GeneralLog" type="log4net.Appender.RollingFileAppender">    
>     <file value="c:\log" />    
>     <rollingStyle value="Date" />
>     <appendToFile value="true" />
>     <datePattern value="yyyyMMdd"/>
>       <staticLogFileName value="false" />
>       <layout type="log4net.Layout.PatternLayout">
>         <conversionPattern value="%date [%thread] %-5level %logger
> [%property{NDC}] -    message%newline"/>
>       </layout>
>     </appender>
> 
> 
> thanks
> -- 
> View this message in context:
> http://www.nabble.com/RollingFileAppender-BUG...-tp15931291p15931291.html
> Sent from the Log4net - Dev mailing list archive at Nabble.com.
> 
> 
> 
> 
> 
> 

--

-- 
View this message in context: http://www.nabble.com/RollingFileAppender-BUG...-tp15931291p15975667.html
Sent from the Log4net - Dev mailing list archive at Nabble.com.