[Mono-bugs] [Bug 72344][Maj] New - Remoting Stopper: System.Xml.XmlException: Document element did not appear

[bugzilla-daemon@bugzilla.ximian.com]

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 willibald.krenn@gmx.at.

http://bugzilla.ximian.com/show_bug.cgi?id=72344

--- shadow/72344	2005-02-08 11:09:51.000000000 -0500
+++ shadow/72344.tmp.6519	2005-02-08 11:09:51.000000000 -0500
@@ -0,0 +1,90 @@
+Bug#: 72344
+Product: Mono: Runtime
+Version: unspecified
+OS: 
+OS Details: SuSE 9.0 AMD64
+Status: NEW   
+Resolution: 
+Severity: 024 Three days
+Priority: Major
+Component: remoting
+AssignedTo: lluis@ximian.com                            
+ReportedBy: Willibald.Krenn@gmx.at               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Remoting Stopper: System.Xml.XmlException: Document element did not appear
+
+Description of Problem:
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+1:N (Server:Client) does not work as expected: Any client N > 1 will die.
+Application tested on MS .NET in 1:4 config - so it's probably an error in
+mono. Simple testcase attached.
+
+
+Steps to reproduce the problem:
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+1. Compile attached testcase. (NANT build script included)
+2. open at least three shells in the directory where you built the example;
+   shell 1: mono --profile=default:stat LiberCmd.exe
+   shell 2&3: mono LiberLastTest.exe (don't press return)
+3. It's important now to start the two (or more) client instances at the
+same time by pressing return.
+   The bug is more likely to happen if the clients are well-mixed served..
+(That's the reason to start the
+   server with sampling profiler on: Due to the signals it's more likely
+that the threads are executed intermixed.)
+
+Actual Results:
+~~~~~~~~~~~~~~~
+
+Clients will die with
+
+Unhandled Exception: System.Xml.XmlException: Document element did not
+appear.  Line 1, position 1.
+in <0x0023b> System.Xml.XmlTextReader:Read ()
+in <0x00083> System.Xml.XmlReader:MoveToContent ()
+in <0x000cc>
+System.Runtime.Serialization.Formatters.Soap.SoapReader:Deserialize
+(System.IO.Stream,System.Runtime.Serialization.Formatters.ISoapMessage)
+in <0x00108>
+System.Runtime.Serialization.Formatters.Soap.SoapFormatter:Deserialize
+(System.IO.Stream,System.Runtime.Remoting.Messaging.HeaderHandler)
+in <0x00030>
+System.Runtime.Serialization.Formatters.Soap.SoapFormatter:Deserialize
+(System.IO.Stream)
+in <0x0009b>
+System.Runtime.Remoting.Channels.SoapClientFormatterSink:DeserializeMessage
+(System.IO.Stream,System.Runtime.Remoting.Channels.ITransportHeaders,System.Runtime.Remoting.Messaging.IMethodCallMessage,System.Runtime.Remoting.Channels.SoapMessageFormatter)
+in <0x00159>
+System.Runtime.Remoting.Channels.SoapClientFormatterSink:SyncProcessMessage
+(System.Runtime.Remoting.Messaging.IMessage)
+in <0x00419> System.Runtime.Remoting.Proxies.RemotingProxy:Invoke
+(System.Runtime.Remoting.Messaging.IMessage)
+in <0x0046a> System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke
+(System.Runtime.Remoting.Proxies.RealProxy,System.Runtime.Remoting.Messaging.IMessage,System.Exception&,object[]&)
+
+
+Expected Results:
+~~~~~~~~~~~~~~~~~
+
+No exception.
+
+
+How often does this happen?
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+It depends on how good the server is switching between the clients. The
+more switches the more likely.
+If it can not be reproduced, I can send a modified version of mono that
+includes some early version of the
+continuious optimization framework: The bug will happen everytime more than
+one client is run.
+
+Additional Information:
+~~~~~~~~~~~~~~~~~~~~~~~
+
+Small testcase with nant build script attached.
+Tested on AMD64.