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, 23 May 2012 14:56:41 +0000 (UTC)
From: "Dominik Psenner (JIRA)" <jira@apache.org>
To: log4net-dev@logging.apache.org
Message-ID: <930731071.11830.1337785001236.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <624316906.7421.1337683961488.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Comment Edited] (LOG4NET-341) RemotingAppender Error
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dominik Psenner edited comment on LOG4NET-341 at 5/23/12 2:55 PM:
------------------------------------------------------------------

There's something fishy going on with how log4net 1.2.11 serializes log events to be sent to the server on client side. It most probably includes some information that the server can deserialize only if the calling assemblies of the 1.2.11 client are available to him. I'll have to bisect the revision since when it is broken and this could take some time. Please be patient. Until then it should work if you have the client assemblies available on server side (a simple copy paste is enough).
                
      was (Author: nachbarslumpi):
    There's something fishy going on with how log4net 1.2.11 client serializes log events sent to the server. It most probably includes some information that the server can deserialize only if the calling assemblies of the 1.2.11 client are available to him. I'll have to bisect the revision since when it is broken and this could take some time. Please be patient. Until then it should work if you have the client assemblies available on server side (a simple copy paste is enough).
                  
> RemotingAppender Error
> ----------------------
>
>                 Key: LOG4NET-341
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-341
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.11
>         Environment: Windows 7, .Net Framework 4, VS C# 2010
>            Reporter: Sandra Neumann
>            Priority: Blocker
>             Fix For: 1.2.10
>
>         Attachments: screenshot-1.jpg
>
>
> I have a solution with a console application (.Net 4 and log4net v1.2.11) which implement the Remoting sink - server side. And a WPF or WindowsForms application - client side. The framework version on the client side doesn't matter. But the log4net version is different. On v1.2.10 anything is ok. When I reference the client with v1.2.11 throw this error: 
> log4net:ERROR [RemotingAppender] ErrorCode: GenericFailure. Failed in SendBufferCallback
> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not load file or assembly 'WpfTestApplication, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Das System kann die angegebene Datei nicht finden.
>    at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
>    at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
>    at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection, Boolean suppressSecurityChecks)
>    at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
>    at System.Reflection.Assembly.Load(String assemblyString)
>    at System.Runtime.Serialization.FormatterServices.LoadAssemblyFromString(String assemblyName)
>    at System.Reflection.MemberInfoSerializationHolder..ctor(SerializationInfo info, StreamingContext context)
>    --- End of inner exception stack trace ---
> Server stack trace: 
>    at System.RuntimeMethodHandle._SerializationInvoke(IRuntimeMethodInfo method, Object target, SignatureStruct& declaringTypeSig, SerializationInfo info, StreamingContext context)
>    at System.Runtime.Serialization.ObjectManager.CompleteISerializableObject(Object obj, SerializationInfo info, StreamingContext context)
>    at System.Runtime.Serialization.ObjectManager.FixupSpecialObject(ObjectHolder holder)
>    at System.Runtime.Serialization.ObjectManager.DoFixups()
>    at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
>    at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
>    at System.Runtime.Remoting.Channels.CoreChannel.DeserializeBinaryRequestMessage(String objectUri, Stream inputStream, Boolean bStrictBinding, TypeFilterLevel securityLevel)
>    at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, Stream& responseStream)
> Exception rethrown at [0]: 
>    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
>    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
>    at log4net.Appender.RemotingAppender.IRemoteLoggingSink.LogEvents(LoggingEvent[] events)
>    at log4net.Appender.RemotingAppender.SendBufferCallback(Object state)

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