[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=13178658#comment-13178658
] 

Martin Meixger commented on LOG4NET-87:
---------------------------------------

The AspNetPatternLayoutConverter retrieves the HttpContext.Current properties only when the
LoggingEvent gets rendered via Format().

Unforunately this is much later and in another thread as the fixing of the fields and ThreadProperties.

I see no other way than copying the interested HttpContext properties manually into the ThreadProperties.

> Support ASP.Net related PatternConverters to allow items from the HttpContext.Current.Session,
Cache, Request, etc. to be captured.
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-87
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-87
>             Project: Log4net
>          Issue Type: Wish
>          Components: Core
>    Affects Versions: 1.2.10
>            Reporter: Ron Grabowski
>            Assignee: Ron Grabowski
>            Priority: Minor
>             Fix For: 1.2.11
>

[jira] [Commented] (LOG4NET-288) ADO.Net Appender is not writing all the records to the table in a high load/user scenario.It stops writing to the table untill i restart my app servers.Also sometimes, it drops few records and writes the rest of the records.

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

Tom Tang commented on LOG4NET-288:
----------------------------------

By the system loading you described, you lost the records could be caused by SQL execution timeout.
Due to there's no way to extend the SqlCommand.ExecutionTimeout property in your code and its
configuration, if the thread was blocked by any other logging thread more than 30 sec, it would get
"SqlException:Execution timeout" and drop these message.
By that, your synchronized business code thread would be hanged by log4net till it got the exception returned.

So I don't suggest you to think the way how to extend the execution timeout.

Log4net is not a guarantee tool sot audit log the kind of serious usage, you better find the other tool or
implement by your own.

"Log" is not as the same severity level as "Audit"

If your audit need to be 100% accurate, it will be to be involve a transaction scope, means the auditing
failure shall cause your business logic rollback...That's much more than just a logging.

Best regards

> ADO.Net Appender is not writing all the records to the table in a high load/user scenario.It stops writing
to the table untill i restart my app servers.Also sometimes, it drops few records and writes the rest of the records.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>

[jira] [Commented] (LOG4NET-320) Location Information

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

Adam Davies commented on LOG4NET-320:
-------------------------------------

I agree it would be much more beneficial to relocate the code.  However, the XMLLayout works quite
differently than any other layout in that it has no converter.  The XMLLayout renders itself.

I can see following possiblity:

Move the code as suggested.
In PatternConverter, create a LocationOffset property and a GetLocationInfoByOffset(LoggingEvent)
In each converter that uses Location Information, call base.GetLocationInfoByOffset() for the offset location

I will code and test over the next few days.

> Location Information
> --------------------
>
>                 Key: LOG4NET-320
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-320
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.2.11
>            Reporter: Adam Davies
>            Priority: Minor

SDK docs on apache.org don't display properly

Who owns the log4net nuget package?

Re: Who owns the log4net nuget package?

On 01/14/2012 10:41 PM, Ron Grabowski wrote:
> Does anyone know who owns the log4net nuget package?
> 
> http://nuget.org/packages/log4net
> http://blog.cincura.net/232619-log4net-back-alive-on-nuget/
> 
> We're the 6th most populate package on nuget! Can someone explain what
> it would take to get the nuget package files into our svn repository?

A lot of guessing, but entering the username "cincura.net" as a webpage
leads to http://www.x2develop.com/ and their contact website
http://www.x2develop.com/contact.html shows a contact to "Mgr. Jiří
Činčura". Contacting him could be a good try?

Cheers
--

-- 
Dominik Psenner
## OpenPGP Key Signature #################################
# Key ID: B469318C                                       #
# Fingerprint: 558641995F7EC2D251354C3A49C7E3D1B469318C  #
##########################################################

Re: SDK docs on apache.org don't display properly

On 2012-01-13, Ron Grabowski wrote:

> Anyone know why there are extended chars in most of the log4net ndoc
> files? For example this page has empty-blocks in IE9 and
> triangle-question-marks in Firefox:

No idea, I used the existing ndoc target in the NAnt build file that I
assume has been used for the earlier releases as well.

Stefan

[jira] [Created] (LOG4NET-321) Add AppSettings lookup to configuration reader value setting

Add AppSettings lookup to configuration reader value setting
------------------------------------------------------------

                 Key: LOG4NET-321
                 URL: https://issues.apache.org/jira/browse/LOG4NET-321
             Project: Log4net
          Issue Type: Improvement
          Components: Core
    Affects Versions: 1.2.11
            Reporter: Jonathan Choy
            Priority: Minor

Add wrapper lookup to resolve AppSetting key/value pairs in the same fashion as environment variables
during configuration. This facilitates deploying the same codebase across environments where the
logging configuration differs only by a machine-specific key/value pair that would already be stored,
forex, in the machine.config or a per-server or per-environment local web.config transform, and the
transform is applicable but setting environment variables is not. (AppHarbor style hosting, for a
specific example).

--
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-321) Add AppSettings lookup to configuration reader value setting

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

Jonathan Choy commented on LOG4NET-321:
---------------------------------------

Suggested syntax would be in the same style as $env{value}:

$AppSetting{keyname} would retrieve the setting from ConfigurationManager.AppSetting[keyname] if
present, with not-present using the same missing value semantics as $env.

Suggested semantic enhancement if not present: If in debug mode, report empty key lookup substitutions
from both $env and $AppSetting.

                
> Add AppSettings lookup to configuration reader value setting
> ------------------------------------------------------------
>
>                 Key: LOG4NET-321
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-321
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.11
>            Reporter: Jonathan Choy
>            Priority: Minor
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Add wrapper lookup to resolve AppSetting key/value pairs in the same fashion as environment variables
during configuration. This facilitates deploying the same codebase across environments where the
logging configuration differs only by a machine-specific key/value pair that would already be stored,
forex, in the machine.config or a per-server or per-environment local web.config transform, and the
transform is applicable but setting environment variables is not. (AppHarbor style hosting, for a
specific example).

--
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-322) Conditional compilation symbols for .net4 Release

Conditional compilation symbols for .net4 Release
-------------------------------------------------

                 Key: LOG4NET-322
                 URL: https://issues.apache.org/jira/browse/LOG4NET-322
             Project: Log4net
          Issue Type: Bug
          Components: Builds
    Affects Versions: 1.2.11
         Environment: log4net.vs2010 project
            Reporter: Iso Su

While Debug configuration has a proper list of Conditional compilation symbols
("NET;NET_2_0;NET_4_0"), the Release configuration has them set to "STRONG;NET;NET_1_0;". This
causes problems with a lot of appenders and LogicalThreadContext is not working, since it uses
SetData(), not LogicalSetData()

--
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