You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Rob Prouse (JIRA)" <ji...@apache.org> on 2010/07/29 22:17:15 UTC
[jira] Commented: (LOG4NET-265) RemoteFileAppender Tests fail on
Windows 7
[ https://issues.apache.org/jira/browse/LOG4NET-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893801#action_12893801 ]
Rob Prouse commented on LOG4NET-265:
------------------------------------
Further testing of my patch, it looks like it is not the FullFixTest that is the problem, it seems that the first event to get logged gets lost. If I disable the FullFixTest, then the next test fails.
> RemoteFileAppender Tests fail on Windows 7
> ------------------------------------------
>
> Key: LOG4NET-265
> URL: https://issues.apache.org/jira/browse/LOG4NET-265
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 1.2.11
> Environment: Windows 7 32bit
> Reporter: Rob Prouse
> Priority: Minor
> Attachments: log4net-265.patch
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Compiled the version of log4net in the repository and ran the unit tests. All of the RemotingAppenderTests fail. Enabling internal logging gives the following error.
> log4net:ERROR [RemotingAppender] ErrorCode: GenericFailure. Failed in SendBufferCallback
> System.Runtime.Serialization.SerializationException: Because of security restrictions, the type System.Runtime.Remoting.ObjRef cannot be accessed. ---> System.Security.SecurityException: Request failed.
> at System.Runtime.Serialization.FormatterServices.nativeGetSafeUninitializedObject(RuntimeType type)
> at System.Runtime.Serialization.FormatterServices.GetSafeUninitializedObject(Type type)
> The action that failed was:
> Demand
> The type of the first permission that failed was:
> System.Security.Permissions.SecurityPermission
> The first permission that failed was:
> <IPermission class="System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
> version="1"
> Flags="Infrastructure"/>
> The demand was for:
> <PermissionSet class="System.Security.PermissionSet"
> version="1">
> <IPermission class="System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
> version="1"
> Flags="Infrastructure"/>
> </PermissionSet>
> The only permitted permissions were:
> <PermissionSet class="System.Security.PermissionSet"
> version="1">
> <IPermission class="System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
> version="1"
> Flags="SerializationFormatter"/>
> </PermissionSet>
> The method that caused the failure was:
> System.Runtime.Remoting.Channels.ServerProcessing ProcessMessage(System.Runtime.Remoting.Channels.IServerChannelSinkStack, System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Channels.ITransportHeaders, System.IO.Stream, System.Runtime.Remoting.Messaging.IMessage ByRef, System.Runtime.Remoting.Channels.ITransportHeaders ByRef, System.IO.Stream ByRef)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.