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

2016-11-07 Thread Arun Kumar 
Unsubscribe

Get Outlook for Android



On Sun, Nov 6, 2016 at 12:39 AM +0530, "Stefan Bodewig (JIRA)" 
mailto:j...@apache.org>> 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

2016-11-07 Thread 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?

2016-11-07 Thread Arun Kumar 
Get Outlook for Android



On Sun, Nov 6, 2016 at 1:37 AM +0530, "Dominik Psenner (JIRA)" 
mailto:j...@apache.org>> wrote:


[ 
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, 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?

2016-11-07 Thread Arun Kumar 
Get Outlook for Android



On Sun, Nov 6, 2016 at 1:37 AM +0530, "Dominik Psenner (JIRA)" 
mailto:j...@apache.org>> wrote:


[ 
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, 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?

2016-11-07 Thread Arun Kumar 
Get Outlook for Android



On Sun, Nov 6, 2016 at 1:37 AM +0530, "Dominik Psenner (JIRA)" 
mailto:j...@apache.org>> wrote:


[ 
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, 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-524) OnlyOnceErrorHandler might cause StackOverflowError

2016-08-27 Thread Arun Kumar 
Unsubscribe

Sent from my Windows Phone

From: Dominik Psenner (JIRA)
Sent: ‎24-‎08-‎2016 22:39
To: log4net-dev@logging.apache.org
Subject: [jira] [Commented] (LOG4NET-524) OnlyOnceErrorHandler might cause 
StackOverflowError


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

Dominik Psenner commented on LOG4NET-524:
-

Please subscribe to the log4j mailing list to track notifications and get 
involved. I do not actively hack on log4j and will most likely loose track of 
this.

> OnlyOnceErrorHandler might cause StackOverflowError
> ---
>
> Key: LOG4NET-524
> URL: https://issues.apache.org/jira/browse/LOG4NET-524
> Project: Log4net
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 1.2.15
>Reporter: Marc Theisen
>Assignee: Dominik Psenner
>
> I am referring to the solution in 
> https://bz.apache.org/bugzilla/show_bug.cgi?id=42151.
> I am suggesting another approach instead of placing a bad hack into 
> com.{{csfb.fao.carat.util.file.LoggingOutputStream}}.
> Why not change the {{error}} method of class {{OnlyOnceErrorHandler}} from
> {code}
> public void error(String message, Exception e, int errorCode, LoggingEvent 
> event)
> {
>   if (e instanceof InterruptedIOException || e instanceof 
> InterruptedException)
>   {
> Thread.currentThread().interrupt();
>   }
>   if(firstTime)
>   {
> LogLog.error(message, e);
> firstTime = false;   // yikes, too late if stdout/stderr has been
>   }  // redirected
> }
> {code}
> to
> {code}
> public void error(String message, Exception e, int errorCode, LoggingEvent 
> event)
> {
>   if (e instanceof InterruptedIOException || e instanceof 
> InterruptedException)
>   {
> Thread.currentThread().interrupt();
>   }
>   if(firstTime)
>   {
> firstTime = false;
> LogLog.error(message, e);
>   }
> }
> {code}



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