Mike Barry (JIRA | 30 Mar 22:49 2015
Picon

[jira] [Commented] (LOG4NET-437) LogicalThreadContext data does not flow properly using Async and Await


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

Mike Barry commented on LOG4NET-437:
------------------------------------

Build fails in code from github. The files do not exist: https://github.com/jabbera/log4net/tree/trunk/src/log4net/Config

1>CSC : error CS2001: Source file 'Config\AliasDomainAttribute.cs' could not be found
1>CSC : error CS2001: Source file 'Config\DomainAttribute.cs' could not be found
1>CSC : error CS2001: Source file 'Config\DOMConfigurator.cs' could not be found
1>CSC : error CS2001: Source file 'Config\DOMConfiguratorAttribute.cs' could not be found

> LogicalThreadContext data does not flow properly using Async and Await
> ----------------------------------------------------------------------
>
>                 Key: LOG4NET-437
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-437
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.9, 1.2.10, 1.2.11, 1.2.12, 1.2.13
>         Environment: Windows 7, .NET 4.5
>            Reporter: Mike Barry
>         Attachments: LogicalThreadContext.diff, Program.cs, ThreadContextStacks.diff
>
>
> LogicalThreadContext doesn't work properly when using Async and Await. The current NDC call stack gets
(Continue reading)

Stefan Bodewig (JIRA | 30 Mar 18:11 2015
Picon

[jira] [Resolved] (LOG4NET-71) Reorganise source repository to support multiple src projects


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

Stefan Bodewig resolved LOG4NET-71.
-----------------------------------
    Resolution: Fixed

the reshuffling has been completed many months ago, right now the last open issue before being able to cut a
release is API docs.

> Reorganise source repository to support multiple src projects
> -------------------------------------------------------------
>
>                 Key: LOG4NET-71
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-71
>             Project: Log4net
>          Issue Type: Task
>            Reporter: Nicko Cadell
>            Assignee: Stefan Bodewig
>             Fix For: 1.3.0
>
>
> The log4net source code repository needs to be updated to allow multiple projects under the src folder.
Currently the source for the log4net assembly is directly in the src folder.
> A better structure would be:
> src/
>     log4net/
>     log4net.Tests/
>     log4net.Experimental/
(Continue reading)

Stefan Bodewig (JIRA | 30 Mar 13:14 2015
Picon

[jira] [Commented] (LOG4NET-442) ReconnectOnError


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

Stefan Bodewig commented on LOG4NET-442:
----------------------------------------

FAQ added with svn revision 1670054

> ReconnectOnError 
> -----------------
>
>                 Key: LOG4NET-442
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-442
>             Project: Log4net
>          Issue Type: Bug
>          Components: Builds
>    Affects Versions: 1.2.13
>         Environment: Microsoft .NET 4.5
>            Reporter: Alessio Sanguineti
>         Attachments: log4net.txt
>
>
> Hello, in our .NET application using Log4Net to log on a Sql Server 2014 database, we set the parameter
"ReconnectOnError" to true in the ADO.Net Appender configuration. 
> Even if the property seems to be read correctly (as visible on the log), whenever the server is not
reachable for a while the appender does not reconnect anymore thus not logging anything else.
> We get the log file attached of a test where we turned off SQL Server for about 1 minute before restarting it.
> Thank you.
(Continue reading)

Stefan Bodewig (JIRA | 30 Mar 13:07 2015
Picon

[jira] [Resolved] (LOG4NET-441) FAQ should have Q&A about initialization


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

Stefan Bodewig resolved LOG4NET-441.
------------------------------------
    Resolution: Fixed

added the suggested FAQ with svn revision 1670051 will update the site soon.

> FAQ should have Q&A about initialization
> ----------------------------------------
>
>                 Key: LOG4NET-441
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-441
>             Project: Log4net
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 1.2.13
>            Reporter: jrv
>            Priority: Minor
>              Labels: documentation
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> I set up a sample application to try out log4net but nothing happened. I had linked the assembly, called the
methods and set up the config, but I neither called one of the configurators nor included one of the
configurator attributes. While in retrospect it's stupid on my part, it also seems to be a common cry for
help (search "log4net not working"). The FAQ Q&A (under troubleshooting) could be something like:
> Q: Why isn't log4net working at all?
(Continue reading)

Stefan Bodewig (JIRA | 30 Mar 12:21 2015
Picon

[jira] [Resolved] (LOG4NET-438) SmtpAppender not working


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

Stefan Bodewig resolved LOG4NET-438.
------------------------------------
    Resolution: Not a Problem

> SmtpAppender not working
> ------------------------
>
>                 Key: LOG4NET-438
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-438
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.13
>         Environment: Windows 7, Visual Studio 2013, ASP.Net 4.5.2
>            Reporter: Jeff Armbruster
>            Priority: Blocker
>              Labels: newbie
>
> SendBuffer and SendEmail are never called.
> I've tried many different configurations.
> Here's my setup.
> My config:
>     <appender name="SmtpAppender" type="log4net.Appender.SmtpAppender">
>       <to value=""******** />
>       <from value="jeff <at> apexenergetics.com" />
>       <subject value="test logging message" />
(Continue reading)

Stefan Bodewig (JIRA | 30 Mar 12:21 2015
Picon

[jira] [Commented] (LOG4NET-438) SmtpAppender not working


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

Stefan Bodewig commented on LOG4NET-438:
----------------------------------------

You put the appender into "lossy" mode but don't specify an Evaluator - with this setting messages will
never get sent.  http://logging.apache.org/log4net/release/sdk/log4net.Appender.BufferingAppenderSkeleton.Lossy.html

> SmtpAppender not working
> ------------------------
>
>                 Key: LOG4NET-438
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-438
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.13
>         Environment: Windows 7, Visual Studio 2013, ASP.Net 4.5.2
>            Reporter: Jeff Armbruster
>            Priority: Blocker
>              Labels: newbie
>
> SendBuffer and SendEmail are never called.
> I've tried many different configurations.
> Here's my setup.
> My config:
>     <appender name="SmtpAppender" type="log4net.Appender.SmtpAppender">
(Continue reading)

Stefan Bodewig (JIRA | 30 Mar 12:02 2015
Picon

[jira] [Commented] (LOG4NET-442) ReconnectOnError


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

Stefan Bodewig commented on LOG4NET-442:
----------------------------------------

should we close this as "Won't fix" ("Not a Problem" is not appropriate IMHO) and add an entry to the FAQ?

> ReconnectOnError 
> -----------------
>
>                 Key: LOG4NET-442
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-442
>             Project: Log4net
>          Issue Type: Bug
>          Components: Builds
>    Affects Versions: 1.2.13
>         Environment: Microsoft .NET 4.5
>            Reporter: Alessio Sanguineti
>         Attachments: log4net.txt
>
>
> Hello, in our .NET application using Log4Net to log on a Sql Server 2014 database, we set the parameter
"ReconnectOnError" to true in the ADO.Net Appender configuration. 
> Even if the property seems to be read correctly (as visible on the log), whenever the server is not
reachable for a while the appender does not reconnect anymore thus not logging anything else.
> We get the log file attached of a test where we turned off SQL Server for about 1 minute before restarting it.
> Thank you.
(Continue reading)

Stefan Bodewig (JIRA | 30 Mar 11:37 2015
Picon

[jira] [Commented] (LOG4NET-344) Make AdoNetAppender not to stuck application process


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

Stefan Bodewig commented on LOG4NET-344:
----------------------------------------

For some reason we've all forgotten there already is an AsyncAppender inside log4net's examples. 
Furthermore there is an implementation using TPL in LOG4NET-407.

The existing example code seems to be similar to Ron's suggestion (it doesn't perform any bulk processing,
but I'd rather see async and buffering/forwarding as two separate issues anyway.  Right now I'm leaning
towards adding AsyncAppender to log4net's core using either the existing example code or Tom's
implementation for .NET < 4.0 and the TPL version for .NET >= 4.0.

Tests would be good :-)

> Make AdoNetAppender not to stuck application process
> ----------------------------------------------------
>
>                 Key: LOG4NET-344
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-344
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 1.2.10
>         Environment: Windows series
>            Reporter: Tom Tang
>              Labels: patch
(Continue reading)

Stefan Bodewig (JIRA | 30 Mar 11:21 2015
Picon

[jira] [Commented] (LOG4NET-412) Millisecond always return 0 in wince


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

Stefan Bodewig commented on LOG4NET-412:
----------------------------------------

I've found the code you use in
http://blog.opennetcf.com/ctacke/archives/ms-Resolution%20DateTime.pdf - unfortunately the
license of that code is totally unclear to me.

> Millisecond always return 0 in wince 
> -------------------------------------
>
>                 Key: LOG4NET-412
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-412
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.3.0
>         Environment: NETCF
>            Reporter: Son Tran
>            Priority: Trivial
>              Labels: DateTime,
>
> As I check the DateTime.Ticks is used in function AbsoluteTimeDateFormatter.FormatDate always return 0
> work around by using Enviroment.TichCount.

--
(Continue reading)

Stefan Bodewig (JIRA | 30 Mar 11:05 2015
Picon

[jira] [Resolved] (LOG4NET-443) Logger.CallAppenders


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

Stefan Bodewig resolved LOG4NET-443.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

implemented the try/finally workaround mentioned in Andrii Chabykins post with svn revision 1670018

> Logger.CallAppenders
> --------------------
>
>                 Key: LOG4NET-443
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-443
>             Project: Log4net
>          Issue Type: Bug
>    Affects Versions: 1.2.13
>         Environment: Windows service implemented with .NET 4.5  using Log4Net 1.2.13 on Windows 2008 R2
>            Reporter: Calin Pavel
>            Priority: Critical
>             Fix For: 1.3.0
>
>         Attachments: log4net.xml
>
>
> I do have an .NET application (Windows Service) that collects data from a lot of sources (DBs, log files,
machines event logs, ...) and uses Log4Net to log details of the actions / execution.  As expected, I'm
using a high number of threads to collect data, threads that are writing logs in some files (RollingFileAppenderer).
(Continue reading)

Stefan Bodewig (JIRA | 30 Mar 10:37 2015
Picon

[jira] [Comment Edited] (LOG4NET-437) LogicalThreadContext data does not flow properly using Async and Await


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

Stefan Bodewig edited comment on LOG4NET-437 at 3/30/15 8:37 AM:
-----------------------------------------------------------------

Sorry, when I opened LOG4NET-455 I completely forgot about this one.  Could you please verify the fix
applied for LOG4NET-455 works for your application as well?

was (Author: bodewig):
Sorry, when I opened LOG4NET-456 I completely forgot about this one.  Could you please verify the fix
applied for LOG4NET-456 works for your application as well?

> LogicalThreadContext data does not flow properly using Async and Await
> ----------------------------------------------------------------------
>
>                 Key: LOG4NET-437
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-437
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.9, 1.2.10, 1.2.11, 1.2.12, 1.2.13
>         Environment: Windows 7, .NET 4.5
>            Reporter: Mike Barry
>         Attachments: LogicalThreadContext.diff, Program.cs, ThreadContextStacks.diff
>
>
> LogicalThreadContext doesn't work properly when using Async and Await. The current NDC call stack gets
(Continue reading)


Gmane