[Mono-bugs] [Bug 81811][Maj] New - Log4net Remoting appender don't work with mono

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Jun 5 12:12:38 EDT 2007

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 informatique.internet at fiducial.fr.


--- 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 Details: 
+Status: NEW   
+Priority: Major
+Component: remoting
+AssignedTo: lluis at ximian.com                            
+ReportedBy: informatique.internet at fiducial.fr               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+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
+Actual Results:
+log4net:ERROR XmlHierarchyConfigurator: Could not create Appender
+der] of type [log4net.Appender.RemotingAppender]. Reported error follows.
+System.Runtime.Remoting.RemotingException: Cannot create channel sink to
+ to URL tcp://localhost:1234/LoggingSink. An appropriate channel has
+probably no
+t been registered.
+  at System.Runtime.Remoting.RemotingServices.GetClientChannelSinkChain
+String url, System.Object channelData, System.String& objectUri) [0x0003e]
+in /h
+  at System.Runtime.Remoting.RemotingServices.GetOrCreateClientIdentity
+Runtime.Remoting.ObjRef objRef, System.Type proxyType, System.Object&
+y) [0x0001e] in
+  at System.Runtime.Remoting.RemotingServices.GetRemoteObject
+moting.ObjRef objRef, System.Type proxyType) [0x00000] in
+  at System.Runtime.Remoting.RemotingServices.Connect (System.Type
+ System.String url, System.Object data) [0x00009] in
+  at System.Activator.GetObject (System.Type type, System.String url,
+ect state) [0x00012] in
+  at log4net.Appender.RemotingAppender.ActivateOptions () [0x0001c] in
+ert/Librairies DotNet/log4net/src/Appender/RemotingAppender.cs:148 
+  at log4net.Repository.Hierarchy.XmlHierarchyConfigurator.ParseAppender
+.Xml.XmlElement appenderElement) [0x0019a] in /home/hubert/Librairies
+Expected Results:
+How often does this happen? 
+Additional Information:
+it works well on MS.NET 1.1 it should works too with mono...
+See the attached monodevelop solution test case!

More information about the mono-bugs mailing list