gmane.comp.apache.logging.log4net.devel

[jira] [Updated] (LOG4NET-338) Port of log4net for MonoDroid

Wojciech Dec (JIRA — 2012-05-11T12:59:49

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

Wojciech Dec updated LOG4NET-338:
---------------------------------

    Attachment: monodroid-on1337114.patch.zip

Port to Mono for Android patch for trunk rev 1337114.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (LOG4NET-338) Port of log4net for MonoDroid

Wojciech Dec (JIRA — 2012-05-11T12:57:50

Wojciech Dec created LOG4NET-338:
------------------------------------

             Summary: Port of log4net for MonoDroid
                 Key: LOG4NET-338
                 URL: https://issues.apache.org/jira/browse/LOG4NET-338
             Project: Log4net
          Issue Type: New Feature
          Components: Appenders, Builds
    Affects Versions: 1.2.11
         Environment: Mono for Android
            Reporter: Wojciech Dec
            Priority: Minor


Hi

I've made a port of log4net to MonoDroid (Mono for Android).

Summary of changes:
 * based on trunk rev 1337114
 * code altered by "#if MONODROID"
 * added log4net.monodroid.vs2010.csproj and log4net.monodroid.vs2010.sln
 * added AndroidLogAppender
 * ConfigureAndWatchHandler based on native FileObserver
 * minor ndoc changes

Build:
 * install Mono for Android
 * get log4net source (see code version above)
 * apply patch
 * open solution in Visual Studio (note: NAnt doesn't support Mono for Android framework)
 * build

Tests:
 * No automatic tes

[jira] [Commented] (LOG4NET-118) RollingFileAppender: RollingStyle=Size with StaticLogFileName=false does not work

Daniel (JIRA — 2012-05-03T01:03:48

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

Daniel commented on LOG4NET-118:
--------------------------------

This is definitely not a Minor issue! I just lost 1GB of logs because of it.
As Brian mentioned, this overwrites the existing log file instead of rolling and creating a new one.

Does anyone know if this is somehow fixed in 1.2.11 ?
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (LOG4NET-148) ThreadContext uses LocalDataStore to store ThreadSpecific data instead should be using [ThreadStatic] variables.

Simon Svensson (JIRA — 2012-05-01T11:29:52

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

Simon Svensson commented on LOG4NET-148:
----------------------------------------

Yes, it seems correct, except for some indenting issues.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (LOG4NET-337) RollingFileAppender.RollOverIfDateBoundaryCrossing doesn't take PreserveLogFileNameExtension into account

Jens Weiermann (JIRA — 2012-04-30T11:18:47

Jens Weiermann created LOG4NET-337:
--------------------------------------

             Summary: RollingFileAppender.RollOverIfDateBoundaryCrossing doesn't take PreserveLogFileNameExtension into account
                 Key: LOG4NET-337
                 URL: https://issues.apache.org/jira/browse/LOG4NET-337
             Project: Log4net
          Issue Type: Bug
          Components: Appenders
    Affects Versions: 1.2.11
         Environment: Windows 7
            Reporter: Jens Weiermann


If a roll over is needed for crossing a date boundary since the last run, the m_scheduledFilename variable is set up based on the last write time of the log file. However, if PreserveLogFileNameExtension is set to true, this extension is NOT preserved, instead this option is ignored. This leads to wrong backup file names.As an example, if the log filename is file.log and the last write time of the file is 2012-04-30, the generated filename is file.log.2012-04-30 instead of file.2012-04-30.log as it should be.

Steps to

[jira] [Created] (LOG4NET-336) Enabling ImmediateFlush on a RollingFileAppender has no effect

bernard mcgourty (JIRA — 2012-04-26T15:02:15

bernard mcgourty created LOG4NET-336:
----------------------------------------

             Summary: Enabling ImmediateFlush on a RollingFileAppender has no effect
                 Key: LOG4NET-336
                 URL: https://issues.apache.org/jira/browse/LOG4NET-336
             Project: Log4net
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.2.10
         Environment: Windows Server 2008 R2 Enterprise
            Reporter: bernard mcgourty


I enabled ImmediateFlush on our RollingFileAppenders and log messages are not immediately written to disk. Doesn't appear to have any effect.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (LOG4NET-335) Lost the ability to monitor changes to logger config files when you call ConfigureAndWatch multiple times with different Config File Names - worked fine on 1.2.10.0

bernard mcgourty (JIRA — 2012-04-26T00:23:17

bernard mcgourty created LOG4NET-335:
----------------------------------------

             Summary: Lost the ability to monitor changes to logger config files when you call ConfigureAndWatch multiple times with different Config File Names - worked fine on 1.2.10.0
                 Key: LOG4NET-335
                 URL: https://issues.apache.org/jira/browse/LOG4NET-335
             Project: Log4net
          Issue Type: Bug
          Components: Other
    Affects Versions: 1.2.11
         Environment: Windows Server 2008 R2
            Reporter: bernard mcgourty
            Priority: Blocker


We had a class that wraps log4net that is in a shared assembly, multiple components in our application create instances to the Log 4 Net Wrapper, each component has its own log config file.

When the Log4Net wrapper class is constructed it uses log4net.Logmanager to ConfigureAndWatch the log config file passed in to it by the calling component. We recently upgraded from log4net 1.2.10.0 to 1.2.11.0 and log4net no long

Re: [jira] [Commented] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders

Ron Grabowski — 2012-04-19T04:47:25

Maybe OpenFile isn't the best place to look for error. If you want access to a logging event so you can send it somewhere else if writing to the appender fails you'll probably need to check that the previous write was successful higher up in the chain in one of the DoAppend methods. I'll keep thinking about this and try to write some code.

________________________________
 From: stalinsubash (Commented) (JIRA) <jira< at >apache.org>
To: log4net-dev< at >logging.apache.org 
Sent: Wednesday, April 18, 2012 6:59 AM
Subject: [jira] [Commented] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders

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

stalinsubash commented on LOG4NET-332:
--------------------------------------

Thanks Ron.

I successfully implemented Failover in AD

[jira] [Commented] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders

Ron Grabowski (Commented) (JIRA — 2012-04-19T04:27:02

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

Ron Grabowski commented on LOG4NET-332:
---------------------------------------

If you have general usage questions post to the mailing list. This item is closed because its not a bug in log4net.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (LOG4NET-332) I'm looking for the ability to set up a hierarchy of appenders, if a log to an ADONETAppender fails, log4net could then log to one of more "back-up" appenders

stalinsubash (Commented) (JIRA — 2012-04-18T10:59:42

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

stalinsubash commented on LOG4NET-332:
--------------------------------------

Thanks Ron.

I successfully implemented Failover in ADONetAppender. If ADONet fails then it will rollover to FileAppender \ EventViewerAppender. Here I attached the ADONetAppender class file as well.

But I FileAppender I’ll fail, I can’t able to get Logging Event in FileAppender class. Here I’ll explain what scenario I tried. I tried to write a log in a text file but the path I mentioned in the configuration file was wrong, so while writing the log it will search the path to open the file in the method (OpenFile) in FileAppender class file, so in the try catch block I implemented below codes as well,

public override void OpenFile(string filename, bool append,Encoding encoding)
{
try
{
                    m_stream = CreateStream(filename, append, F

[jira] [Issue Comment Edited] (LOG4NET-233) Support .NET 4.0 including Client Profile

Dominik Psenner (Issue Comment Edited) (JIRA — 2012-04-16T11:42:18

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

Dominik Psenner edited comment on LOG4NET-233 at 4/16/12 11:41 AM:
-------------------------------------------------------------------

That's why you have to define it. :-) Clicking on the link above and following one of the first 3 search results (at least those are the ones I have tried) shows you how to achieve that with visual studio. What you cannot do is building log4net from source and expecting that visual studio builds all different dll's for .net 3.5, 4.0, 4.0 client profile since visual studio does not allow you to change the target profile of a project at build-time. What are you trying to achieve that requires you to not use a precompiled log4net dll?
                
      was (Author: nachbarslumpi):
    That's why you have to define it. :-) Clicking on the link above and following one of the first 3 search results (at le

[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile

Dominik Psenner (Commented) (JIRA — 2012-04-16T11:40:18

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

Dominik Psenner commented on LOG4NET-233:
-----------------------------------------

That's why you have to define it. :-) Clicking on the link above and following one of the first 3 search results (at least which ones I have tried) shows you how to achieve that with visual studio. What you cannot do is building log4net from source and expecting that visual studio builds all different dll's for .net 3.5, 4.0, 4.0 client profile since visual studio does not allow you to change the target profile of a project at build-time. What are you trying to achieve that requires you to not use a precompiled log4net dll?
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more inf

[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile

Rufus Buschart (Commented) (JIRA — 2012-04-16T10:46:17

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

Rufus Buschart commented on LOG4NET-233:
----------------------------------------

What a helpful comment... Problem is, I'm not able to find the constant CLIENT_PROFILE in the csproj-file and therefore I have no idea what to change.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile

Dominik Psenner (Commented) (JIRA — 2012-04-16T09:02:18

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

Dominik Psenner commented on LOG4NET-233:
-----------------------------------------

http://tinyurl.com/82mq7h8
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile

Rufus Buschart (Commented) (JIRA — 2012-04-16T07:34:18

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

Rufus Buschart commented on LOG4NET-233:
----------------------------------------

Thank you for your kind answere. Solution 1 is what i actually did last week to come around this problem, but solution 2 is what I prefer to do. Sadly I have no idea, where I can set this 'compiler constants' in Visual Studio. I understand, that NAnt does it automatically, but I believe, that a lot users are not using NAnt (like myself). Can you point me to the correct location for setting this constants?
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile

Stefan Bodewig (Commented) (JIRA — 2012-04-14T04:11:42

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

Stefan Bodewig commented on LOG4NET-233:
----------------------------------------

trunk should work without any modifications if you set the "correct" build defines.  For the 4.0 Client Profile you have to define NET, NET_2_0, NET_4_0, CLIENT_PROFILE. With those all references to classes not part of the client profile will be hidden.

The official build system of log4net is NAnt and this automatically sets those defines as needed.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Issue Comment Edited] (LOG4NET-233) Support .NET 4.0 including Client Profile

Dominik Psenner (Issue Comment Edited) (JIRA — 2012-04-13T22:45:17

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

Dominik Psenner edited comment on LOG4NET-233 at 4/13/12 10:44 PM:
-------------------------------------------------------------------

HttpContext is part of the System.Web namespace, which itself is within the System.Web.dll. Unfortunately the .NET Framework 4.0 Client Profile does not include the System.Web.dll and thus it doesn't know about HttpContext. There are some steps you can take, I'm going to write down two of them:

1) remove all references to System.Web (in which case you will have to remove log4net.Plugin.RemoteLoggingServerPlugin) to build it
2) add conditionals that exclude all references when built against the Client Profile

In case you do 2) please send us a patch together with the revision we can apply it to. The reason why we are able to build it is that we use a buildbot which builds it for us against a client prof

[jira] [Issue Comment Edited] (LOG4NET-233) Support .NET 4.0 including Client Profile

Dominik Psenner (Issue Comment Edited) (JIRA — 2012-04-13T21:39:16

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

Dominik Psenner edited comment on LOG4NET-233 at 4/13/12 9:37 PM:
------------------------------------------------------------------

HttpContext is part of the System.Web namespace, which itself is within the System.Web.dll. Unfortunately the .NET Framework 4.0 Client Profile does not include the System.Web.dll and thus it doesn't know about HttpContext. There are some steps you can take, I'm going to write down two of them:

1) remove all references to System.Web (in which case you will have to remove log4net.Plugin.RemoteLoggingServerPlugin) to build it
2) add conditionals that exclude all references when built against the Client Profile

In case you do 2) please send us a patch together with the revision we can apply it to.
                
      was (Author: nachbarslumpi):
    HttpContext is part of the System.Web namespace, which

[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile

Dominik Psenner (Commented) (JIRA — 2012-04-13T21:37:19

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

Dominik Psenner commented on LOG4NET-233:
-----------------------------------------

HttpContext is part of the System.Web namespace, which itself is within the in System.Web.dll. Unfortunately the .NET Framework 4.0 Client Profile does not include the System.Web.dll and thus it doesn't know about HttpContext. There are some possible options, I'm going to write down two of them:

1) remove all references to System.Web (in which case you will have to remove log4net.Plugin.RemoteLoggingServerPlugin) to build it
2) add conditionals that exclude all references when built against the Client Profile

In case you do 2) please send us a patch together with the revision we can apply it to.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://is

[jira] [Commented] (LOG4NET-233) Support .NET 4.0 including Client Profile

Rufus Buschart (Commented) (JIRA — 2012-04-13T11:33:17

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

Rufus Buschart commented on LOG4NET-233:
----------------------------------------

I just downloaded the TRUNK from the Subversion repository and it seems, that I have this Client Framework issue again. When I try to compile it with the .net Framework 4.0 Client Profile as a target I recieve the error message, that "The type or namespace name 'HttpContex' could not be found". Any idea how to fix ist.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Issue Comment Edited] (LOG4NET-233) Support .NET 4.0 including Client Profile

Rufus Buschart (Issue Comment Edited) (JIRA — 2012-04-13T11:33:18

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

Rufus Buschart edited comment on LOG4NET-233 at 4/13/12 11:31 AM:
------------------------------------------------------------------

I just downloaded the TRUNK from the Subversion repository and it seems, that I have this Client Framework issue again. When I try to compile it with the .net Framework 4.0 Client Profile as a target I recieve the error message, that "The type or namespace name 'HttpContex' could not be found". Any idea how to fix ist?
                
      was (Author: rufusjwb):
    I just downloaded the TRUNK from the Subversion repository and it seems, that I have this Client Framework issue again. When I try to compile it with the .net Framework 4.0 Client Profile as a target I recieve the error message, that "The type or namespace name 'HttpContex' could not be found". Any idea how to fix ist.
                  

--