reusing a task where your "x-correlation-id" was set
(if (i==3)) for other values of i, this is why you are seeing multiple
modified log outputs.
cheers,
alex
On Fri, Apr 7, 2017 at 10:04 AM, Dominik Psenner (JIRA)
mailto:j...@apache.org>> wrote:
[
https://issues
[
https://issues.apache.org/jira/browse/LOG4NET-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960445#comment-15960445
]
Dominik Psenner commented on LOG4NET-562:
-
Have you tried to include the ac
[
https://issues.apache.org/jira/browse/LOG4NET-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958776#comment-15958776
]
Dominik Psenner commented on LOG4NET-562:
-
To me this works as designed.
[
https://issues.apache.org/jira/browse/LOG4NET-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958370#comment-15958370
]
Dominik Psenner commented on LOG4NET-555:
-
This may be among the reasons:
[
https://issues.apache.org/jira/browse/LOG4NET-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947044#comment-15947044
]
Dominik Psenner edited comment on LOG4NET-552 at 3/29/17 12:4
[
https://issues.apache.org/jira/browse/LOG4NET-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947044#comment-15947044
]
Dominik Psenner commented on LOG4NET-552:
-
1. I couldn't find the log4
[
https://issues.apache.org/jira/browse/LOG4NET-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944804#comment-15944804
]
Dominik Psenner commented on LOG4NET-552:
-
1. This changes the current beha
[
https://issues.apache.org/jira/browse/LOG4NET-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927616#comment-15927616
]
Dominik Psenner commented on LOG4NET-552:
-
I'm unsure whether we can ju
[
https://issues.apache.org/jira/browse/LOG4NET-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925680#comment-15925680
]
Dominik Psenner commented on LOG4NET-559:
-
Looks like
[
https://issues.apache.org/jira/browse/LOG4NET-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner reassigned LOG4NET-559:
---
Assignee: Dominik Psenner
> Custom Appender throws exception to user when I
[
https://issues.apache.org/jira/browse/LOG4NET-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925675#comment-15925675
]
Dominik Psenner commented on LOG4NET-552:
-
Rolling by date with mult
[
https://issues.apache.org/jira/browse/LOG4NET-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925675#comment-15925675
]
Dominik Psenner edited comment on LOG4NET-552 at 3/15/17 7:3
h 2017 at 04:29, Mikael Ståldal
> wrote:
>
>> I think that a vast majority of our users only uses one of the languages
>> we support, and therefore only are interested in one of the subprojects.
>>
>> On Fri, Mar 10, 2017 at 11:23 AM, Dominik Psenner w
>> rote:
keeping the user’s
lists separate isn’t likely to be an issue as most of the things
that would need to be discussed would be on a dev list anyway.
Ralph
On Mar 9, 2017, at 2:45 AM, Dominik Psenner mailto:dpsen...@gmail.com>> wrote:
The votes are way too scattered ov
rs: +1
Stefan Bodewig: +1
Sven Rautenverg: -1
Thorsten Schöning: -0
Ivan Habunek: -0
Dominik Psenner: +1
Remko Popma: +1
Mikael Ståldal: +0
Totals so far:
+1: 5
+0: 1
-0: 2
-1: 1
log4j-user@, log4php-user@, log4net-user@, log4cxx-user@, general@
->u...@logging.apache.org
Matt Sicker: -1
Ralph
Of course, this is just something I've noticed while clicking through
the site and it is definitely not a blocker for 2.0.8.
On 2017-03-09 09:13, Stefan Bodewig wrote:
On 2017-03-08, Dominik Psenner wrote:
I am looking through the release and am going to give a few feedbacks
during the
Assemblies work, checksums match.
+1
On 2017-03-08 19:52, Stefan Bodewig wrote:
Hi all
log4net 2.0.8 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/logging/log4net
(revision 18620)
Details of changes since 2.0.7 are in the release notes:
https://stefan.samaf
The site and rat report look good, going to test the nuget binary tomorrow.
On 8 Mar 2017 9:39 p.m., "Dominik Psenner" wrote:
> I am looking through the release and am going to give a few feedbacks
> during the next hour. The first thing i noticed is this:
>
> The website
I am looking through the release and am going to give a few feedbacks
during the next hour. The first thing i noticed is this:
The website page 'features' still mentions that log4net has builds for
ancient .net framework versions. We should change that.
On 8 Mar 2017 7:52 p.m., "Stefan Bodewig"
[
https://issues.apache.org/jira/browse/LOG4NET-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901686#comment-15901686
]
Dominik Psenner commented on LOG4NET-557:
-
Is this not a duplicate of LOG
*hm*
Rereading the patch its probably safe to just apply the patch [1] and
check if all the unittests pass.
[1]
https://issues.apache.org/jira/secure/attachment/12852105/log4net-DebugAppenderCategory3.patch
On 2017-03-07 10:42, Stefan Bodewig wrote:
On 2017-03-06, Dominik Psenner wrote
The codereview of 553 is fine and includes reasonable unittests. The
regression tests for all supported framework targets is the bottleneck here.
On 6 Mar 2017 12:20 p.m., "Stefan Bodewig" wrote:
On 2017-03-06, Dominik Psenner wrote:
> Testing and applying the patch for LOG4NET
Hi Stefan,
Testing and applying the patch for LOG4NET-553 is on my todo, but can't
see when I can free the spare time to actually get it done.
Cheers
On 2017-03-06 10:27, Stefan Bodewig wrote:
Hi all
apart from the LockRecursionException Joe has fixed, we probably should
also bring back sup
[
https://issues.apache.org/jira/browse/LOG4NET-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872182#comment-15872182
]
Dominik Psenner commented on LOG4NET-554:
-
Interesting, I look forward seei
[
https://issues.apache.org/jira/browse/LOG4NET-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862874#comment-15862874
]
Dominik Psenner commented on LOG4NET-553:
-
Finally had the time to read thr
[
https://issues.apache.org/jira/browse/LOG4NET-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861461#comment-15861461
]
Dominik Psenner edited comment on LOG4NET-553 at 2/10/17 4:0
[
https://issues.apache.org/jira/browse/LOG4NET-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861461#comment-15861461
]
Dominik Psenner commented on LOG4NET-553:
-
Largely agreed, I would fur
[
https://issues.apache.org/jira/browse/LOG4NET-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861228#comment-15861228
]
Dominik Psenner commented on LOG4NET-553:
-
I have a mixed feeling about
[
https://issues.apache.org/jira/browse/LOG4NET-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859322#comment-15859322
]
Dominik Psenner commented on LOG4NET-553:
-
I just reviewed your patch an
[
https://issues.apache.org/jira/browse/LOG4NET-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858031#comment-15858031
]
Dominik Psenner commented on LOG4NET-553:
-
Would you like to write a patch
[
https://issues.apache.org/jira/browse/LOG4NET-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857585#comment-15857585
]
Dominik Psenner commented on LOG4NET-553:
-
Hi!
Thanks for the patch. Whi
[
https://issues.apache.org/jira/browse/LOG4NET-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856040#comment-15856040
]
Dominik Psenner commented on LOG4NET-552:
-
1. If you need a fix soon, pl
Hi joe,
Glad to welcome you among us!
Cheers
On 6 Feb 2017 10:43 a.m., "Joe" wrote:
Thanks to everyone for the good wishes and I'm looking forward to working
with you all.
--
*From:* Harry Martyrossian
*Sent:* 05 February 2017 17:54:11
*To:* Log4NET Dev
*Subject:*
Interesting. I dont mind the spam unless i have to look at all the content
to filter the spam manually. Can i safely mark everything as read or is
there anything i have to catch up with?
On 17 Jan 2017 9:54 p.m., "Stefan Bodewig" wrote:
> Hi
>
> there's been a cycle where a mailer daemon respond
[
https://issues.apache.org/jira/browse/LOG4NET-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-543.
---
Resolution: Not A Bug
Assignee: Dominik Psenner
Thanks for reporting this issue
Welcome to the list, marty! Here we go, feel free to start discussions.
On 6 Jan 2017 8:17 a.m., "HMartyrossian" wrote:
Github user HMartyrossian commented on the issue:
https://github.com/apache/log4net/pull/40
@bodewig: Thank you very much, Stefan, for your prompt answer! I did
subsc
Great! All in all this is a clear
+1
from Italy.
On 2016-12-22 14:04, Stefan Bodewig wrote:
On 2016-12-22, Dominik Psenner wrote:
A question about the .net core support:
according to the documentation, .net remoting is not available with
.net standard 1.3. Would that mean too that the
Just finished the tests and the binaries work for me. This means that
the functionality is there but we have to discuss if the license issue
is a showstopper before I can cast my vote.
Cheers
On 2016-12-20 11:07, Stefan Bodewig wrote:
Hi all
log4net 2.0.6 RC1 is available for review here:
Gotcha at http://stefan.samaflost.de/staging/log4net-2.0.6/license.html
{quote}
Copyright [] [name of copyright owner]
{quote
We should replace the placeholders.
On 2016-12-20 11:07, Stefan Bodewig wrote:
Hi all
log4net 2.0.6 RC1 is available for review here:
https://dist.apache.or
A question about the .net core support:
according to the documentation, .net remoting is not available with .net
standard 1.3. Would that mean too that the log4net.ThreadLogicalContext
is not available either because it requires
System.Runtime.Remoting.Messaging.CallContext?
If so, is this w
Hi Stefan,
thanks for carving out 2.0.6. I'm looking through the website and am
going to run some sanity checks right now. Are you planning to push this
to nuget?
Cheers,
Dominik
On 2016-12-20 11:07, Stefan Bodewig wrote:
Hi all
log4net 2.0.6 RC1 is available for review here:
https://di
[
https://issues.apache.org/jira/browse/LOG4NET-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-411.
---
Resolution: Invalid
Assignee: Dominik Psenner
Thanks for bringing up this issue, I&#
[
https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754100#comment-15754100
]
Dominik Psenner commented on LOG4NET-538:
-
Has this issue been resolved
[
https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745628#comment-15745628
]
Dominik Psenner commented on LOG4NET-538:
-
Raymond Sanchez posted this on
ithub?
If you are not able to do so, check the raw sql query being sent to
Postgres. I have seen .net providers sending incorrect column names to the
database.
Hope this helps.
On Mon, Dec 12, 2016 at 10:05 AM, Dominik Psenner
wrote:
> Hi Raymond,
>
> have you already tried to migrat
Hi Raymond,
have you already tried to migrate to postgresql 9.5 or newer?
Best regards,
Dominik
On 2016-12-12 16:06, Raymond Sanchez wrote:
What version of Postgresql are you using?
Our company is using 9.4.5 and log4net 1.2.15 with no issues.
On Mon, Dec 12, 2016 at 7:30 AM, Cristian Marge
[
https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742315#comment-15742315
]
Dominik Psenner commented on LOG4NET-538:
-
Would you kindly investigate if
[
https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742270#comment-15742270
]
Dominik Psenner edited comment on LOG4NET-538 at 12/12/16 3:5
[
https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741846#comment-15741846
]
Dominik Psenner commented on LOG4NET-538:
-
> All you need to do is c
[
https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741228#comment-15741228
]
Dominik Psenner commented on LOG4NET-538:
-
I've tried to work out the r
[
https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735238#comment-15735238
]
Dominik Psenner commented on LOG4NET-538:
-
Another thing that I just notice
[
https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735054#comment-15735054
]
Dominik Psenner commented on LOG4NET-538:
-
-Does your implementation
[
https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735036#comment-15735036
]
Dominik Psenner commented on LOG4NET-538:
-
Does your implementation
[
https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734964#comment-15734964
]
Dominik Psenner commented on LOG4NET-538:
-
A quick google search gave me
[
https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734959#comment-15734959
]
Dominik Psenner commented on LOG4NET-538:
-
What happens if you write i
[
https://issues.apache.org/jira/browse/LOG4NET-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734877#comment-15734877
]
Dominik Psenner commented on LOG4NET-538:
-
I cannot find PG error 4
[
https://issues.apache.org/jira/browse/LOG4NET-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708599#comment-15708599
]
Dominik Psenner commented on LOG4NET-537:
-
Looks like System.Exception.ToSt
[
https://issues.apache.org/jira/browse/LOG4NET-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-534.
---
Resolution: Invalid
Assignee: Dominik Psenner
Closing as invalid. The logging
[
https://issues.apache.org/jira/browse/LOG4NET-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708525#comment-15708525
]
Dominik Psenner commented on LOG4NET-537:
-
We require at least a stacktrac
[
https://issues.apache.org/jira/browse/LOG4NET-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner updated LOG4NET-535:
Description:
LocalSyslogAppender doesn’t work on macOS Sierra 10.12 anymore because it was
[
https://issues.apache.org/jira/browse/LOG4NET-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner updated LOG4NET-535:
Issue Type: New Feature (was: Bug)
> Add support for macOS unified logg
[
https://issues.apache.org/jira/browse/LOG4NET-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner updated LOG4NET-535:
Summary: Add support for macOS unified logging (was: LocalSyslogAppender
doesn’t work on
[
https://issues.apache.org/jira/browse/LOG4NET-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692962#comment-15692962
]
Dominik Psenner commented on LOG4NET-535:
-
So it seems that macOS Sierra 1
[
https://issues.apache.org/jira/browse/LOG4NET-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692787#comment-15692787
]
Dominik Psenner commented on LOG4NET-534:
-
https://logging.apache.org/log
[
https://issues.apache.org/jira/browse/LOG4NET-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692561#comment-15692561
]
Dominik Psenner commented on LOG4NET-535:
-
What does it
[
https://issues.apache.org/jira/browse/LOG4NET-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690236#comment-15690236
]
Dominik Psenner commented on LOG4NET-533:
-
I just noticed that there is a p
[
https://issues.apache.org/jira/browse/LOG4NET-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690230#comment-15690230
]
Dominik Psenner commented on LOG4NET-533:
-
Thanks, I have run your sa
[
https://issues.apache.org/jira/browse/LOG4NET-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-533.
---
Resolution: Duplicate
Assignee: Dominik Psenner
Marked as duplicate and closing issue
[
https://issues.apache.org/jira/browse/LOG4NET-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687194#comment-15687194
]
Dominik Psenner commented on LOG4NET-533:
-
You should be able to attach file
[
https://issues.apache.org/jira/browse/LOG4NET-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-531.
---
Resolution: Invalid
Closed for good.
> AdoNetAppender crashes application
[
https://issues.apache.org/jira/browse/LOG4NET-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner reopened LOG4NET-531:
-
Gotta fix a typo in my comment, sorry for the noise.
> AdoNetAppender crashes applicat
[
https://issues.apache.org/jira/browse/LOG4NET-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650843#comment-15650843
]
Dominik Psenner edited comment on LOG4NET-531 at 11/9/16 2:4
[
https://issues.apache.org/jira/browse/LOG4NET-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-531.
---
Resolution: Invalid
Assignee: Dominik Psenner
Happy to help and closing as invalid
[
https://issues.apache.org/jira/browse/LOG4NET-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650800#comment-15650800
]
Dominik Psenner edited comment on LOG4NET-531 at 11/9/16 12:4
[
https://issues.apache.org/jira/browse/LOG4NET-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650800#comment-15650800
]
Dominik Psenner commented on LOG4NET-531:
-
The base AppenderSkeleton c
On 2016-11-09 10:11, Stefan Bodewig wrote:
On 2016-11-07, Dominik Psenner wrote:
LOG4NET-487 is about the configuration option and the issue I would
like to see in the release. The reason is, not having this
configurable costs performance and creating a mutex always is
troublesome to some
This sounds like a plan.
On 6 Nov 2016 8:25 p.m., "Joe" wrote:
> > 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 RollingFi
ith fix version 1.2.14 and the correspondig
commit (svn revision 1711838) really is part of 1.2.14.
https://svn.apache.org/viewvc/logging/log4net/tags/1.2.14/src/Appender/RollingFileAppender.cs?r1=1707180&r2=1711838
Stefan
On 2016-11-06, Dominik Psenner wrote:
We had introduced a mute
We had introduced a mutex to secure rolling operations in the rolling file
appender. It would be nice if we could make the rolling locking
configurable (none, lock, mutex), defaulting to none. There should be an
issue for that, too.
On 6 Nov 2016 2:19 p.m., "Joe" wrote:
I just had a quick look t
[
https://issues.apache.org/jira/browse/LOG4NET-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15640651#comment-15640651
]
Dominik Psenner commented on LOG4NET-256:
-
So this is not something that ca
[
https://issues.apache.org/jira/browse/LOG4NET-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-264.
---
Resolution: Cannot Reproduce
Assignee: Dominik Psenner
Closing because we can&#
[
https://issues.apache.org/jira/browse/LOG4NET-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15640492#comment-15640492
]
Dominik Psenner commented on LOG4NET-264:
-
Bumping WinXP related issues,
[
https://issues.apache.org/jira/browse/LOG4NET-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-272.
---
Resolution: Won't Fix
Assignee: Dominik Psenner
The month became a year, closi
[
https://issues.apache.org/jira/browse/LOG4NET-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15640493#comment-15640493
]
Dominik Psenner commented on LOG4NET-211:
-
Bumping WinXP related issues,
[
https://issues.apache.org/jira/browse/LOG4NET-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15640489#comment-15640489
]
Dominik Psenner commented on LOG4NET-183:
-
Bumping WinXP related issues,
[
https://issues.apache.org/jira/browse/LOG4NET-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15640490#comment-15640490
]
Dominik Psenner commented on LOG4NET-256:
-
Bumping WinXP related issues,
the ones set by the reporters. Which
> usually means everybody considers their issues the most important ones.
>
I tend to prioritize recent reports because the reporters of those old
issues most likely have found a workaround or moved to another logging
framework. Those issues are most likely to be closed because they are not
reproducable.
--
Dominik Psenner
[
https://issues.apache.org/jira/browse/LOG4NET-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-255.
---
Resolution: Won't Fix
Assignee: Dominik Psenner
WinXP has reached end of life a
[
https://issues.apache.org/jira/browse/LOG4NET-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-281.
---
Resolution: Won't Fix
Assignee: Dominik Psenner
Extension methods are the road
Thanks joe for bringing up this issue. This is a good catch for a won't
fix. :-)
2016-11-05 20:54 GMT+01:00 Dominik Psenner (JIRA) :
>
> [ https://issues.apache.org/jira/browse/LOG4NET-281?page=
> com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Do
On 2016-11-04 10:37, Stefan Bodewig wrote:
On 2016-11-03, Joe wrote:
However I don’t understand your point about event formatters – are
there any formatters that aren’t thread safe? It doesn’t seem to be
an unreasonable restriction to require writers of formatters / layout
implementations to
either BufferingAppenderSkeleton or AppenderSkeleton. I’ll give it
some more thought and post again to justify this opinion soon(ish).
*From:*Dominik Psenner [mailto:dpsen...@gmail.com]
*Sent:* 03 November 2016 00:14
*To:* Log4NET Dev
*Subject:* Re: AsyncAppenderSkeleton
As far as I can recall
don’t see what
> race condition could cause a message to be “broken up into elements from
> multiple thread contexts”?
>
>
>
> Can you throw any light on that?
>
>
>
>
>
>
>
> *From:* Dominik Psenner [mailto:dpsen...@apache.org]
> *Sent:* 31 October 2016 15:31
These few lines alone are very suspicious indeed. Without further
investigations I'm unable to give any sensible feedback.
On 2016-10-31 11:54, Joe wrote:
Another point is that for any asynchronous appender implementation,
it’s a sine qua non that the LoggingEvent class be thread-safe.
At l
See inlines.
On 2016-10-31 11:30, Joe wrote:
Hi Dominik,
Thanks for the feedback
> Please note also that MSMQ sounds like a MS only service and that would in turn mean that the .net core
variant would no longer be able to benefit from the
AsyncAppenderSkeleton. To me this outlines a path th
Hi Joe!
On 2016-10-31 08:15, Joe wrote:
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 configur
[
https://issues.apache.org/jira/browse/LOG4NET-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609569#comment-15609569
]
Dominik Psenner commented on LOG4NET-528:
-
There is not enough informatio
Appenders that log is immensely hard to implement if not separated entirely
from the normal logging. Therefore there is the loglog class. It could be a
feature to allow the configuration of loglog appenders under the
precondition that those appenders do not append events back into the
logging frame
[
https://issues.apache.org/jira/browse/LOG4NET-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner resolved LOG4NET-527.
-
Resolution: Fixed
Fix Version/s: 2.0.6
> broken link on config-examples.h
[
https://issues.apache.org/jira/browse/LOG4NET-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605471#comment-15605471
]
Dominik Psenner edited comment on LOG4NET-527 at 10/25/16 2:3
1 - 100 of 1040 matches
Mail list logo
