[jira] [Commented] (LOG4NET-235) IP Address Pattern Converter

[ https://issues.apache.org/jira/browse/LOG4NET-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104307#comment-13104307 ] Stefan Bodewig commented on LOG4NET-235: Yes, the SDK docs are generated from met

RE: Name for MutexLock?

>The RemotingAppender tries to flush all message in shutdown but if >things go really bad you may be losing some messages, this is true. There can't be any guarantee anyway that all log messages are written before the application goes down. There are circumstances where the operating system takes

RE: Name for MutexLock?

Remoting appender: If the application goes down that's finally persisting the log events, the logging is down too. InterProcessLock / MutexLock: Since every application persists the log events by itself, the logging survives as long as the application is "alive". _ From: Ron Grab

Re: Name for MutexLock?

On 2011-09-14, Ron Grabowski wrote: > Can you share a config snippet showing how to use the RemotingAppender > like you've described? We used to have an extraordinally simple Windows Service at $work that didn't do much but using log4net writing to a file and starting the RemoteLoggingServerPlugi

Re: diffs between 1.2.10 and current trunk

On 2011-09-14, Ron Grabowski wrote: > The signature changes from void to ICollection shouldn't break > anything. I agree. > Now the configurators return a list of configuration messages. I > suppose it should return an array of a certain type instead of just > ICollection. Maybe something like C

RE: Name for MutexLock?

No, I do not have a configuration, but the idea would be to setup a logging application that would be the receiver of logging sent out from 2 or more applications using a remoting appender. Basically the same idea as remote Syslog application. Yes, it might be slow to log, but (other than the log

Re: Name for MutexLock?

Can you share a config snippet showing how to use the RemotingAppender like you've described? What happens when one of the apps goes down? I envision the InterProcessLock as a locking model used between two low/medium chatty apps that want to write to the same file that may or may not be runnin

[jira] [Commented] (LOG4NET-164) using a named mutex for file appenders

[ https://issues.apache.org/jira/browse/LOG4NET-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104050#comment-13104050 ] Ron Grabowski commented on LOG4NET-164: --- I like the name InterProcessLock > using

Re: Name for MutexLock?

I don't have any hard numbers but the last time I played around with MinimalLock it was very very slow. I view InterProcessLock as an intermediary between exclusive and minimal locking. From: Dominik Psenner To: 'Log4NET Dev' Sent: Tuesday, September 13, 2011

Re: diffs between 1.2.10 and current trunk

The signature changes from void to ICollection shouldn't break anything. Now the configurators return a list of configuration messages. I suppose it should return an array of a certain type instead of just ICollection. Maybe something like ConfigurationMessage[] or  LogLog[]. I lean more towards

[jira] [Commented] (LOG4NET-235) IP Address Pattern Converter

[ https://issues.apache.org/jira/browse/LOG4NET-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104037#comment-13104037 ] Ron Grabowski commented on LOG4NET-235: --- I don't think having one aspnet pattern co

[jira] [Commented] (LOG4NET-235) IP Address Pattern Converter

[ https://issues.apache.org/jira/browse/LOG4NET-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103706#comment-13103706 ] Adam Davies commented on LOG4NET-235: - I can provide documentation for 235, 236, 237.

[jira] [Commented] (LOG4NET-314) Improve StackTracePatternConverter

[ https://issues.apache.org/jira/browse/LOG4NET-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103705#comment-13103705 ] Stefan Bodewig commented on LOG4NET-314: Hi Adam, I'm glad you are still around ;

[jira] [Commented] (LOG4NET-314) Improve StackTracePatternConverter

[ https://issues.apache.org/jira/browse/LOG4NET-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103699#comment-13103699 ] Adam Davies commented on LOG4NET-314: - I can add a theshold constraint if desired, an

diffs between 1.2.10 and current trunk

Hi all, in order to shape up for the release I diffed the 1.2.10 release ZIP source tree against current trunk's src and used BitDiffer from bitwidgets[1] to compare the DEBUG assemblies targeting 2.0 in binary. The results can be found in The so

Re: Name for MutexLock?

On 2011-09-13, Roy Chastain wrote: > I like InterProcessLock and would like to propose MultiProcessLock as my > favorite. > I HOPE that the documentation will indicate what a bad plan this is and > that a remoteing appender etc might be a better plan. You can always ensure it does by providing t

RE: Name for MutexLock?

>Not only, it would also appear inside the config file in order to set >the locking model of FileAppender like in the third example of >http://logging.apache.org/log4net/release/config-examples.html#fileappender >Right now it would be > > Quite obvious what it does. If one enters "MutexLock .NET"

RE: Name for MutexLock?

I like InterProcessLock and would like to propose MultiProcessLock as my favorite. I HOPE that the documentation will indicate what a bad plan this is and that a remoteing appender etc might be a better plan. -- Roy Chastain

Re: Name for MutexLock?

On 2011-09-13, Dominik Psenner wrote: >> LOG4NET-164 introduced a new locking strategy for FileAppender which >> technically uses a System.Threading.Mutex with a name built from the log >> file's name. This should allow separate processes to share a log file >> without repeatedly opening and clos

RE: Name for MutexLock?

>LOG4NET-164 introduced a new locking strategy for FileAppender which >technically uses a System.Threading.Mutex with a name built from the log >file's name. This should allow separate processes to share a log file >without repeatedly opening and closing it. > >The main remaining issue is its name

[jira] [Commented] (LOG4NET-87) Support ASP.Net related PatternConverters to allow items from the HttpContext.Current.Session, Cache, Request, etc. to be captured.

[ https://issues.apache.org/jira/browse/LOG4NET-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103583#comment-13103583 ] Stefan Bodewig commented on LOG4NET-87: --- just missing some documentation > Support

Name for MutexLock?

Hi, LOG4NET-164 introduced a new locking strategy for FileAppender which technically uses a System.Threading.Mutex with a name built from the log file's name. This should allow separate processes to share a log file without repeatedly opening and closing it. The main remaining issue is its name

Trailing dots in names for NamedPatternConverter and precision > 0

Hi, I wanted to fix LOG4NET-215 and started by writing a few tests for the existing code (as it looked unnecessarily complex to me) and stumbled over the case of trailing dots - which is the reason the code looked so complex in the first place. NamedPatternConverter is the base class used by %log

[jira] [Resolved] (LOG4NET-215) Exception on Convert for return %class{1} name

[ https://issues.apache.org/jira/browse/LOG4NET-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved LOG4NET-215. Resolution: Fixed fixed with svn revision 1170104 > Exception on Convert for return %clas

[jira] [Commented] (LOG4NET-154) Add a StackTracePatternConverter to display method calls leading up to log message

[ https://issues.apache.org/jira/browse/LOG4NET-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103474#comment-13103474 ] Stefan Bodewig commented on LOG4NET-154: I've had a look at Adam's (MAX|MIN) cont

[jira] [Created] (LOG4NET-314) Improve StackTracePatternConverter

Improve StackTracePatternConverter -- Key: LOG4NET-314 URL: https://issues.apache.org/jira/browse/LOG4NET-314 Project: Log4net Issue Type: Improvement Components: Core Affects Versions: 1.2.11

[jira] [Created] (LOG4NET-313) Document %stacktrace and %stacktracedetail

Document %stacktrace and %stacktracedetail -- Key: LOG4NET-313 URL: https://issues.apache.org/jira/browse/LOG4NET-313 Project: Log4net Issue Type: Sub-task Components: Documentation

[jira] [Commented] (LOG4NET-154) Add a StackTracePatternConverter to display method calls leading up to log message

[ https://issues.apache.org/jira/browse/LOG4NET-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103456#comment-13103456 ] Stefan Bodewig commented on LOG4NET-154: Documentation on stacktracedetail patter

[jira] [Updated] (LOG4NET-151) Cache DateTime.Now values when creating LoggingEvent when Environment.TickCount has not changed

[ https://issues.apache.org/jira/browse/LOG4NET-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-151: --- Fix Version/s: (was: 1.2.11) 1.2 Maintenance Release Pushing it back