Kenny Clement (JIRA | 13 Aug 12:12 2008
Picon

[jira] Created: (LOG4NET-167) ArrayOutOfBounds Exception in MemoryAppender.getEvents()

ArrayOutOfBounds Exception in MemoryAppender.getEvents()
--------------------------------------------------------

                 Key: LOG4NET-167
                 URL: https://issues.apache.org/jira/browse/LOG4NET-167
             Project: Log4net
          Issue Type: Bug
          Components: Appenders
    Affects Versions: 1.2.10
         Environment: Windows Vista and XP.
            Reporter: Kenny Clement

Getting this every once in a while.
No specific reproduction scenario.

Destination array was not long enough. Check destIndex and length, and the array's lower bounds.
   at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32
destinationIndex, Int32 length, Boolean reliable)
   at System.Collections.ArrayList.ToArray(Type type)
   at log4net.Appender.MemoryAppender.GetEvents()

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Manfred Braun (JIRA | 14 Aug 00:28 2008
Picon

[jira] Created: (LOG4NET-168) New property ReplyTo address for the SmtpAppender required

New property ReplyTo address for the SmtpAppender required
----------------------------------------------------------

                 Key: LOG4NET-168
                 URL: https://issues.apache.org/jira/browse/LOG4NET-168
             Project: Log4net
          Issue Type: New Feature
          Components: Appenders
    Affects Versions: 1.2.10
         Environment: log4net 1.2.10, Net 1.1/Net 2.0, Windows, Linux
            Reporter: Manfred Braun

log4net is often used in administrative utilities and used to send mails in case of errors. It is total
unrealistic to assume each used mail-address really exists. Mostly "virtual address" are used,
means:They do not have any pop3 mailbox. So, if sending mail fails from the smpt server, no user can be
informed. A property, which allows to specify the "reply-to" address on the SmtpAppender would solve
this problem.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

kiran khatri (JIRA | 19 Aug 01:47 2008
Picon

[jira] Created: (LOG4NET-169) Hot to append log data to multiple tables depending on severity of statement using adonetappender?

Hot to append log data to multiple tables depending on severity of statement using adonetappender?
--------------------------------------------------------------------------------------------------

                 Key: LOG4NET-169
                 URL: https://issues.apache.org/jira/browse/LOG4NET-169
             Project: Log4net
          Issue Type: Task
          Components: Appenders
         Environment: Windows server 2003 and asp.net website
            Reporter: kiran khatri

I want to log statement to different tables in database depending on the severity of statement, for example
logging all warn messages to warnlog table and all errors and info to otherlog table. Can this be acheived
using log4net?

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Wood, Brandon C (DOA | 20 Aug 17:58 2008

how to submit code to log4net

I have created a web service appender for a project I'm working on, and would like to contribute the code to log4net.  There are several places on the website that talk about why you should contribute your code to the project, but on the page about Subversion, it says you need an account to commit any code.  So my question is, how can I submit my code?  If I need a Subversion account, how do I get one?

 

Cheers,

 

Brandon Wood

Ron Grabowski | 21 Aug 01:05 2008
Picon

Re: how to submit code to log4net

Create a ticket:

 https://issues.apache.org/jira/browse/LOG4NET

and upload the patch there so people can review it and it'll get merged into the code.

----- Original Message ----
From: "Wood, Brandon C (DOA)" <brandon.wood <at> alaska.gov>
To: log4net-dev <at> logging.apache.org
Sent: Wednesday, August 20, 2008 11:58:49 AM
Subject: how to submit code to log4net

<!-- _filtered {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered {font-family:Consolas;panose-1:2 11 6 9 2 2 4 3 2 4;} p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", "sans-serif";} a:link, span.MsoHyperlink {color:blue;text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {color:purple;text-decoration:underline;} p.MsoPlainText, li.MsoPlainText, div.MsoPlainText {margin:0in;margin-bottom:.0001pt;font-size:10.5pt;font-family:Consolas;} span.EmailStyle17 {font-family:"Calibri", "sans-serif";color:windowtext;} span.PlainTextChar {font-family:Consolas;} .MsoChpDefault {} _filtered {margin:1.0in 1.0in 1.0in 1.0in;} div.Section1 {} -->

I have created a web service appender for a project I'm working on, and would like to contribute the code to log4net.  There are several places on the website that talk about why you should contribute your code to the project, but on the page about Subversion, it says you need an account to commit any code.  So my question is, how can I submit my code?  If I need a Subversion account, how do I get one?

 

Cheers,

 

Brandon Wood

Jerry Shea (JIRA | 22 Aug 13:42 2008
Picon

[jira] Created: (LOG4NET-170) Documentation improvement re: fixing and active properties

Documentation improvement re: fixing and active properties
----------------------------------------------------------

                 Key: LOG4NET-170
                 URL: https://issues.apache.org/jira/browse/LOG4NET-170
             Project: Log4net
          Issue Type: Improvement
          Components: Documentation
    Affects Versions: 1.2.10
            Reporter: Jerry Shea
            Priority: Minor

Documentation improvement - see http://www.nabble.com/ASP.NET%2C-AdoNetAppender-and-deferred-property-execution-tt18865968.html

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Jerry Shea (JIRA | 22 Aug 13:44 2008
Picon

[jira] Updated: (LOG4NET-170) Documentation improvement re: fixing and active properties


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

Jerry Shea updated LOG4NET-170:
-------------------------------

    Attachment: fixing.patch

> Documentation improvement re: fixing and active properties
> ----------------------------------------------------------
>
>                 Key: LOG4NET-170
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-170
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 1.2.10
>            Reporter: Jerry Shea
>            Priority: Minor
>         Attachments: fixing.patch
>
>
> Documentation improvement - see http://www.nabble.com/ASP.NET%2C-AdoNetAppender-and-deferred-property-execution-tt18865968.html

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Steven Myron (JIRA | 22 Aug 23:00 2008
Picon

[jira] Created: (LOG4NET-171) Log file locking causing an error to be thrown from the RollingFileAppender

Log file locking causing an error to be thrown from the RollingFileAppender
---------------------------------------------------------------------------

                 Key: LOG4NET-171
                 URL: https://issues.apache.org/jira/browse/LOG4NET-171
             Project: Log4net
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.2.10
         Environment: Windows 2003 Server (scheduled jobs/.exe that may be overlapping)
            Reporter: Steven Myron
            Priority: Critical

Scheduled processes (~ 15 minutes apart) seem to be overlapping possibly causing file sharing violations
for the log file that log4net is writing to.  This file is statically named and is written to using the
RollingFileAppender.  This abruptly terminates the application and presents an unexpected error to the client.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Steven Myron (JIRA | 22 Aug 23:04 2008
Picon

[jira] Updated: (LOG4NET-171) Log file locking causing an error to be thrown from the RollingFileAppender


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

Steven Myron updated LOG4NET-171:
---------------------------------

    Attachment: original issue.jpg

> Log file locking causing an error to be thrown from the RollingFileAppender
> ---------------------------------------------------------------------------
>
>                 Key: LOG4NET-171
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-171
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.10
>         Environment: Windows 2003 Server (scheduled jobs/.exe that may be overlapping)
>            Reporter: Steven Myron
>            Priority: Critical
>         Attachments: original issue.jpg
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> Scheduled processes (~ 15 minutes apart) seem to be overlapping possibly causing file sharing
violations for the log file that log4net is writing to.  This file is statically named and is written to
using the RollingFileAppender.  This abruptly terminates the application and presents an unexpected
error to the client.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

rgrabowski | 23 Aug 20:56 2008
Picon

svn commit: r688397 - in /logging/log4net/trunk: src/Core/LoggingEvent.cs xdocs/src/release/manual/contexts.xml

Author: rgrabowski
Date: Sat Aug 23 11:56:17 2008
New Revision: 688397

URL: http://svn.apache.org/viewvc?rev=688397&view=rev
Log:
Fix for LOG4NET-140. Improve documentation for IFixingRequired to explain how data can be evaluated
immediately when a logging event is created or delayed until being written to an appender.

Modified:
    logging/log4net/trunk/src/Core/LoggingEvent.cs
    logging/log4net/trunk/xdocs/src/release/manual/contexts.xml

Modified: logging/log4net/trunk/src/Core/LoggingEvent.cs
URL: http://svn.apache.org/viewvc/logging/log4net/trunk/src/Core/LoggingEvent.cs?rev=688397&r1=688396&r2=688397&view=diff
==============================================================================
--- logging/log4net/trunk/src/Core/LoggingEvent.cs (original)
+++ logging/log4net/trunk/src/Core/LoggingEvent.cs Sat Aug 23 11:56:17 2008
 <at>  <at>  -228,7 +228,7  <at>  <at> 
 		Exception = 0x100,

 		/// <summary>
-		/// Fix the event properties
+		/// Fix the event properties. Active properties must implement <see cref="IFixingRequired"/> in
order to be eligible for fixing.
 		/// </summary>
 		Properties = 0x200,

Modified: logging/log4net/trunk/xdocs/src/release/manual/contexts.xml
URL: http://svn.apache.org/viewvc/logging/log4net/trunk/xdocs/src/release/manual/contexts.xml?rev=688397&r1=688396&r2=688397&view=diff
==============================================================================
--- logging/log4net/trunk/xdocs/src/release/manual/contexts.xml (original)
+++ logging/log4net/trunk/xdocs/src/release/manual/contexts.xml Sat Aug 23 11:56:17 2008
 <at>  <at>  -149,9 +149,28  <at>  <at> 
                         string by calling the <span class="code">ToString</span> method the current number of bytes 
                         allocated by the garbage collector will be returned and included in the output.
                     </p>
-                    
-                </section>
-                
+					<p>
+						Note that the <span class="code">ToString</span>method will not be
+						called until the <span class="code">LoggingEvent</span>is rendered, as
+						explained in the <a href="#fixing">Fixing</a>section. An active property
+						is not eligible to be fixed unless it implements 
+						<a href="../sdk/log4net.Core.IFixingRequired.html"> IFixingRequired</a>.
+					</p>
+				</section>
+			</section>
+			
+			<section id="fixing" name="Fixing">
+				<p>
+					Some properties, e.g. the current thread property, or any 
+					<a href="#active">active properties</a>, are not realised
+					until their containing <span class="code">LoggingEvent</span>is rendered. If the 
+					<span class="code">LoggingEvent</span>is been sent to a buffering appender (such as 
+					<a href="../sdk/log4net.Appender.AdoNetAppender.html">AdoNetAppender</a>) then this
rendering will not happen
+					unless the <a href="../sdk/log4net.Appender.BufferingAppenderSkeleton.html">
+					BufferingAppenderSkeleton</a>'s <a href="../sdk/log4net.Appender.BufferingAppenderSkeleton.Fix.html">
+					Fix property</a>has been set. In addition, an active property is not eligible to be fixed unless it
implements 
+					<a href="../sdk/log4net.Core.IFixingRequired.html">IFixingRequired</a>.
+				</p>
             </section>

             <section id="stacks" name="Context Stacks">


Gmane