RemotingAppender and strong names in .NET 1.1

["Hogeboom, J. (Jaap)" <Ja...@vep.akzonobel.com>]

Dear all,

 

RemoteAppender does not seem to work with strong name log4net assembly
in .net 1.1

Top of Form

 

This bug appears when the strong named release log4net.dll assembly from
log4net1.2.0-beta8 is used in in the RemoteAppender demo from
log4net1.2.0-beta5.

The RemoteAppender on the server seems to have no persmission to receive
the LogEvent from the client. The 
RemoteAppender works fine if you do not use strong named version of the
dll.

The following error message appears on the client:
log4net:ERROR AppenderAttachedImpl: Failed to Close appender
[RemotingAppender]
System.Runtime.Serialization.SerializationException: 
Because of security restrictions, the type log4net.spi.LoggingEvent
cannot be accessed. ---> 
System.Security.SecurityException: Request failed.
at 
System.Security.SecurityRuntime.FrameDescSetHelper(FrameSecurityDescript
or secDesc, PermissionSet 
demandSet, PermissionSet& alteredDemandSet)
at 
System.Runtime.Serialization.FormatterServices.nativeGetSafeUninitialize
dObject(RuntimeType type)
at 
System.Runtime.Serialization.FormatterServices.GetSafeUninitializedObjec
t(Type type)
--- End of inner exception stack trace ---

Server stack trace: 
at 
System.Runtime.Serialization.FormatterServices.GetSafeUninitializedObjec
t(Type type)
at 
System.Runtime.Serialization.Formatters.Binary.ObjectReader.ParseObject(
ParseRecord pr)
at 
System.Runtime.Serialization.Formatters.Binary.ObjectReader.Parse(ParseR
ecord pr)
at 
System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObject
WithMapTyped
(BinaryObjectWithMapTyped record)
at 
System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObject
WithMapTyped(BinaryHeaderEnum 
binaryHeaderEnum)
at 
System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at 
System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(
HeaderHandler handler, 
__BinaryParser serParser, Boolean fCheck, IMethodCallMessage
methodCallMessage)
at 
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deseriali
ze(Stream serializationStream, 
HeaderHandler handler, Boolean fCheck, IMethodCallMessage
methodCallMessage)
at 
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.UnsafeDes
erialize(Stream serializationStream, HeaderHandler handler)
at 
System.Runtime.Remoting.Channels.CoreChannel.DeserializeBinaryRequestMes
sage(String objectUri, Stream 
inputStream, Boolean bStrictBinding, TypeFilterLevel securityLevel)
at 
System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessag
e(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.IRemoteLoggingSink.LogEvents(LoggingEvent[] events)
at log4net.Appender.RemotingAppender.SendBuffer(LoggingEvent[] events)
at 
log4net.Appender.BufferingAppenderSkeleton.SendBuffer(CyclicBuffer
buffer)
at 
log4net.Appender.BufferingAppenderSkeleton.OnClose()
at log4net.Appender.AppenderSkeleton.Close()
at 
log4net.helpers.AppenderAttachedImpl.RemoveAllAppenders()
The program '[2796] RemotingClient.exe' has exited with code 0 (0x0).

Sincerely,
Jaap (jaap.hogeboom@akzonobel.com) 

Bottom of Form