You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/04/04 22:30:07 UTC
[jira] [Updated] (LOG4NET-632) UDPAppender does not work when
configured by file under .net core
[ https://issues.apache.org/jira/browse/LOG4NET-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers updated LOG4NET-632:
--------------------------------
LOG4NET is now dormant.
> UDPAppender does not work when configured by file under .net core
> -----------------------------------------------------------------
>
> Key: LOG4NET-632
> URL: https://issues.apache.org/jira/browse/LOG4NET-632
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.0.8
> Environment: OS Name: Microsoft Windows 10 Enterprise
> OS Version: 10.0.17763 N/A Build 17763
> OS Manufacturer: Microsoft Corporation
> OS Configuration: Member Workstation
> OS Build Type: Multiprocessor Free
> Hotfix(s): 9 Hotfix(s) Installed.
> [01]: KB4495590
> [02]: KB4470788
> [03]: KB4480056
> [04]: KB4489907
> [05]: KB4493478
> [06]: KB4493510
> [07]: KB4497932
> [08]: KB4499728
> [09]: KB4494441
> Reporter: Keith Henderson
> Priority: Major
> Attachments: SampleApplication.zip
>
>
> I have run across an issue with the UDP appender where it acts differently depending upon how the system is configured.
>
> Attached is 2 sample programs (one zip file). One targets .net 4.7.2 and the other targets .net core 2.1. Each program has 2 methods in it called testByFile and testProgrammatically. Also included in the zip is the log4net.config file I used with both programs.
>
> I would expect all 4 methods to behave the same since my programmatic configuration matches the file. When configured by file, the core application does not log to the UDP appender. I have verified this by looking at wireshark while the program is running. The UDP Appender works as expected for the other 3 configuration methods.
>
> Obviously the work around is to configure log4net programmatically. My question is why does this one case fail though? I would expect to be able to go to .net core and still use a config file.
>
> Any help you can provide would be greatly appreciated.
> Keith Henderson
--
This message was sent by Atlassian Jira
(v8.3.4#803005)