Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=81811 --- shadow/81811 2007-06-05 12:12:38.000000000 -0400 +++ shadow/81811.tmp.28366 2007-06-05 12:12:38.000000000 -0400 @@ -0,0 +1,90 @@ +Bug#: 81811 +Product: Mono: Runtime +Version: 1.2 +OS: +OS Details: +Status: NEW +Resolution: +Severity: +Priority: Major +Component: remoting +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +Summary: Log4net Remoting appender don't work with mono + +Description of Problem: +I try to use to log4net RemotingAppender with mono (in order to create a +centralised log server for all our web applications) + + +Steps to reproduce the problem: +1. Create a simple RemotingAppender + <appender name="RemotingAppender" +type="log4net.Appender.RemotingAppender" > + <sink value="tcp://localhost:1234/LoggingSink" /> + <lossy value="false" /> + <bufferSize value="1" /> + <onlyFixPartialEventData value="true" /> + </appender> +2. Create the server +3. + +Actual Results: + +log4net:ERROR XmlHierarchyConfigurator: Could not create Appender +[RemotingAppen +der] of type [log4net.Appender.RemotingAppender]. Reported error follows. +System.Runtime.Remoting.RemotingException: Cannot create channel sink to +connect + to URL tcp://localhost:1234/LoggingSink. An appropriate channel has +probably no +t been registered. + at System.Runtime.Remoting.RemotingServices.GetClientChannelSinkChain +(System. +String url, System.Object channelData, System.String& objectUri) [0x0003e] +in /h +ome/hubert/mono/mcs/class/corlib/System.Runtime.Remoting/RemotingServices.cs:674 + + at System.Runtime.Remoting.RemotingServices.GetOrCreateClientIdentity +(System. +Runtime.Remoting.ObjRef objRef, System.Type proxyType, System.Object& +clientProx +y) [0x0001e] in +/home/hubert/mono/mcs/class/corlib/System.Runtime.Remoting/Remot +ingServices.cs:613 + at System.Runtime.Remoting.RemotingServices.GetRemoteObject +(System.Runtime.Re +moting.ObjRef objRef, System.Type proxyType) [0x00000] in +/home/hubert/mono/mcs/ +class/corlib/System.Runtime.Remoting/RemotingServices.cs:726 + at System.Runtime.Remoting.RemotingServices.Connect (System.Type +classToProxy, + System.String url, System.Object data) [0x00009] in +/home/hubert/mono/mcs/class +/corlib/System.Runtime.Remoting/RemotingServices.cs:183 + at System.Activator.GetObject (System.Type type, System.String url, +System.Obj +ect state) [0x00012] in +/home/hubert/mono/mcs/class/corlib/System/Activator.cs:3 +02 + at log4net.Appender.RemotingAppender.ActivateOptions () [0x0001c] in +/home/hub +ert/Librairies DotNet/log4net/src/Appender/RemotingAppender.cs:148 + at log4net.Repository.Hierarchy.XmlHierarchyConfigurator.ParseAppender +(System +.Xml.XmlElement appenderElement) [0x0019a] in /home/hubert/Librairies +DotNet/log +4net/src/Repository/Hierarchy/XmlHierarchyConfigurator.cs:329 +Expected Results: + + +How often does this happen? +always + +Additional Information: +it works well on MS.NET 1.1 it should works too with mono... +See the attached monodevelop solution test case! _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
