And while I have your attention, I noticed that we released the
log4net NuGet package for 1.2.10 as 1.2.10, but 1.2.11 and 1.2.12
were 2.0.0 and 2.0.1, respectively. 1.2.12 was then re-released as
2.0.2. Since I've only been with Apache Logging since the spring and
I'm completely new to
Thanks to everyone for the good wishes and I'm looking forward to working with
you all.
From: Harry Martyrossian <hmartyross...@msn.com>
Sent: 05 February 2017 17:54:11
To: Log4NET Dev
Subject: RE: [ANN] New Committer Joe
Welcome to the team, Joe!
Wi
er support for logging from an Appender
On 2016-10-21, Joe wrote:
> From within DoAppend, there is a flag m_recursiveGuard which should
> prevent re-entrancy problems from a synchronous appender's Append
> method. For an asynchronous appender there would need to be an
> additional check sin
I just had a quick look through the commits since 1.2.15 and I don't see
anything that looks particularly risky.
I'd vote for cutting an RC.
-Original Message-
From: Stefan Bodewig [mailto:bode...@apache.org]
Sent: 06 November 2016 11:14
To: log4net-dev@logging.apache.org
Subject:
I think it's much easier to discuss something concrete, so I've put up an
incomplete version of the AsyncAppenderSkeleton I envisage on the following
branch:
https://github.com/JJoe2/log4net/tree/wip/AsyncAppender
I would appreciate it if you could review this and let me know if you're happy
> A long time ago I had started a reimplementation of the RollingFileAppender
> because we've seen that we cannot fix it without breaking compatibility or
> redefining its features. Most of the
> issues related to the RollingFileAppender should be marked as related issues
> to the rewrite
> If you are willing to help, please join log4net's dev mailing list and raise
> your hand. Look through log4net's issue tracker and pick things you'd like to
> work on. If you don't know where to start, please ask, Dominik and Stefan
> will be there to help.
> If there is anything holding you
I think the answer is probably yes: a FileAppender owns an IDisposable Stream,
and other appenders probably own IDisposable objects.
I would suggest having AppenderSkeleton implement IDisposable, rather than
IAppender. The Dispose method would call OnClose.
I also notice that AppenderSkeleton
I would like to be able to log events from within an appender. I've always
been surprised there isn't more support for this. Obviously to avoid
re-entrancy, an appender must ignore events it generated itself, and should not
generate events before log4net has been successfully configured.
to arms
Hi Joe,
good to read you and welcome on the dev list! You're free to work on issues
that attract your attention. Nobody's going to force you to work on things you
don't deem to be worth the effort.
We've already decided to gradually drop official support for ancient .net
frameworks
into another appender that must
not care about locking because the buffering appender already does. If one
knows that locking/buffering is not needed because his application does no
multithreading at all, he could still configure the other appender all alone.
2016-11-02 20:55 GMT+01:00 Joe
<jocu
I have some ideas for developing a new AsyncAppenderSkeleton, based on recent
experience developing a custom async appender that sends logging events to a
Web API.
My current thoughts are:
1. A new base class AsyncAppenderSkeleton that can be configured to work
in synchronous mode
bably be able to operate asynchronously
> or synchronously and change mode of operation based on a configuration flag
> "Asynchronous=True"
That's exactly what I had in mind.
Joe
Joe created LOG4NET-397:
---
Summary: Conflicts due to new strong name key
Key: LOG4NET-397
URL: https://issues.apache.org/jira/browse/LOG4NET-397
Project: Log4net
Issue Type: Bug
Reporter
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe updated LOG4NET-397:
Description:
Consider an application that uses two third-party assemblies:
- AssemblyA from Supplier A, compiled
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789039#comment-13789039
]
Joe commented on LOG4NET-397:
-
... it may be time to learn about the GAC
1. I know about
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789065#comment-13789065
]
Joe commented on LOG4NET-397:
-
... if a third party library uses log4net and another third
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789073#comment-13789073
]
Joe commented on LOG4NET-397:
-
Using a privatePath attribute on a probing element in your
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789105#comment-13789105
]
Joe commented on LOG4NET-397:
-
So far I had assumed you had no influence on the suppliers
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790118#comment-13790118
]
Joe commented on LOG4NET-397:
-
IMHO your FAQ should provide more detailed information
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790265#comment-13790265
]
Joe commented on LOG4NET-397:
-
@dominik - I get the impression from your comments that you
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790315#comment-13790315
]
Joe commented on LOG4NET-397:
-
@Dominik, no offence taken. My opinion, as you'll have
Joe created LOG4NET-511:
---
Summary: API to flush appenders
Key: LOG4NET-511
URL: https://issues.apache.org/jira/browse/LOG4NET-511
Project: Log4net
Issue Type: Wish
Components: Appenders
Joe created LOG4NET-512:
---
Summary: Thread safety issue in Hierarchy.cs
Key: LOG4NET-512
URL: https://issues.apache.org/jira/browse/LOG4NET-512
Project: Log4net
Issue Type: Bug
Components
[
https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849790#comment-15849790
]
Joe commented on LOG4NET-551:
-
Stefan, when using DebugFormat, the message in the LoggingEvent
[
https://issues.apache.org/jira/browse/LOG4NET-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849761#comment-15849761
]
Joe commented on LOG4NET-551:
-
This probably has the same root cause as LOG4NET-550.
A workaround would
Joe created LOG4NET-550:
---
Summary: Logging recursively from an Appender not supported for
NET_4_0 and MONO_4_0
Key: LOG4NET-550
URL: https://issues.apache.org/jira/browse/LOG4NET-550
Project: Log4net
[
https://issues.apache.org/jira/browse/LOG4NET-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15641314#comment-15641314
]
Joe commented on LOG4NET-256:
-
I would suggest it could be resolved as "Cannot reproduce".
If th
[
https://issues.apache.org/jira/browse/LOG4NET-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15640035#comment-15640035
]
Joe commented on LOG4NET-281:
-
Surely adding an ILog2 interface and a LogManager.GetLogger2 method to return
[
https://issues.apache.org/jira/browse/LOG4NET-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650727#comment-15650727
]
Joe commented on LOG4NET-531:
-
[~lanorkin] from the stack trace I would say there is am unhandled exception
[
https://issues.apache.org/jira/browse/LOG4NET-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650645#comment-15650645
]
Joe commented on LOG4NET-531:
-
It's probably a threading bug in your custom appender.
I believe
[
https://issues.apache.org/jira/browse/LOG4NET-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15640560#comment-15640560
]
Joe commented on LOG4NET-256:
-
I'm not sure this is XP related.
The bug description doesn't explain how
[
https://issues.apache.org/jira/browse/LOG4NET-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15640578#comment-15640578
]
Joe commented on LOG4NET-264:
-
I can't see anything in the current source code that uses
[
https://issues.apache.org/jira/browse/LOG4NET-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe updated LOG4NET-526:
Description:
A common requirement is to be able to define a base directory for log files
that can be used
[
https://issues.apache.org/jira/browse/LOG4NET-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15581186#comment-15581186
]
Joe commented on LOG4NET-511:
-
[~bodewig] - it occurs to me that it would have been better to implement
35 matches
Mail list logo
