Thang Cao (JIRA | 19 Nov 07:06 2014
Picon

[jira] [Commented] (LOG4NET-446) Google spreadsheet appender


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

Thang Cao commented on LOG4NET-446:
-----------------------------------

Thank you, Stefan and Justin !
Because it has some external dependencies (GData api sdk) so I publish it as a repository in github : https://github.com/ctthang/log4net.googlespreadsheetappender
Please add a link from log4net's website to it.
Thanks.

> Google spreadsheet appender
> ---------------------------
>
>                 Key: LOG4NET-446
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-446
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 1.2.13
>            Reporter: Thang Cao
>              Labels: features
>             Fix For: 1.3.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> This is not really an issue!
(Continue reading)

Stefan Bodewig (JIRA | 18 Nov 16:24 2014
Picon

[jira] [Commented] (LOG4NET-446) Google spreadsheet appender


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

Stefan Bodewig commented on LOG4NET-446:
----------------------------------------

Actually the official way would be to create a patch and attach it to this issue - github pull requests work as
well, pick your preferred option.

But please let us step back for a moment.  An appender can easily be added as separate DLL and doesn't need to
ship with log4net itself.  I don't know whether your code has any additional external dependencies,
log4net already has more than it should for some people (ASP.NET).  Maybe not bundling the appender with
log4net but rather publishing it as a separate download via github/bintray/nuget/you-name-it is the
better approach?  You'd decouple yourself from log4net's release cycle (realistically we currently
move at the speed of continental drift) and could make the appender available to users immediately.  We
could and should link from log4net's website to your appender prominently.

> Google spreadsheet appender
> ---------------------------
>
>                 Key: LOG4NET-446
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-446
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 1.2.13
>            Reporter: Thang Cao
>              Labels: features
(Continue reading)

Justin Dearing (JIRA | 17 Nov 15:34 2014
Picon

[jira] [Commented] (LOG4NET-446) Google spreadsheet appender


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

Justin Dearing commented on LOG4NET-446:
----------------------------------------

This looks awesome. I'm not personally on the log4net team, so I can't speak for if this would make it in. 

You would need to fork log4net on github, add your code to that fork and send a pull request. Reference that in
this jira ticket.

I'd be interested in using this appender. A poor man's loogly.

> Google spreadsheet appender
> ---------------------------
>
>                 Key: LOG4NET-446
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-446
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 1.2.13
>            Reporter: Thang Cao
>              Labels: features
>             Fix For: 1.3.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
(Continue reading)

Thang Cao (JIRA | 17 Nov 03:29 2014
Picon

[jira] [Created] (LOG4NET-446) Google spreadsheet appender

Thang Cao created LOG4NET-446:
---------------------------------

             Summary: Google spreadsheet appender
                 Key: LOG4NET-446
                 URL: https://issues.apache.org/jira/browse/LOG4NET-446
             Project: Log4net
          Issue Type: New Feature
          Components: Appenders
    Affects Versions: 1.2.13
            Reporter: Thang Cao
             Fix For: 1.3.0

This is not really an issue!
Someday ago I developed an appender to submit logging events to google spreadsheets for .net compact (2.0
++) and .net full.
I want to contribute it to log4net but the problem is that I do not know how to do.
Does everyone can help ?

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

Dominik Psenner (JIRA | 29 Oct 20:56 2014
Picon

[jira] [Commented] (LOG4NET-445) the log content can not write the right files by date


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

Dominik Psenner commented on LOG4NET-445:
-----------------------------------------

Is this actually a bug? If the local time was changed I would want to see that in the logfiles.

> the log content can not write the right files by date
> -----------------------------------------------------
>
>                 Key: LOG4NET-445
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-445
>             Project: Log4net
>          Issue Type: Task
>         Environment: visual studio 2010 ,net framework 4.0
>            Reporter: cwguang
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
>  Change the system date,for example ,change May  1st  to May 2nd,log4net will create a new log
20140502log.txt.but when you chang the date back to May 1st,log4net  still write the log content in
20140502log.txt. it should write the log content  to  20140501log.txt

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

(Continue reading)

cwguang (JIRA | 28 Oct 06:45 2014
Picon

[jira] [Created] (LOG4NET-445) the log content can not write the right files by date

cwguang created LOG4NET-445:
-------------------------------

             Summary: the log content can not write the right files by date
                 Key: LOG4NET-445
                 URL: https://issues.apache.org/jira/browse/LOG4NET-445
             Project: Log4net
          Issue Type: Task
         Environment: visual studio 2010 ,net framework 4.0
            Reporter: cwguang

 Change the system date,for example ,change May  1st  to May 2nd,log4net will create a new log
20140502log.txt.but when you chang the date back to May 1st,log4net  still write the log content in
20140502log.txt. it should write the log content  to  20140501log.txt

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

Bruno Marotta (JIRA | 24 Oct 11:10 2014
Picon

[jira] [Created] (LOG4NET-444) XmlHierarchyConfigurator is not extensible

Bruno Marotta created LOG4NET-444:
-------------------------------------

             Summary: XmlHierarchyConfigurator is not extensible
                 Key: LOG4NET-444
                 URL: https://issues.apache.org/jira/browse/LOG4NET-444
             Project: Log4net
          Issue Type: Improvement
          Components: Core
    Affects Versions: 1.2.13
         Environment: Any
            Reporter: Bruno Marotta
             Fix For: 1.2 Maintenance Release

Although the class XmlHierarchyConfigurator has many protected methods, none of them are marked as
virtual, making it impossible to be extended. This would be a really minor change and would allow the
extension of the XML parsing (for instance, for merging different XML files).

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

Dominik Psenner (JIRA | 22 Oct 08:44 2014
Picon

[jira] [Commented] (LOG4NET-443) Logger.CallAppenders


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

Dominik Psenner commented on LOG4NET-443:
-----------------------------------------

Or maybe you could try to use several remoting appenders that send events to one remoting sink which then
writes to the log files? This could be a safe way to abort threads without leaking locks since every thread
has his own appender and does not have to be synchronized with the other threads.

> Logger.CallAppenders
> --------------------
>
>                 Key: LOG4NET-443
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-443
>             Project: Log4net
>          Issue Type: Bug
>    Affects Versions: 1.2.13
>         Environment: Windows service implemented with .NET 4.5  using Log4Net 1.2.13 on Windows 2008 R2
>            Reporter: Calin Pavel
>            Priority: Critical
>         Attachments: log4net.xml
>
>
> I do have an .NET application (Windows Service) that collects data from a lot of sources (DBs, log files,
machines event logs, ...) and uses Log4Net to log details of the actions / execution.  As expected, I'm
using a high number of threads to collect data, threads that are writing logs in some files (RollingFileAppenderer).
> Lately it happens that the entire application is BLOCKED because all threads were trying to acquire a read
(Continue reading)

Dominik Psenner (JIRA | 21 Oct 16:35 2014
Picon

[jira] [Commented] (LOG4NET-443) Logger.CallAppenders


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

Dominik Psenner commented on LOG4NET-443:
-----------------------------------------

Then this one might be hitting you here:

http://joeduffyblog.com/2007/01/29/monitorenter-thread-aborts-and-orphaned-locks/

Quite worrying .. That blog post tells us this: THOU SHALL NOT ABORT THREADS. :-) As far as I can understand
this you will have to work around this issue by untangling the threads.

> Logger.CallAppenders
> --------------------
>
>                 Key: LOG4NET-443
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-443
>             Project: Log4net
>          Issue Type: Bug
>    Affects Versions: 1.2.13
>         Environment: Windows service implemented with .NET 4.5  using Log4Net 1.2.13 on Windows 2008 R2
>            Reporter: Calin Pavel
>            Priority: Critical
>         Attachments: log4net.xml
>
>
> I do have an .NET application (Windows Service) that collects data from a lot of sources (DBs, log files,
(Continue reading)

Calin Pavel (JIRA | 21 Oct 14:32 2014
Picon

[jira] [Commented] (LOG4NET-443) Logger.CallAppenders


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

Calin Pavel commented on LOG4NET-443:
-------------------------------------

It's a Win 2008 R2 x64

> Logger.CallAppenders
> --------------------
>
>                 Key: LOG4NET-443
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-443
>             Project: Log4net
>          Issue Type: Bug
>    Affects Versions: 1.2.13
>         Environment: Windows service implemented with .NET 4.5  using Log4Net 1.2.13 on Windows 2008 R2
>            Reporter: Calin Pavel
>            Priority: Critical
>         Attachments: log4net.xml
>
>
> I do have an .NET application (Windows Service) that collects data from a lot of sources (DBs, log files,
machines event logs, ...) and uses Log4Net to log details of the actions / execution.  As expected, I'm
using a high number of threads to collect data, threads that are writing logs in some files (RollingFileAppenderer).
> Lately it happens that the entire application is BLOCKED because all threads were trying to acquire a read
lock, like in the stack trace:
> 000000001ac3d998 00000000774715fa [HelperMethodFrame: 000000001ac3d998] System.Threading.Thread.SleepInternal(Int32)
(Continue reading)

Dominik Psenner (JIRA | 21 Oct 13:59 2014
Picon

[jira] [Commented] (LOG4NET-443) Logger.CallAppenders


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

Dominik Psenner commented on LOG4NET-443:
-----------------------------------------

This could be indeed an orphaned lock issue if thread aborts happen regularily. Is your Win2008 server
running on x64 or x32?

> Logger.CallAppenders
> --------------------
>
>                 Key: LOG4NET-443
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-443
>             Project: Log4net
>          Issue Type: Bug
>    Affects Versions: 1.2.13
>         Environment: Windows service implemented with .NET 4.5  using Log4Net 1.2.13 on Windows 2008 R2
>            Reporter: Calin Pavel
>            Priority: Critical
>         Attachments: log4net.xml
>
>
> I do have an .NET application (Windows Service) that collects data from a lot of sources (DBs, log files,
machines event logs, ...) and uses Log4Net to log details of the actions / execution.  As expected, I'm
using a high number of threads to collect data, threads that are writing logs in some files (RollingFileAppenderer).
> Lately it happens that the entire application is BLOCKED because all threads were trying to acquire a read
lock, like in the stack trace:
(Continue reading)


Gmane