Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET Dev" <log4net-dev@logging.apache.org>
Date: Wed, 24 Jun 2015 10:03:04 +0000 (UTC)
From: "Dominik Psenner (JIRA)" <jira@apache.org>
To: log4net-dev@logging.apache.org
Message-ID: <JIRA.12673082.1381344049000.697.1435140184835@Atlassian.JIRA>
In-Reply-To: <JIRA.12673082.1381344049000@Atlassian.JIRA>
References: <JIRA.12673082.1381344049000@Atlassian.JIRA>
 <JIRA.12673082.1381344049766@arcas>
Subject: [jira] [Commented] (LOG4NET-398) SerializationException after
 setting a LogicalThreadContext property
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dominik Psenner commented on LOG4NET-398:
-----------------------------------------

You are right, AppDomains shouldn't be able to share information unless the objects are serialized/deserialized. But to me it sounds strange that a dictionary tries to cross into another AppDomain. At first sight, this shouldn't happen at all. Can you work out why this happens?

> SerializationException after setting a LogicalThreadContext property
> --------------------------------------------------------------------
>
>                 Key: LOG4NET-398
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-398
>             Project: Log4net
>          Issue Type: Task
>          Components: Core
>    Affects Versions: 1.2.12
>         Environment: Visual Studio 2010
>            Reporter: Thomas Meum
>            Priority: Minor
>              Labels: triaged
>
> I have found that accessing Page.Request.Url after setting a LogicalThreadContext property causes a SerializationException with the following message: Type is not resolved for member 'log4net.Util.PropertiesDictionary,log4net, Version=1.2.12.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a'.
> I have been able to reproduce the problem on two different machines with the following steps:
> 1. Create a new ASP.NET Empty Web Application
> 2. Add a reference to log4net.dll
> 3. Add a new Web Form
> 4. Add the following code to Page_Load:
>     log4net.LogicalThreadContext.Properties["Test"] = 1;
>     Uri url = Request.Url;
> 5. Hit F5


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