Uploaded image for project: 'Log4net'
  1. Log4net
  2. LOG4NET-265

RemoteFileAppender Tests fail on Windows 7

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 1.2.11
    • Appenders
    • None
    • Windows 7 32bit

    Description

      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)

      Attachments

        1. log4net-265.patch
          1 kB
          Rob Prouse

        Activity

          People

            Unassigned Unassigned
            rprouse Rob Prouse
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 3h
                3h
                Remaining:
                Remaining Estimate - 3h
                3h
                Logged:
                Time Spent - Not Specified
                Not Specified