Nabble - Log4net - Dev

Re: Debugging log4net source

2009-11-09T08:38:17Z

I can happily confirm that this version is working great:

It is both debuggable, and compatible with existing assemblies that reference it.

Ron - thank you very very much!

Omer.

On Mon, Nov 9, 2009 at 1:09 AM, Ron Grabowski <rongrabowski@...> wrote:

I've contacted Omer off list to have him verify the .pdb file. If its correct I'll publish it somewhere.

From: Omer Mor <omer.mor@...>
To: Log4NET Dev <log4net-dev@...>
Sent: Mon, October 19, 2009 1:09:24 AM

Subject: Re: Debugging log4net source

Thanks!

On Mon, Oct 19, 2009 at 5:04 AM, Ron Grabowski <rongrabowski@...> wrote:

I emailed Nicko asking him what I need to do to get the .snk file onto my system. It looks like the version in source control is encrypted.

From: Omer Mor <omer.mor@...>
To: Log4NET Dev <log4net-dev@...>

Sent: Wed, October 7, 2009 9:01:18 AM

Subject: Re: Debugging log4net source

I'm trying again to get some help from the log4net developers community:
I really need to get a release build with pdb.
I explained blow exactly what needs to be changed in the nant script to build it this way.

It should only take a couple of minutes to do this.
I would have done it myself if the assembly signing key would have been public.
Maybe if no one is free to compile it, then I could join the log4net dev team, and get permission to access the signing key?

Thanks in advance,
  Omer Mor.

On Wed, Aug 26, 2009 at 5:01 PM, Omer Mor <omer.mor@...> wrote:

Thanks.
First - you should change the nant script:
In the file <root>\log4net.include line 171 should be changed from:

   <property name="build.debug" value="false" />

to:
   <property name="build.debug" value="pdbonly" />
then just run the build script (build.cmd) and the release folder (<root>\bin\net\2.0\release\) should contain both the dll and pdb files.

I suggest making the change in the nant script permanent as it does not affect performance and allows for debugging into log4net source.

Thanks in advance,

  Omer Mor.

On Wed, Aug 26, 2009 at 5:41 AM, Ron Grabowski <rongrabowski@...> wrote:

Tell me the exact nant command line to run and I'll run it.

From: Omer Mor <omer.mor@...>

To: Log4NET Dev <log4net-dev@...>
Sent: Sunday, August 23, 2009 11:49:03 AM
Subject: Re: Debugging log4net source

I would like to ask again the developer community of log4net for a signed build of 1.2.10 assembly that was compiled with a PDB file.
This is the best way for us to enable live debugging of the log4net source.

I believe it would only take a couple of minutes to compile it this way, and it would help us tremendously.

Thanks again,
  Omer Mor (omer.mor@...)

On Fri, Aug 7, 2009 at 12:44 PM, Omer Mor <omer.mor@...> wrote:

I prefer debugging the situation live.
Is it so hard to re-compile 1.2.10 with pdb? It's just a matter of a slight tweak in the project settings.

On Fri, Aug 7, 2009 at 6:12 AM, Ron Grabowski <rongrabowski@...> wrote:

Have you tried specifying a custom error handler on the appender to track down when it enters a failed state?

<appender name=".." >
...
<errorHandler type="Your.ErrorHandler, YourAssembly" />
</appender>

You would write one that sends an email when the file can't be created.

From: Omer Mor <omer.mor@...>
To: log4net-dev@...

Sent: Thursday, August 6, 2009 3:02:17 AM
Subject: Debugging log4net source

Hi,
to research a (rare) bug we have with log4net (log file is not being created) we wanted to debug its source.
However, the release build of 1.2.10 is supplied without a pdb file.
And since it is a signed assembly we can't compile it ourself and replace it.
Also - the debug build of 1.2.10 is supplied with a pdb, but is not signed, so it is not substitutable.
What I'd like to ask is that one of the developers compile a release build of 1.2.10 and enable pdb creation, so that we could debug the source.

Using a non-signed copy of log4net is not an option for us, because some of our 3rd-party assemblies are compiled against the signed 1.2.10 log4net assembly.

The files could be sent irectly to me at omer.mor@... .

Thanks in advance,
Omer Mor.

[jira] Commented: (LOG4NET-64) [PATCH] to RollingFileAppender.cs to add the ability to preserve the log file name extension when rolling the log file.

2009-11-08T23:35:32Z

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

Hakan Lindestaf commented on LOG4NET-64:
----------------------------------------

I have an issue with this issue, some of the files are still named in the old format.
Here's what my directory output looks like:
Volume in drive C has no label.
Volume Serial Number is 7057-2FE1

Directory of C:\inetpub\wwwroot\KickService\Logs

11/09/2009 08:32 AM <DIR> .
11/09/2009 08:32 AM <DIR> ..
11/09/2009 07:56 AM 12,822 Service.log
10/28/2009 11:27 PM 748,549 Service.log20091028
10/29/2009 10:30 PM 738,261 Service.log20091029
11/05/2009 10:42 PM 819,465 Service.log20091105
11/06/2009 11:20 PM 873,142 Service.log20091106
11/07/2009 02:42 PM 148,499 Service.log20091107
11/08/2009 09:06 PM 81,809 Service.log20091108
10/16/2009 10:51 PM 586,003 Service20091016.log
10/20/2009 10:51 PM 654,559 Service20091020.log
10/21/2009 10:46 PM 848,594 Service20091021.log
10/22/2009 10:57 PM 6,586,212 Service20091022.log
10/25/2009 11:51 PM 264,567 Service20091025.log
10/26/2009 11:54 PM 908,770 Service20091026.log
10/27/2009 11:53 PM 426,759 Service20091027.log
10/30/2009 11:54 PM 456,209 Service20091030.log
10/31/2009 11:54 PM 26,600 Service20091031.log
11/01/2009 11:54 PM 153,698 Service20091101.log
11/02/2009 11:48 PM 1,194,835 Service20091102.log
11/03/2009 11:59 PM 2,587,370 Service20091103.log
11/04/2009 11:56 PM 846,138 Service20091104.log
11/09/2009 08:32 AM 0 x.x
21 File(s) 18,962,861 bytes
2 Dir(s) 32,061,755,392 bytes free

See how there is a mix of the output formats. I haven't had a chance to look thru the code yet. I'm running log4net from svn trunk. Here's my config:
<appender name="RollingLogFileAppender" type="log4net.Appender.RollingFileAppender">
<file value="C:\Inetpub\wwwroot\Service\Logs\Service.log"/>
<appendToFile value="true"/>
<maxSizeRollBackups value="30"/>
<rollingStyle value="Date"/>
<staticLogFileName value="true"/>
<datePattern value="yyyyMMdd"/>
<preserveLogFileNameExtension value="true"/>
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%date [%property{SessionId}] %-5level %logger [%property{NDC}] - %message%newline"/>
</layout>
</appender>

> [PATCH] to RollingFileAppender.cs to add the ability to preserve the log file name extension when rolling the log file.
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4NET-64
> URL: https://issues.apache.org/jira/browse/LOG4NET-64
> Project: Log4net
> Issue Type: New Feature
> Components: Appenders
> Affects Versions: 1.2.9
> Reporter: Joshua Bassett
> Assignee: Ron Grabowski
> Fix For: 1.2.11
>
> Attachments: LOG4NET-64.patch, LOG4NET-64.patch, patch.txt
>
>
> Normally, when the log file is rolled the file name extension is not preserved.
> For example, file.log is rolled to file.log.1 or file.log.yyyy-MM-dd.
> However, this may not be desired in all cases and it may be necessary to preserve the log file name extension when the log file is rolled. Most notably, this feature is useful for maintaining file associations under Windows so that all log files can be associated with a particaular text viewer.
> For example, file.log is rolled to file.1.log or file.yyyy-MM-dd.log.
> This patch adds an additional boolean property PreserveLogFileNameExtension to the RollingFileAppender class which is used to toggle this behavior.

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

[jira] Issue Comment Edited: (LOG4NET-64) [PATCH] to RollingFileAppender.cs to add the ability to preserve the log file name extension when rolling the log file.

2009-11-08T23:35:32Z

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

Hakan Lindestaf edited comment on LOG4NET-64 at 11/9/09 7:35 AM:
-----------------------------------------------------------------

I have a problem with this issue, some of the files are still named in the old format.
Here's what my directory output looks like:
Volume in drive C has no label.
Volume Serial Number is 7057-2FE1

Directory of C:\inetpub\wwwroot\KickService\Logs

11/09/2009 08:32 AM <DIR> .
11/09/2009 08:32 AM <DIR> ..
11/09/2009 07:56 AM 12,822 Service.log
10/28/2009 11:27 PM 748,549 Service.log20091028
10/29/2009 10:30 PM 738,261 Service.log20091029
11/05/2009 10:42 PM 819,465 Service.log20091105
11/06/2009 11:20 PM 873,142 Service.log20091106
11/07/2009 02:42 PM 148,499 Service.log20091107
11/08/2009 09:06 PM 81,809 Service.log20091108
10/16/2009 10:51 PM 586,003 Service20091016.log
10/20/2009 10:51 PM 654,559 Service20091020.log
10/21/2009 10:46 PM 848,594 Service20091021.log
10/22/2009 10:57 PM 6,586,212 Service20091022.log
10/25/2009 11:51 PM 264,567 Service20091025.log
10/26/2009 11:54 PM 908,770 Service20091026.log
10/27/2009 11:53 PM 426,759 Service20091027.log
10/30/2009 11:54 PM 456,209 Service20091030.log
10/31/2009 11:54 PM 26,600 Service20091031.log
11/01/2009 11:54 PM 153,698 Service20091101.log
11/02/2009 11:48 PM 1,194,835 Service20091102.log
11/03/2009 11:59 PM 2,587,370 Service20091103.log
11/04/2009 11:56 PM 846,138 Service20091104.log
11/09/2009 08:32 AM 0 x.x
21 File(s) 18,962,861 bytes
2 Dir(s) 32,061,755,392 bytes free

See how there is a mix of the output formats. I haven't had a chance to look thru the code yet. I'm running log4net from svn trunk. Here's my config:
<appender name="RollingLogFileAppender" type="log4net.Appender.RollingFileAppender">
<file value="C:\Inetpub\wwwroot\Service\Logs\Service.log"/>
<appendToFile value="true"/>
<maxSizeRollBackups value="30"/>
<rollingStyle value="Date"/>
<staticLogFileName value="true"/>
<datePattern value="yyyyMMdd"/>
<preserveLogFileNameExtension value="true"/>
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%date [%property{SessionId}] %-5level %logger [%property{NDC}] - %message%newline"/>
</layout>
</appender>

was (Author: hakanl):
I have an issue with this issue, some of the files are still named in the old format.
Here's what my directory output looks like:
Volume in drive C has no label.
Volume Serial Number is 7057-2FE1

Directory of C:\inetpub\wwwroot\KickService\Logs

11/09/2009 08:32 AM <DIR> .
11/09/2009 08:32 AM <DIR> ..
11/09/2009 07:56 AM 12,822 Service.log
10/28/2009 11:27 PM 748,549 Service.log20091028
10/29/2009 10:30 PM 738,261 Service.log20091029
11/05/2009 10:42 PM 819,465 Service.log20091105
11/06/2009 11:20 PM 873,142 Service.log20091106
11/07/2009 02:42 PM 148,499 Service.log20091107
11/08/2009 09:06 PM 81,809 Service.log20091108
10/16/2009 10:51 PM 586,003 Service20091016.log
10/20/2009 10:51 PM 654,559 Service20091020.log
10/21/2009 10:46 PM 848,594 Service20091021.log
10/22/2009 10:57 PM 6,586,212 Service20091022.log
10/25/2009 11:51 PM 264,567 Service20091025.log
10/26/2009 11:54 PM 908,770 Service20091026.log
10/27/2009 11:53 PM 426,759 Service20091027.log
10/30/2009 11:54 PM 456,209 Service20091030.log
10/31/2009 11:54 PM 26,600 Service20091031.log
11/01/2009 11:54 PM 153,698 Service20091101.log
11/02/2009 11:48 PM 1,194,835 Service20091102.log
11/03/2009 11:59 PM 2,587,370 Service20091103.log
11/04/2009 11:56 PM 846,138 Service20091104.log
11/09/2009 08:32 AM 0 x.x
21 File(s) 18,962,861 bytes
2 Dir(s) 32,061,755,392 bytes free

See how there is a mix of the output formats. I haven't had a chance to look thru the code yet. I'm running log4net from svn trunk. Here's my config:
<appender name="RollingLogFileAppender" type="log4net.Appender.RollingFileAppender">
<file value="C:\Inetpub\wwwroot\Service\Logs\Service.log"/>
<appendToFile value="true"/>
<maxSizeRollBackups value="30"/>
<rollingStyle value="Date"/>
<staticLogFileName value="true"/>
<datePattern value="yyyyMMdd"/>
<preserveLogFileNameExtension value="true"/>
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%date [%property{SessionId}] %-5level %logger [%property{NDC}] - %message%newline"/>
</layout>
</appender>

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

Re: Debugging log4net source

2009-11-08T15:09:36Z

I've contacted Omer off list to have him verify the .pdb file. If its correct I'll publish it somewhere.

From: Omer Mor <omer.mor@...>
To: Log4NET Dev <log4net-dev@...>
Sent: Mon, October 19, 2009 1:09:24 AM
Subject: Re: Debugging log4net source

Thanks!

On Mon, Oct 19, 2009 at 5:04 AM, Ron Grabowski <rongrabowski@...> wrote:

I emailed Nicko asking him what I need to do to get the .snk file onto my system. It looks like the version in source control is encrypted.

From: Omer Mor <omer.mor@...>
To: Log4NET Dev <log4net-dev@...>

Sent: Wed, October 7, 2009 9:01:18 AM

Subject: Re: Debugging log4net source

I'm trying again to get some help from the log4net developers community:
I really need to get a release build with pdb.
I explained blow exactly what needs to be changed in the nant script to build it this way.

It should only take a couple of minutes to do this.
I would have done it myself if the assembly signing key would have been public.
Maybe if no one is free to compile it, then I could join the log4net dev team, and get permission to access the signing key?

Thanks in advance,
  Omer Mor.

On Wed, Aug 26, 2009 at 5:01 PM, Omer Mor <omer.mor@...> wrote:

Thanks.
First - you should change the nant script:
In the file <root>\log4net.include line 171 should be changed from:

   <property name="build.debug" value="false" />

to:
   <property name="build.debug" value="pdbonly" />
then just run the build script (build.cmd) and the release folder (<root>\bin\net\2.0\release\) should contain both the dll and pdb files.

I suggest making the change in the nant script permanent as it does not affect performance and allows for debugging into log4net source.

Thanks in advance,

  Omer Mor.

On Wed, Aug 26, 2009 at 5:41 AM, Ron Grabowski <rongrabowski@...> wrote:

Tell me the exact nant command line to run and I'll run it.

From: Omer Mor <omer.mor@...>

To: Log4NET Dev <log4net-dev@...>
Sent: Sunday, August 23, 2009 11:49:03 AM
Subject: Re: Debugging log4net source

I would like to ask again the developer community of log4net for a signed build of 1.2.10 assembly that was compiled with a PDB file.
This is the best way for us to enable live debugging of the log4net source.

I believe it would only take a couple of minutes to compile it this way, and it would help us tremendously.

Thanks again,
  Omer Mor (omer.mor@...)

On Fri, Aug 7, 2009 at 12:44 PM, Omer Mor <omer.mor@...> wrote:

I prefer debugging the situation live.
Is it so hard to re-compile 1.2.10 with pdb? It's just a matter of a slight tweak in the project settings.

On Fri, Aug 7, 2009 at 6:12 AM, Ron Grabowski <rongrabowski@...> wrote:

Have you tried specifying a custom error handler on the appender to track down when it enters a failed state?

<appender name=".." >
...
<errorHandler type="Your.ErrorHandler, YourAssembly" />
</appender>

You would write one that sends an email when the file can't be created.

From: Omer Mor <omer.mor@...>
To: log4net-dev@...

Sent: Thursday, August 6, 2009 3:02:17 AM
Subject: Debugging log4net source

Hi,
to research a (rare) bug we have with log4net (log file is not being created) we wanted to debug its source.
However, the release build of 1.2.10 is supplied without a pdb file.
And since it is a signed assembly we can't compile it ourself and replace it.
Also - the debug build of 1.2.10 is supplied with a pdb, but is not signed, so it is not substitutable.
What I'd like to ask is that one of the developers compile a release build of 1.2.10 and enable pdb creation, so that we could debug the source.

Using a non-signed copy of log4net is not an option for us, because some of our 3rd-party assemblies are compiled against the signed 1.2.10 log4net assembly.

The files could be sent irectly to me at omer.mor@... .

Thanks in advance,
Omer Mor.

[jira] Updated: (LOG4NET-237) URL Referrer Pattern Converter

2009-11-08T13:43:32Z

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

Adam Davies updated LOG4NET-237:
--------------------------------

Attachment: log4net - Url Referrer Address.zip

Created AspNetUrlReferrerPatternConverter.

Usage: %aspnet-urlreferrer

> URL Referrer Pattern Converter
> ------------------------------
>
> Key: LOG4NET-237
> URL: https://issues.apache.org/jira/browse/LOG4NET-237
> Project: Log4net
> Issue Type: New Feature
> Components: Other
> Affects Versions: 1.2.10
> Reporter: Adam Davies
> Priority: Trivial
> Fix For: 1.2.10
>
> Attachments: log4net - Url Referrer Address.zip
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Need a URL Referrer Pattern Converter to provide the referring page's URL for the current request.

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

[jira] Created: (LOG4NET-237) URL Referrer Pattern Converter

2009-11-08T13:39:32Z

URL Referrer Pattern Converter
------------------------------

Key: LOG4NET-237
URL: https://issues.apache.org/jira/browse/LOG4NET-237
Project: Log4net
Issue Type: New Feature
Components: Other
Affects Versions: 1.2.10
Reporter: Adam Davies
Priority: Trivial
Fix For: 1.2.10

Need a URL Referrer Pattern Converter to provide the referring page's URL for the current request.

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

[jira] Updated: (LOG4NET-236) Request URL PatternConverter

2009-11-08T12:47:32Z

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

Adam Davies updated LOG4NET-236:
--------------------------------

Attachment: log4net - Url Address.zip

Created AspNetUrlPatternConverter.

usage: %aspnet-url

> Request URL PatternConverter
> ----------------------------
>
> Key: LOG4NET-236
> URL: https://issues.apache.org/jira/browse/LOG4NET-236
> Project: Log4net
> Issue Type: New Feature
> Components: Other
> Affects Versions: 1.2.10
> Reporter: Adam Davies
> Priority: Trivial
> Fix For: 1.2.10
>
> Attachments: log4net - Url Address.zip
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Need an URL Pattern Converter to provide the current requested URL.

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

[jira] Created: (LOG4NET-236) Request URL PatternConverter

2009-11-08T12:45:32Z

Request URL PatternConverter
----------------------------

Key: LOG4NET-236
URL: https://issues.apache.org/jira/browse/LOG4NET-236
Project: Log4net
Issue Type: New Feature
Components: Other
Affects Versions: 1.2.10
Reporter: Adam Davies
Priority: Trivial
Fix For: 1.2.10

Need an URL Pattern Converter to provide the current requested URL.

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

[jira] Commented: (LOG4NET-235) IP Address Pattern Converter

2009-11-07T19:50:32Z

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

Adam Davies commented on LOG4NET-235:
-------------------------------------

In order to use this pattern use %aspnet-ipaddress

Example:
<appender name="DebugAppender" type="log4net.Appender.DebugAppender" >
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="User: %identity IP: %aspnet-ipaddress%newline" />
</layout>
</appender>

> IP Address Pattern Converter
> ----------------------------
>
> Key: LOG4NET-235
> URL: https://issues.apache.org/jira/browse/LOG4NET-235
> Project: Log4net
> Issue Type: New Feature
> Components: Other
> Affects Versions: 1.2.10
> Reporter: Adam Davies
> Priority: Trivial
> Fix For: 1.2.10
>
> Attachments: log4net - IP Address.zip
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Created AspNetIPAddressPatternConverter to provide the client IP Address.

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

[jira] Updated: (LOG4NET-235) IP Address Pattern Converter

2009-11-07T19:48:32Z

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

Adam Davies updated LOG4NET-235:
--------------------------------

Attachment: log4net - IP Address.zip

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

[jira] Created: (LOG4NET-235) IP Address Pattern Converter

2009-11-07T19:46:32Z

IP Address Pattern Converter
----------------------------

Key: LOG4NET-235
URL: https://issues.apache.org/jira/browse/LOG4NET-235
Project: Log4net
Issue Type: New Feature
Components: Other
Affects Versions: 1.2.10
Reporter: Adam Davies
Priority: Trivial
Fix For: 1.2.10

Created AspNetIPAddressPatternConverter to provide the client IP Address.

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

[jira] Updated: (LOG4NET-154) Add a StackTracePatternConverter to display method calls leading up to log message

2009-11-07T16:44:32Z

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

Adam Davies updated LOG4NET-154:
--------------------------------

Attachment: log4net - StackTrace and StackTraceDetail.zip

> Add a StackTracePatternConverter to display method calls leading up to log message
> ----------------------------------------------------------------------------------
>
> Key: LOG4NET-154
> URL: https://issues.apache.org/jira/browse/LOG4NET-154
> Project: Log4net
> Issue Type: New Feature
> Reporter: Ron Grabowski
> Fix For: 1.2.11
>
> Attachments: log4net - StackTrace and StackTraceDetail.zip, StackTracePatternConverter.zip
>
>
> Modify LocationInfo to save StackTrace information and make it available as StackTracePatternConverter to display call stack leading up to the log message:
> log.Debug("Item Saved");
>
> [%stackTrace{3}] %message%newline
> [default_aspx.btnSubmit_Click > productController.Save > productService.Save] Item Saved
> This will probably be a slow pattern converter on par with other LocationInfo derived pattern converters.

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

[jira] Commented: (LOG4NET-154) Add a StackTracePatternConverter to display method calls leading up to log message

2009-11-07T16:40:32Z

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

Adam Davies commented on LOG4NET-154:
-------------------------------------

I have further extended the functionality of the StackTracePatternConverter to allow the selection of min / max frames.

Given: %message%exception%stacktrace{MAX|MIN}

Explantion: {MAX|MIN}
The MAX controls how deep to display the stacktrace. MAX displays the first n of the stacktrace from the top item
(stacktrace[0] to stacktrace[n])
Any int >= 0 will only allow the first x
The MIN is optional. MIN sets the number of stacktrace items to skip from stacktrace[0]
If MIN is greater than the number of stacktrace items, then no stacktrace will be displayed.

Example: %stacktrace{3}, displays stacktrace[2] > stacktrace[1] > stacktrace[0]
Example: %stacktrace{5}, displays stacktrace[4] > stacktrace[3] > stacktrace[2] > stacktrace[1] > stacktrace[0]
Example: %stacktrace{3|1}, displays stacktrace[2] > stacktrace[1]
Example: %stacktrace{-1}, displays stacktrace[n] > stacktrace[n-1] > ... > stacktrace[1] > stacktrace[0]
Example: %stacktrace{-1|3}, displays stacktrace[n] > stacktrace[n-1] > ... > stacktrace[4] > stacktrace[3]

In addition I have created a new pattern StackTraceDetailPatternConverter. This pattern inherits from StackTracePatternConverter, and provides parameter information for each method.

Given: %message%exception%stacktracedetail{MAX|MIN}

Example: %stacktrace{3}, displays stacktrace[2](type param, ...) > stacktrace[1](type param, ...) > stacktrace[0](type param, ...)
Example: %stacktrace{3|1}, displays stacktrace[2](type param, ...) > stacktrace[1](type param, ...)

> Add a StackTracePatternConverter to display method calls leading up to log message
> ----------------------------------------------------------------------------------
>
> Key: LOG4NET-154
> URL: https://issues.apache.org/jira/browse/LOG4NET-154
> Project: Log4net
> Issue Type: New Feature
> Reporter: Ron Grabowski
> Fix For: 1.2.11
>
> Attachments: StackTracePatternConverter.zip
>
>
> Modify LocationInfo to save StackTrace information and make it available as StackTracePatternConverter to display call stack leading up to the log message:
> log.Debug("Item Saved");
>
> [%stackTrace{3}] %message%newline
> [default_aspx.btnSubmit_Click > productController.Save > productService.Save] Item Saved
> This will probably be a slow pattern converter on par with other LocationInfo derived pattern converters.

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

LoggingEvent Fix property

2009-11-06T14:13:09Z

Hello

In my company we are using an AsyncAppender for asynchronous logging that we have implemented ourselves and we are quite happy with it. From the start we had prepared a FixFields property on this appender so that user can decide which fields has to be fixed by the appender before passing it to nested appenders. The default value for this property is Partial.

I recently try to use it so that most of the logging event formatting is done in the logging thread rather than in the thread that generate the log event. So I change the FixFields value to ThreadName and discovered that it has an impact on the job performed by nested appenders. For instance when I log an exception through a ConsoleAppender nested in a AsyncAppender I have normally the following result:

ERROR Exception raised
System.ApplicationException: FOO
à AsyncAppenderTest.Program.ThrowException() dans C:\Dev\AsyncAppenderTest\AsyncAppenderTest\Program.cs:ligne 69
à AsyncAppenderTest.Program.Main(String[] args) dans C:\Dev\AsyncAppenderTest\AsyncAppenderTest\Program.cs:ligne 40

Once I changed the FixFields to simply ThreadName I had:

ERROR Exception raised

As you can see the log of the exception has disappeared. This is so with or without the %exception in the PatternLayout.

The problem is in the LoggingEvent class. It looks like you cannot partially fix a LoggingEvent. Once you fix some fields using the Fix property m_cacheUpdatable is set to false and when the LoggingEvent reference is pass to the ConsoleAppender which call GetExceptionString this method return an empty string because m_cacheUpdatable is false. What is m_cacheUpdatable for exactly ? It looks like the intention is to avoid the same field to be fixed several time but as all fields default value in LoggingEventData is null and is not null anymore once fixed it seems enough to avoid the multiple fixes situation. Couldn't be LoggingEvent.m_cacheUpdatable simply removed ?

Thanks

[jira] Created: (LOG4NET-234) RollingFileAppender generates incorrect file name

2009-10-28T10:33:59Z

RollingFileAppender generates incorrect file name
-------------------------------------------------

Key: LOG4NET-234
URL: https://issues.apache.org/jira/browse/LOG4NET-234
Project: Log4net
Issue Type: Bug
Components: Appenders
Affects Versions: 1.2.10
Environment: Windows XP, Windows 2003
Reporter: Miroslav Vanicky

I have Appender defined as follow...

<appender name="RollingFileAppender" type="log4net.Appender.RollingFileAppender" >
<file value="Logs\Log" /> 
<appendtofile value="true" />
<rollingstyle value="Date" /> 
<datepattern value="_yyyy-MM-dd.\tx\t"/> 
<StaticLogFileName value="false" /> 


<layout type="log4net.Layout.PatternLayout">
<conversionpattern value="%date [%-5level] - %message%newline"></conversionpattern>
</layout>
</appender>

This Appender should generate file names like "Log_2009-10-15.txt", mostly it works fine, but in some unknown situations it generates file named "Log_2009-10-15.txt_2009-10-15.txt". It seems to me that this happens when there were no log-files and the incorrectly named file was the first log-file generated.

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

[jira] Commented: (LOG4NET-201) Add asynchronous logging behavior

2009-10-19T18:12:59Z

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

Ron Grabowski commented on LOG4NET-201:
---------------------------------------

Here's a ~50 line BufferingForwardingAppender inspired by Ayende:

public class AsyncBufferingForwardingAppender : BufferingForwardingAppender
{
private readonly object syncLock = new object();
private readonly LinkedList<LoggingEvent[]> eventsList = new LinkedList<LoggingEvent[]>();
private bool anotherThreadAlreadyHandlesLogging;

public override void ActivateOptions()
{
base.ActivateOptions();
Fix = FixFlags.All & ~FixFlags.LocationInfo;
}

// Rhino.Commons.Logging.AsyncBulkInsertAppender#SendBuffer
protected override void SendBuffer(LoggingEvent[] events)
{
ThreadPool.QueueUserWorkItem(delegate
{
lock (syncLock)
{
eventsList.AddLast(events);
if (anotherThreadAlreadyHandlesLogging)
{
return;
}
anotherThreadAlreadyHandlesLogging = true;
}
while (true)
{
LoggingEvent[] current;
lock (syncLock)
{
if(eventsList.Count == 0)
{
anotherThreadAlreadyHandlesLogging = false;
return;
}
current = eventsList.First.Value;
eventsList.RemoveFirst();
}
SynchronousSendBuffer(current);
});
}

protected virtual void SynchronousSendBuffer(LoggingEvent[] events)
{
foreach (AppenderSkeleton appender in Appenders)
{
appender.DoAppend(events);
}
}
}

Probably needs some flush code in the Close() method too.

> Add asynchronous logging behavior
> ---------------------------------
>
> Key: LOG4NET-201
> URL: https://issues.apache.org/jira/browse/LOG4NET-201
> Project: Log4net
> Issue Type: New Feature
> Components: Core
> Environment: All
> Reporter: Jason
> Attachments: log4net_trunk.zip
>
>
> This issue was first discussed in an e-mail conversation which I'll paste here:
> -------------------------------------------------
> Hi Ron,
> I'll open a JIRA ticket for this issue.
> I've only looked at log4net briefly (an hour before I started coding - needed a quick solution), so I'm happy to hear your input.
> My less knowledgeable inputs:
> * For the hierarchy level vs the logger level, I agree that the hierarchy level seems better. I didn't realize anything about the 'hierarchy' until later today. I only added the asynchronous behavior to the logger because I mistakenly thought that was the highest level.
> * I also realized that FixFlags.All would be slow by comparison to a partial 'Fix', but I hadn't yet figured out which fields were relevant. I'm still fuzzy on this as I'm not sure how to tell which fields are required - maybe inferred from the log level? This seems to be a big issue with the async behavior since it could potentially introduce more harm than good in the current implementation.
> * ThreadSafeBlockingQueue - I'd seen mention of IBulkAppenders but didn't know anymore than what I could infer from the names. I'm guessing these receive a collection of inputs. The TSBQueue could certainly be modified. I was going to create it with generics but I'm guessing log4net doesn't use generics to provide backwards compatibility?
> I'm interested to hear about your other solution since you seem to understand the overall design well. For now I need to get my application running on top of what I have, but I might be able to lend a hand on this issue going forward.
> Jason
> On 2/17/09, Ron Grabowski wrote:
> >
> > The best place to put your code would be on a new JIRA ticket and make sure
> > to grant the ok to include into a ASF project.
> >
> > I've been thinking about a feature like this but I wanted to get the
> > remaining tickets for the next version closed out (before 4.0 comes out!!!).
> > My original plan was to Fix the events then dispatch them to another worker
> > thread as soon as they arrived so the code would return to the caller as
> > soon as possible. I was thinking more on the ILoggerRepository (Hiearchy)
> > level as opposed to an individual Logger. The Logger level definietly offers
> > more control but part of me things that people would be ok with either all
> > loggers being sync (how it is today) or all-async...allowing them to change
> > on a per Logger level might be too confusing ??? Plus if there's a Thread
> > per Logger and there are a lot of Loggers won't there be a lot of Threads
> > running? I suppose that's why you added a property on a per logger basis to
> > control which specific loggers were async.
> >
> > ThreadSafeBlockingQueue.Dequeue(Queue) could dequeue the
> > items into LoggingEvent[] to allow IBulkAppenders to better handle the
> > items.
> >
> > When ForcedLogSub is called with FixFlags.All I think a StackTrace is
> > capture (slow) even if none of the attached appenders use location
> > information. Maybe add some checks to AddAppender to make a FixFlags that is
> > All - LocationInfo.
> >
> > Its late, I have another solution that I'll write about tomorrow.
> >
> > ________________________________
> > From: Jason Aubrey
> > Sent: Tuesday, February 17, 2009 12:13:26 PM
> > Subject: Commit access requested for an asynchronous logging addition
> >
> > Hi,
> >
> > I just added a property to my working copy called 'Synchronous'. It's
> > 'true' by default to maintain the current behavior. When 'false' the logger
> > will queue log events in a thread safe queue that's serviced by a worker
> > thread.
> >
> > The goal of asynchronous logging is to reduce the amount of time incurred by
> > logging on the primary thread. This can be useful in applications such as
> > in financial trading where time is quite literally money. It's realized
> > that a data integrity risk is introduced by logging asynchronously, but this
> > is a known and acceptable risk. I added the synchronous option within the
> > logger instead of the appenders because the behavior should apply to all
> > appenders.
> >
> > The new/modified files are attached within log4net_trunk.zip. I don't
> > currently have commit access but I can commit the code if granted access.
> > There are unit tests for the new code.
> >
> > Jason Aubrey
> >

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

[jira] Created: (LOG4NET-233) Support .NET 4.0 including Client Profile

2009-10-19T17:12:59Z

Support .NET 4.0 including Client Profile
-----------------------------------------

Key: LOG4NET-233
URL: https://issues.apache.org/jira/browse/LOG4NET-233
Project: Log4net
Issue Type: New Feature
Components: Appenders, Builds, Core, Documentation, Examples, Other
Affects Versions: 1.2.11, v.Next
Environment: Windows XP, Vista, 7 - .Net 4.0
Reporter: Daniel mcGloin

Please add a release targeting .NET 4.0 (currently in Beta 2). In addition, to support the .NET 4.0 Client Profile, divide any server-side parts into a separate library set that can be optionally referenced/deployed..

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

[jira] Commented: (LOG4NET-201) Add asynchronous logging behavior

2009-10-19T15:03:59Z

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

Grant Birchmeier commented on LOG4NET-201:
------------------------------------------

So, I see lots of discussion about details here, but no resolution.

Was Ron passing the ball back to Jason? Is there anyone picking this up for inclusion into trunk? Is there a competing fix that has or will go in?

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

Re: Debugging log4net source

2009-10-18T22:09:24Z

Thanks!

On Mon, Oct 19, 2009 at 5:04 AM, Ron Grabowski <rongrabowski@...> wrote:

I emailed Nicko asking him what I need to do to get the .snk file onto my system. It looks like the version in source control is encrypted.

From: Omer Mor <omer.mor@...>
To: Log4NET Dev <log4net-dev@...>

Sent: Wed, October 7, 2009 9:01:18 AM

Subject: Re: Debugging log4net source

I'm trying again to get some help from the log4net developers community:
I really need to get a release build with pdb.
I explained blow exactly what needs to be changed in the nant script to build it this way.

It should only take a couple of minutes to do this.
I would have done it myself if the assembly signing key would have been public.
Maybe if no one is free to compile it, then I could join the log4net dev team, and get permission to access the signing key?

Thanks in advance,
  Omer Mor.

On Wed, Aug 26, 2009 at 5:01 PM, Omer Mor <omer.mor@...> wrote:

Thanks.
First - you should change the nant script:
In the file <root>\log4net.include line 171 should be changed from:

   <property name="build.debug" value="false" />

to:
   <property name="build.debug" value="pdbonly" />
then just run the build script (build.cmd) and the release folder (<root>\bin\net\2.0\release\) should contain both the dll and pdb files.

I suggest making the change in the nant script permanent as it does not affect performance and allows for debugging into log4net source.

Thanks in advance,

  Omer Mor.

On Wed, Aug 26, 2009 at 5:41 AM, Ron Grabowski <rongrabowski@...> wrote:

Tell me the exact nant command line to run and I'll run it.

From: Omer Mor <omer.mor@...>

To: Log4NET Dev <log4net-dev@...>
Sent: Sunday, August 23, 2009 11:49:03 AM
Subject: Re: Debugging log4net source

I would like to ask again the developer community of log4net for a signed build of 1.2.10 assembly that was compiled with a PDB file.
This is the best way for us to enable live debugging of the log4net source.

I believe it would only take a couple of minutes to compile it this way, and it would help us tremendously.

Thanks again,
  Omer Mor (omer.mor@...)

On Fri, Aug 7, 2009 at 12:44 PM, Omer Mor <omer.mor@...> wrote:

I prefer debugging the situation live.
Is it so hard to re-compile 1.2.10 with pdb? It's just a matter of a slight tweak in the project settings.

On Fri, Aug 7, 2009 at 6:12 AM, Ron Grabowski <rongrabowski@...> wrote:

Have you tried specifying a custom error handler on the appender to track down when it enters a failed state?

<appender name=".." >
...
<errorHandler type="Your.ErrorHandler, YourAssembly" />
</appender>

You would write one that sends an email when the file can't be created.

From: Omer Mor <omer.mor@...>
To: log4net-dev@...

Sent: Thursday, August 6, 2009 3:02:17 AM
Subject: Debugging log4net source

Hi,
to research a (rare) bug we have with log4net (log file is not being created) we wanted to debug its source.
However, the release build of 1.2.10 is supplied without a pdb file.
And since it is a signed assembly we can't compile it ourself and replace it.
Also - the debug build of 1.2.10 is supplied with a pdb, but is not signed, so it is not substitutable.
What I'd like to ask is that one of the developers compile a release build of 1.2.10 and enable pdb creation, so that we could debug the source.

Using a non-signed copy of log4net is not an option for us, because some of our 3rd-party assemblies are compiled against the signed 1.2.10 log4net assembly.

The files could be sent irectly to me at omer.mor@... .

Thanks in advance,
Omer Mor.

[jira] Commented: (LOG4NET-225) Multithreading and Deadlocks

2009-10-18T20:28:31Z

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

Ron Grabowski commented on LOG4NET-225:
---------------------------------------

Thomas, filters are processed within the recursive lock. Are you sure you need your appender to issue another log message? I suppose your appender could log to a different repository with its own appenders. That smells bad too...

> Multithreading and Deadlocks
> ----------------------------
>
> Key: LOG4NET-225
> URL: https://issues.apache.org/jira/browse/LOG4NET-225
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 1.2.10
> Reporter: Thomas Haller
> Priority: Blocker
> Attachments: Log4NetDeadlock.zip
>
>
> If an Appender has to execute some logic on another thread,
> witch uses also log4net, this leads to a deadlock.
> The sample project i created demonstrates that problem.

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

[jira] Commented: (LOG4NET-225) Multithreading and Deadlocks

2009-10-18T20:22:31Z

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

Ron Grabowski commented on LOG4NET-225:
---------------------------------------

DRIN, the problem is that you shouldn't be logging from within appenders. Is that what your appender is doing?

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

Re: Debugging log4net source

2009-10-18T20:04:22Z

I emailed Nicko asking him what I need to do to get the .snk file onto my system. It looks like the version in source control is encrypted.

From: Omer Mor <omer.mor@...>
To: Log4NET Dev <log4net-dev@...>
Sent: Wed, October 7, 2009 9:01:18 AM
Subject: Re: Debugging log4net source

I'm trying again to get some help from the log4net developers community:

I really need to get a release build with pdb.

I explained blow exactly what needs to be changed in the nant script to build it this way.

It should only take a couple of minutes to do this.

I would have done it myself if the assembly signing key would have been public.
Maybe if no one is free to compile it, then I could join the log4net dev team, and get permission to access the signing key?

Thanks in advance,

Omer Mor.

On Wed, Aug 26, 2009 at 5:01 PM, Omer Mor <omer.mor@...> wrote:

Thanks.
First - you should change the nant script:
In the file <root>\log4net.include line 171 should be changed from:

   <property name="build.debug" value="false" />

to:
   <property name="build.debug" value="pdbonly" />
then just run the build script (build.cmd) and the release folder (<root>\bin\net\2.0\release\) should contain both the dll and pdb files.

I suggest making the change in the nant script permanent as it does not affect performance and allows for debugging into log4net source.

Thanks in advance,

  Omer Mor.

On Wed, Aug 26, 2009 at 5:41 AM, Ron Grabowski <rongrabowski@...> wrote:

Tell me the exact nant command line to run and I'll run it.

From: Omer Mor <omer.mor@...>

To: Log4NET Dev <log4net-dev@...>
Sent: Sunday, August 23, 2009 11:49:03 AM
Subject: Re: Debugging log4net source

I would like to ask again the developer community of log4net for a signed build of 1.2.10 assembly that was compiled with a PDB file.
This is the best way for us to enable live debugging of the log4net source.

I believe it would only take a couple of minutes to compile it this way, and it would help us tremendously.

Thanks again,
  Omer Mor (omer.mor@...)

On Fri, Aug 7, 2009 at 12:44 PM, Omer Mor <omer.mor@...> wrote:

I prefer debugging the situation live.
Is it so hard to re-compile 1.2.10 with pdb? It's just a matter of a slight tweak in the project settings.

On Fri, Aug 7, 2009 at 6:12 AM, Ron Grabowski <rongrabowski@...> wrote:

Have you tried specifying a custom error handler on the appender to track down when it enters a failed state?

<appender name=".." >
...
<errorHandler type="Your.ErrorHandler, YourAssembly" />
</appender>

You would write one that sends an email when the file can't be created.

From: Omer Mor <omer.mor@...>
To: log4net-dev@...

Sent: Thursday, August 6, 2009 3:02:17 AM
Subject: Debugging log4net source

Hi,
to research a (rare) bug we have with log4net (log file is not being created) we wanted to debug its source.
However, the release build of 1.2.10 is supplied without a pdb file.
And since it is a signed assembly we can't compile it ourself and replace it.
Also - the debug build of 1.2.10 is supplied with a pdb, but is not signed, so it is not substitutable.
What I'd like to ask is that one of the developers compile a release build of 1.2.10 and enable pdb creation, so that we could debug the source.

Using a non-signed copy of log4net is not an option for us, because some of our 3rd-party assemblies are compiled against the signed 1.2.10 log4net assembly.

The files could be sent irectly to me at omer.mor@... .

Thanks in advance,
Omer Mor.

[jira] Created: (LOG4NET-232) Use ReaderWriterLockSlim instead of ReaderWriterLock.

2009-10-16T16:47:31Z

Use ReaderWriterLockSlim instead of ReaderWriterLock.
-----------------------------------------------------

Key: LOG4NET-232
URL: https://issues.apache.org/jira/browse/LOG4NET-232
Project: Log4net
Issue Type: Improvement
Affects Versions: 1.2.10
Environment: Any
Reporter: Aron Weiler
Priority: Minor

ReaderWriterLock should be replaced with ReaderWriterLockSlim according to Microsoft for performance and simplification reasons.

MSDN: http://msdn.microsoft.com/en-us/library/system.threading.readerwriterlock.aspx

The .NET Framework has two reader-writer locks, ReaderWriterLockSlim and ReaderWriterLock. ReaderWriterLockSlim is recommended for all new development. ReaderWriterLockSlim is similar to ReaderWriterLock, but it has simplified rules for recursion and for upgrading and downgrading lock state. ReaderWriterLockSlim avoids many cases of potential deadlock. In addition, the performance of ReaderWriterLockSlim is significantly better than ReaderWriterLock.

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

Re: Building for .Net 3.5

2009-10-16T14:52:14Z

Never mind I was using NAnt .85 when I should have been using .86.

Thanks,
Jon

From: Jon Shuler <jonshuler@...>
To: log4net-dev@...
Sent: Fri, October 16, 2009 4:29:10 PM
Subject: Building for .Net 3.5

I am trying to use the trunk versions of log4net.build and log4net.include to build. I am using the build command "build.cmd compile-net3.5". I get the following error:

BUILD FAILED

D:\_dev\CSP_DEV_1.0_Iteration_4\Server\DotNetShared\ThirdParty\log4net\1.2.10\log4net.include(231,8):
Target framework could not be changed. "net-3.0" is not a valid framework identifier. Valid values are: netcf-2.0, net-2.0, net-1.1.

Any ideas?

Thanks,
Jon

Building for .Net 3.5

2009-10-16T14:29:10Z

Re: Debugging log4net source

2009-10-07T06:01:18Z

I'm trying again to get some help from the log4net developers community:

I really need to get a release build with pdb.

I explained blow exactly what needs to be changed in the nant script to build it this way.

It should only take a couple of minutes to do this.

Thanks in advance,

Omer Mor.

On Wed, Aug 26, 2009 at 5:01 PM, Omer Mor <omer.mor@...> wrote:

Thanks.
First - you should change the nant script:
In the file <root>\log4net.include line 171 should be changed from:

   <property name="build.debug" value="false" />

to:
   <property name="build.debug" value="pdbonly" />
then just run the build script (build.cmd) and the release folder (<root>\bin\net\2.0\release\) should contain both the dll and pdb files.

I suggest making the change in the nant script permanent as it does not affect performance and allows for debugging into log4net source.

Thanks in advance,

  Omer Mor.

On Wed, Aug 26, 2009 at 5:41 AM, Ron Grabowski <rongrabowski@...> wrote:

Tell me the exact nant command line to run and I'll run it.

From: Omer Mor <omer.mor@...>

To: Log4NET Dev <log4net-dev@...>
Sent: Sunday, August 23, 2009 11:49:03 AM
Subject: Re: Debugging log4net source

I would like to ask again the developer community of log4net for a signed build of 1.2.10 assembly that was compiled with a PDB file.
This is the best way for us to enable live debugging of the log4net source.

I believe it would only take a couple of minutes to compile it this way, and it would help us tremendously.

Thanks again,
  Omer Mor (omer.mor@...)

On Fri, Aug 7, 2009 at 12:44 PM, Omer Mor <omer.mor@...> wrote:

I prefer debugging the situation live.
Is it so hard to re-compile 1.2.10 with pdb? It's just a matter of a slight tweak in the project settings.

On Fri, Aug 7, 2009 at 6:12 AM, Ron Grabowski <rongrabowski@...> wrote:

Have you tried specifying a custom error handler on the appender to track down when it enters a failed state?

<appender name=".." >
...
<errorHandler type="Your.ErrorHandler, YourAssembly" />
</appender>

You would write one that sends an email when the file can't be created.

From: Omer Mor <omer.mor@...>
To: log4net-dev@...

Sent: Thursday, August 6, 2009 3:02:17 AM
Subject: Debugging log4net source

Hi,
to research a (rare) bug we have with log4net (log file is not being created) we wanted to debug its source.
However, the release build of 1.2.10 is supplied without a pdb file.
And since it is a signed assembly we can't compile it ourself and replace it.
Also - the debug build of 1.2.10 is supplied with a pdb, but is not signed, so it is not substitutable.
What I'd like to ask is that one of the developers compile a release build of 1.2.10 and enable pdb creation, so that we could debug the source.

Using a non-signed copy of log4net is not an option for us, because some of our 3rd-party assemblies are compiled against the signed 1.2.10 log4net assembly.

The files could be sent irectly to me at omer.mor@... .

Thanks in advance,
Omer Mor.

Appender for ASP.NET web interface

2009-10-02T17:00:19Z

Hello,

I've been working on an Ajax/Comet interface for pushing logging information into a separate tab of the browser. So
far it's still more or less in alpha, but it's functional and functioning fairly well in a couple of projects I've been doing at
work. It basically works by juggling piping the logging information through an open HttpRequest, which writes
<script> tags to a hidden IFRAME. Script on the front end drops the logs into a table, which is limited to a set
number of rows.

Users just see a table with all the recent log entries, which get updated live and rotated out when they're old.

The implementation isn't suitable for a web farm, unfortunately.

It's been useful at work because it's easy to set up and doesn't require additional access to fileshares or databases in
order to see the logging information.

Unfortunately, I don't have a host which supports IIS or mod_mono, so I don't have publicly available demo for it.
(Though I might be able to pass off a link to a staging installation in private).

I was going to post the code up at SourceForge in order to share it out with other developers who might want to
use it, but I thought I would pass it by you kind folk to see if you'd consider it as a viable inclusion in your project. Or
maybe it grows up a bit on SourceForge before getting included later on?

If you want the code, I can pack it up and send it to someone, or check it in to somewhere. Let me know.

Thanks,

-d

[jira] Commented: (LOG4NET-231) App hangs on log attempt when non-contiguous rolling log files exist

2009-09-30T22:58:23Z

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

John Fairhall commented on LOG4NET-231:
---------------------------------------

Have tracked the issue. We have one java application running as a service that starts up our c# application. The missing backup logs were generating output on stderr, which the java app was not configured to read. As nothing was reading it's stderr, the c# app blocked.

I'd say this issue is resolved, with a further comment that it should have been straightforward to stifle the stderr output from the logger, but isn't.

> App hangs on log attempt when non-contiguous rolling log files exist
> --------------------------------------------------------------------
>
> Key: LOG4NET-231
> URL: https://issues.apache.org/jira/browse/LOG4NET-231
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 1.2.10
> Environment: Win32, Win Server 2003, C# app
> Reporter: John Fairhall
> Fix For: 1.2.11
>
>
> Application has this log4net config:
> <log4net>
> <appender name="RollingFile" type="log4net.Appender.RollingFileAppender">
> <file value="..\log\OOPCollector.log" />
> <appendToFile value="false" />
> <maximumFileSize value="5MB" />
> <maxSizeRollBackups value="5" />
> <lockingModel type="log4net.Appender.FileAppender+MinimalLock" />
> <layout type="log4net.Layout.PatternLayout">
> <conversionPattern value="%date %5level [%thread] %logger - %message%newline" />
> </layout>
> </appender>
> <root>
> <level value="INFO" />
> <appender-ref ref="RollingFile" />
> </root>
> </log4net>
> We are attemping to keep current + 5 backup logs.
> Somehow, the resulting logs for the OOPCollector app became;
> OOPCollector.log
> OOPCollector.log.5
> Starting the app with only those logs already existing causes the app to stop on a log attempt permanently.
> The OOPCollector.log.5 log dissappears but the OOPCollector.log does not get renamed to OOPCollector.log.1, and no new OOPCollector.log is created.
> The issue also occurs if the directory contains
> OOPCollector.log
> OOPCollector.log.4
> except that .4 does get renamed to .5, but otherwise same problem.
> Directory containining
> OOPCollector.log
> OOPCollector.log.3
> works as expected.
> Have set config to store 10 backups, and have same issue with OOPCollector.log and OOPCollector.log.10, and OOPCollector.log and OOPCollector.log.9.
> So looks like a fencepost error with rollover.
> We are also getting OOPCollector.<timestamp>.1, .2, .3 files in the directory occaisionally for no apparent reason.

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

[jira] Created: (LOG4NET-231) App hangs on log attempt when non-contiguous rolling log files exist

2009-09-29T17:48:32Z

App hangs on log attempt when non-contiguous rolling log files exist
--------------------------------------------------------------------

Key: LOG4NET-231
URL: https://issues.apache.org/jira/browse/LOG4NET-231
Project: Log4net
Issue Type: Bug
Components: Appenders
Affects Versions: 1.2.10
Environment: Win32, Win Server 2003, C# app
Reporter: John Fairhall
Fix For: 1.2.11

Application has this log4net config:

<log4net>
<appender name="RollingFile" type="log4net.Appender.RollingFileAppender">
<file value="..\log\OOPCollector.log" />
<appendToFile value="false" />
<maximumFileSize value="5MB" />
<maxSizeRollBackups value="5" />
<lockingModel type="log4net.Appender.FileAppender+MinimalLock" />
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%date %5level [%thread] %logger - %message%newline" />
</layout>
</appender>
<root>
<level value="INFO" />
<appender-ref ref="RollingFile" />
</root>
</log4net>

We are attemping to keep current + 5 backup logs.

Somehow, the resulting logs for the OOPCollector app became;
OOPCollector.log
OOPCollector.log.5

Starting the app with only those logs already existing causes the app to stop on a log attempt permanently.
The OOPCollector.log.5 log dissappears but the OOPCollector.log does not get renamed to OOPCollector.log.1, and no new OOPCollector.log is created.

The issue also occurs if the directory contains
OOPCollector.log
OOPCollector.log.4
except that .4 does get renamed to .5, but otherwise same problem.

Directory containining
OOPCollector.log
OOPCollector.log.3
works as expected.

Have set config to store 10 backups, and have same issue with OOPCollector.log and OOPCollector.log.10, and OOPCollector.log and OOPCollector.log.9.
So looks like a fencepost error with rollover.

We are also getting OOPCollector.<timestamp>.1, .2, .3 files in the directory occaisionally for no apparent reason.

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

Logging not happening when run on IIS using log4net

2009-09-24T11:18:56Z

I’m using an ASP.net web application, in that I’m using log4net for logging.
When I run the project, in the ASP.net development server, I’m able to log the logger statements.
But when the application is run on IIS no logging happens. My application is set as a virtual directory inside a Asp web application.

Below is my setting in webconfig.
<configuration>
<configSections>
<section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler, log4net"/>
</configSections>
<log4net>
<appender name="LogFileAppender" type="log4net.Appender.FileAppender">



<layout type="log4net.Layout.PatternLayout">

</layout>
</appender>
<appender name="SmtpAppender" type="log4net.Appender.SmtpAppender">
<to value=""/>
<from value=""/>
<subject value=""/>
<smtpHost value=""/>
<bufferSize value="512"/>
<lossy value="true"/>
<evaluator type="log4net.Core.LevelEvaluator">
<threshold value="WARN"/>
</evaluator>
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%newline%date [%thread] %-5level %logger [%property] - %message%newline%newline%newline"/>
</layout>
</appender>
<logger name="File">
<level value="All"/>
<appender-ref ref="LogFileAppender"/>
</logger>
<logger name="EmailLog">
<level value="All"/>
<appender-ref ref="SmtpAppender"/>
</logger>
</log4net>
</configuration>
In my appication start I’m using the following code

protected void Application_Start(object sender, EventArgs e)
{
log4net.Config.XmlConfigurator.Configure();
}
My C# class is as follows.

using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.IO;
using log4net;
namespace SEAIWedgeSizing.Pages
{
public partial class SizingMaster : System.Web.UI.Page

{
private ILog logger = LogManager.GetLogger("File");
protected void Page_Load(object sender, EventArgs e)
{
logger.Debug("**** Entering Class - SizingMaster :: Method - Page_Load ********");
}
}
}

Are there any seetings in IIS?

[jira] Commented: (LOG4NET-219) RollingFileAppender with varying dynamic filenames not working

2009-09-22T11:28:17Z

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

Matt Schwartz commented on LOG4NET-219:
---------------------------------------

I'm experiencing the same issue

> RollingFileAppender with varying dynamic filenames not working
> --------------------------------------------------------------
>
> Key: LOG4NET-219
> URL: https://issues.apache.org/jira/browse/LOG4NET-219
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 1.2.10
> Environment: OS: Windows Server 2003, Sharepoint 2007
> Reporter: Amar G
> Attachments: log4netinternaldebug.txt
>
>
> The Log4Net configuration file is as below:
> <log4net>
> <appender name="RollingFile" type="log4net.Appender.RollingFileAppender">
> <file type="log4net.Util.PatternString" value="C:\ErrorLog\%property{LogPath}"></file>
> <appendToFile value="true"></appendToFile>
> <maximumFileSize value="1024KB"></maximumFileSize>
> <maxSizeRollBackups value="2"></maxSizeRollBackups>
> <layout type="log4net.Layout.PatternLayout">
> <conversionpattern value="%newline%date - %message%newline"></conversionpattern>
> </layout>
> </appender>
> <logger name="File">
> <level value="All" />
> <appender-ref ref="RollingFile" />
> </logger>
> </log4net>
> In my application the debug method for logging the information will be called many times. Some messages should get stored in a file with name say xy.log and some messages should get stored in a file with name say ab.log.
> In Global.asax i have written the following code:
> log4net.Config.XmlConfigurator.ConfigureAndWatch(new System.IO.FileInfo(Server.MapPath("/Log4Net.config")));
> The above LOC is written in the Application_Start event
> Actual call to the debug method:
> log4net.GlobalContext.Properties["LogPath"] = String.Concat(FilePrefix,"_Debug.log");
> log4net.ILog filelogger = log4net.LogManager.GetLogger("File");
> filelogger.Debug(info);
> Issue: Although the property named LogPath is getting set properly, i dont see any file with the name specified through the code getting created in the path specified.
> Can you please look into this and let me know whether i am missing something or whether it is not supported?
> Thanks in advance.....

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

[jira] Commented: (LOG4NET-230) Unable to Download log4net

2009-09-22T05:12:16Z

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

Dag Christensen commented on LOG4NET-230:
-----------------------------------------

The download at http://logging.apache.org/log4net/download.html worked for me.
If you don't want to clear your browser cache, you can try download it using wget (http://gnuwin32.sourceforge.net/packages/wget.htm).
Extract bin\wget.exe and execute this command:
wget.exe http://archive.apache.org/dist/incubator/log4net/1.2.10/incubating-log4net-1.2.10.zip

> Unable to Download log4net
> ---------------------------
>
> Key: LOG4NET-230
> URL: https://issues.apache.org/jira/browse/LOG4NET-230
> Project: Log4net
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.10
> Environment: ASP.NET
> Reporter: Prince M. Premnath
> Priority: Critical
>
> Hi i Couldn't download the log4net 1.2.10 from this location http://logging.apache.org/log4net/download.html it ultimately stops at certain point after downloading 4.7 MB ive tried as many times , but still i could n't find myself successful may i have another mirror to download ?
> what ive to do in order to download ?
> Prince

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

[jira] Updated: (LOG4NET-230) Unable to Download log4net

2009-09-22T05:06:16Z

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

Prince M. Premnath updated LOG4NET-230:
----------------------------------------

Comment: was deleted

(was: Hi Dag Christensen

Even the alternate link what you've given me suffering from the same issue it seems .. i couldn't complete my download :-( where can i get it again ?)

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

[jira] Updated: (LOG4NET-230) Unable to Download log4net

2009-09-22T05:06:16Z

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

[jira] Commented: (LOG4NET-230) Unable to Download log4net

2009-09-22T05:06:16Z

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

Prince M. Premnath commented on LOG4NET-230:
---------------------------------------------

Hi Dag Christensen

Even the alternate link what you've given me suffering from the same issue it seems .. i couldn't complete my download :-( where can i get it again ?

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