Build failed in Jenkins: log4net-trunk-tests #16

[Apache Jenkins Server]

See 

Changes:

[bodewig] update release notes for 2.0.6

[bodewig] use UTC time internally, patch by JocularJoe, closes #36

[bodewig] LOG4NET-529 don't assign m_compositeProperties before it is complete

--
[...truncated 13 lines...]
U src\site\xdoc\release\release-notes.xml
U src\Util\SystemInfo.cs
U src\Util\LogLog.cs
U src\Util\OnlyOnceErrorHandler.cs
U src\Core\TimeEvaluator.cs
U src\Core\LoggingEvent.cs
U tests\src\Layout\XmlLayoutTest.cs
U tests\src\Core\FixingTest.cs
At revision 1768598

Executing command: cmd.exe /C "F:\jenkins\tools\nant\nant-0.92\bin\NAnt.exe 
-buildfile:log4net.build compile-net-4.0 && exit %%ERRORLEVEL%%"
[log4net-trunk-tests] $ cmd.exe /C 
"F:\jenkins\tools\nant\nant-0.92\bin\NAnt.exe -buildfile:log4net.build 
compile-net-4.0 && exit %%ERRORLEVEL%%"
NAnt 0.92 (Build 0.92.4543.0; release; 6/9/2012)
Copyright (C) 2001-2012 Gerry Shaw
http://nant.sourceforge.net

Buildfile: 
file:///f:/jenkins/jenkins-slave/workspace/log4net-trunk-tests/log4net.build
Target framework: Microsoft .NET Framework 4.0
Target(s) specified: compile-net-4.0 


check-current-build-config:


set-build-configuration:


set-debug-build-configuration:


check-current-build-config:


set-build-configuration-flags:


check-current-build-config:


set-framework-configuration:


check-bin-dir:

[mkdir] Creating directory 
'

check-doc-dir:

[mkdir] Creating directory 
'

check-sdkdoc-dir:


check-sdkdoc-debug:


check-current-build-config:


check-build-debug:


check-build-defines:


set-net-4.0-runtime-configuration:


check-log4net-basedir:


check-current-bin-dir:

[mkdir] Creating directory 
'

clean-current-bin-dir:

 [echo] Cleaning the bin/net/4.0/debug binaries directory.
   [delete] Deleting directory 
'
[mkdir] Creating directory 
'

compile-net-4.0:

  [csc] Compiling 226 files to 
'

BUILD SUCCEEDED

Total time: 2.5 seconds.

Executing command: cmd.exe /C "F:\jenkins\tools\nant\nant-0.92\bin\NAnt.exe 
-buildfile:tests/nant.build && exit %%ERRORLEVEL%%"
[log4net-trunk-tests] $ cmd.exe /C 
"F:\jenkins\tools\nant\nant-0.92\bin\NAnt.exe -buildfile:tests/nant.build && 
exit %%ERRORLEVEL%%"
NAnt 0.92 (Build 0.92.4543.0; release; 6/9/2012)
Copyright (C) 2001-2012 Gerry Shaw
http://nant.sourceforge.net

Buildfile: 
file:///f:/jenkins/jenkins-slave/workspace/log4net-trunk-tests/tests/nant.build
Target framework: Microsoft .NET Framework 4.0
Target(s) specified: runtests 


check-current-build-config:


set-build-configuration:


set-debug-build-configuration:


check-current-build-config:


set-build-configuration-flags:


check-current-build-config:


set-framework-configuration:


check-bin-dir:

[mkdir] Creating directory 
'

check-doc-dir:

[mkdir] Creating directory 
'

check-sdkdoc-dir:


check-sdkdoc-debug:


check-current-build-config:


check-build-debug:


check-build-defines:


set-net-4.0-runtime-configuration:


install-nunit:

  [get] Retrieving 
'https://github.com/nunit/nunitv2/releases/download/2.6.4/NUnit-2.6.4.zip' to 
'C:\Users\jenkins\AppData\Local\Microsoft\Windows\INetCache\nunit.zip'.
[unzip] Unzipping 
'C:\Users\jenkins\AppData\Local\Microsoft\Windows\INetCache\nunit.zip' to 
'C:\Users\jenkins\AppData\Local\Microsoft\Windows\INetCache\nunit.tmp'.
 [copy] Copying 1 file to 
'

runtests:

 [echo] Running tests for net-4.0

check-bin-dir:


check-doc-dir:


check-sdkdoc-dir:


check-sdkdoc-debug:


check-current-build-config:


check-build-debug:


check-build-defines:


set-net-4.0-runtime-configuration:


check-log4net-basedir:


check-current-bin-dir:

[mkdir] Creating directory 
'

clean-current-bin-dir:

 [echo] Cleaning the bin/net/4.0/debug binaries directory.
   [delete] Deleting directory 
'
[mkdir] Creating directory 
'

check-log4net-output-dir:


check-log4net-assembly:


compile-net-4.0:

 [copy] Copying 3 files to 

Jenkins build is back to normal : log4net-trunk-build #139

[Apache Jenkins Server]

See 

Re: [jira] [Resolved] (LOG4NET-526) Add appSetting conversion pattern to PatternString

[Arun Kumar]

Unsubscribe

Get Outlook for Android



On Sun, Nov 6, 2016 at 12:39 AM +0530, "Stefan Bodewig (JIRA)" 
> wrote:


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

Stefan Bodewig resolved LOG4NET-526.

   Resolution: Fixed
Fix Version/s: 2.0.6

Test added, many thanks Joe.

> Add appSetting conversion pattern to PatternString
> --
>
> Key: LOG4NET-526
> URL: https://issues.apache.org/jira/browse/LOG4NET-526
> Project: Log4net
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 1.2.15
>Reporter: Joe
>Priority: Minor
> Fix For: 2.0.6
>
>
> A common requirement is to be able to define a base directory for log files 
> that can be used by multiple FileAppenders.  In this way, the directory only 
> needs to be changed in one place.
> Today the typical solution is to use a PatternString with a property that is 
> set in code before log4net is configured, e.g.
>value="%property{LogDIr}MyFile.log"/>
> Suggested feature is to allow a conversion pattern that reads the base 
> directory name from an appSetting, e.g.:
>value="%appSetting{LogDIr}MyFile.log"/>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jira] [Closed] (LOG4NET-255) Problem with getting path to appdata with windows service in Windows XP

[Arun Kumar]

Unsubscribe

Get Outlook for Android

From: Dominik Psenner (JIRA)
Sent: Sunday, November 6, 01:30
Subject: [jira] [Closed] (LOG4NET-255) Problem with getting path to appdata 
with windows service in Windows XP
To: Log4NET Dev

[ 
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 
and we are not going to implement a hack for it. Closing as won't fix. Whoever 
hits this issue is better off by finding a workaround. > Problem with getting 
path to appdata with windows service in Windows XP > 
--- > > 
Key: LOG4NET-255 > URL: https://issues.apache.org/jira/browse/LOG4NET-255 > 
Project: Log4net > Issue Type: Bug > Affects Versions: 1.2.10 > Environment: 
Windows XP, C# , Windows Service > Reporter: Martin B. > Assignee: Dominik 
Psenner > Fix For: 1.2 Maintenance Release > > > I've got windows service in C# 
which using RollingFilleAppender that logs to appdata folder. Everything works 
fine in Vista, W7 or 2008 server, ${APPDATA} is correctly replaced by 
corresponding path to app data folder. But when i run my service in Windows XP 
I get following error through internal debugger. > log4net:ERROR 
[RollingFileAppender] Unable to acquire lock on file \\MyTestApp\LOG\LOG.TXT. 
Could not find a part of the path '\\MyTestApp\LOG'. > Logger path setting from 
config file is below: > -- This message was sent by Atlassian JIRA (v6.3.4#6332)

Re: [jira] [Commented] (LOG4NET-256) log4net With MDC is not exactly threadsafe?

[Arun Kumar]

Get Outlook for Android



On Sun, Nov 6, 2016 at 1:37 AM +0530, "Dominik Psenner (JIRA)" 
> wrote:


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

Dominik Psenner commented on LOG4NET-256:
-

Bumping WinXP related issues, dev list please discuss if we can close this 
issue as won't fix because WinXP reached end of life.

> log4net With MDC is not exactly threadsafe?
> ---
>
> Key: LOG4NET-256
> URL: https://issues.apache.org/jira/browse/LOG4NET-256
> Project: Log4net
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.2.10
> Environment: Windows Server 2003, Windows XP
>Reporter: MK Pandey
> Fix For: 1.2 Maintenance Release
>
> Attachments: bug detals mail.jpg
>
>
> Hi All,
> Our situation is that we are using MDC values (ex, transID) to set additional 
> values which is used across multiple classes to identify the transaction.
> We have one LogHelper class which creates private static instance of the as 
> below:
> log4net.ILog fileLogger = LogManager.GetLogger(GetType());
> When second thread starts and modifies the values, the subsequent logs from 
> other threads start using the same values.
> Any suggestions?
> When using web.config file for appender defintion, is this not thread safe?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jira] [Commented] (LOG4NET-256) log4net With MDC is not exactly threadsafe?

[Arun Kumar]

Get Outlook for Android



On Sun, Nov 6, 2016 at 1:37 AM +0530, "Dominik Psenner (JIRA)" 
> wrote:


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

Dominik Psenner commented on LOG4NET-256:
-

Bumping WinXP related issues, dev list please discuss if we can close this 
issue as won't fix because WinXP reached end of life.

> log4net With MDC is not exactly threadsafe?
> ---
>
> Key: LOG4NET-256
> URL: https://issues.apache.org/jira/browse/LOG4NET-256
> Project: Log4net
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.2.10
> Environment: Windows Server 2003, Windows XP
>Reporter: MK Pandey
> Fix For: 1.2 Maintenance Release
>
> Attachments: bug detals mail.jpg
>
>
> Hi All,
> Our situation is that we are using MDC values (ex, transID) to set additional 
> values which is used across multiple classes to identify the transaction.
> We have one LogHelper class which creates private static instance of the as 
> below:
> log4net.ILog fileLogger = LogManager.GetLogger(GetType());
> When second thread starts and modifies the values, the subsequent logs from 
> other threads start using the same values.
> Any suggestions?
> When using web.config file for appender defintion, is this not thread safe?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jira] [Commented] (LOG4NET-256) log4net With MDC is not exactly threadsafe?

[Arun Kumar]

Get Outlook for Android



On Sun, Nov 6, 2016 at 1:37 AM +0530, "Dominik Psenner (JIRA)" 
> wrote:


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

Dominik Psenner commented on LOG4NET-256:
-

Bumping WinXP related issues, dev list please discuss if we can close this 
issue as won't fix because WinXP reached end of life.

> log4net With MDC is not exactly threadsafe?
> ---
>
> Key: LOG4NET-256
> URL: https://issues.apache.org/jira/browse/LOG4NET-256
> Project: Log4net
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.2.10
> Environment: Windows Server 2003, Windows XP
>Reporter: MK Pandey
> Fix For: 1.2 Maintenance Release
>
> Attachments: bug detals mail.jpg
>
>
> Hi All,
> Our situation is that we are using MDC values (ex, transID) to set additional 
> values which is used across multiple classes to identify the transaction.
> We have one LogHelper class which creates private static instance of the as 
> below:
> log4net.ILog fileLogger = LogManager.GetLogger(GetType());
> When second thread starts and modifies the values, the subsequent logs from 
> other threads start using the same values.
> Any suggestions?
> When using web.config file for appender defintion, is this not thread safe?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

RE: Apache log4net Needs Help

[Dominik Psenner]

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 RollingFileAppender should be marked as related
> issues to the rewrite issue. I dont have the issue id at hand, though. If
> you wanted to pick up that initial work and
>
> > continue it would be awesome! Most probably I am going to jump in
> helping you because the RollingFileAppender is one of the most used
> features and therefore one of the crucial points
>
> > where performance and sanity can make a difference of users moving away
> from log4net or attracting more users.
>
>
>
> I’d be willing to get involved in that.  A suggestion for what I could do
> over the next months:
>
>
>
> 1.  Complete AsyncAppenderSkeleton and AsyncForwardingAppender
>
>
>
> 2. Possibly implement the ability to log to an ILog from an appender
> derived from AsyncAppenderSkeleton if the re-entrancy issues can be solved
> (which I think they can).
>
>
>
> 3. Implement performance counters in AsyncAppenderSkeleton (and maybe
> AppenderSkeleton).  I’ve recently done something similar for a custom
> asynchronous appender, and it should be fairly straightforward to
> implement.  The idea is to make it easy to monitor performance of an
> appender: number of logging events processed, rate at which they’re
> processed, average processing time, queue length when in asynchronous mode,
> …  I’ll create an issue for this in due course with a more detailed
> description.
>
>
>
> 4. Reimplement RollingFileAppender, perhaps as AsyncRollingFileAppender
> derived from AsyncAppenderSkeleton.  It might be useful to be able to use
> it in asynchronous mode, for example to reduce the performance impact of
> contention for the mutex when logging to a shared file.
>
>
>
>
>