[Mono-devel-list] Remoting Problem

Lluis Sanchez lluis at ximian.com
Mon Feb 7 12:07:35 EST 2005


Hi Willi,

The best way of reporting this kind of issues is to fill a bug report in
bugzilla.ximian.com, providing information about the mono version you
are using, and providing a simple test application we can use to
reproduce the problem.

Thanks!
Lluis.

On dg, 2005-02-06 at 16:36 +0100, Willibald Krenn wrote:
> Hi!
> 
> I did try to investigate this myself, but I really don't know where to 
> start looking and as this is some kind of showstopper, I ask for your help.
> 
> For testing purposes I've built some application that consists of a 
> server and a client connected via some remoting channel. Everything runs 
> fine if I have a 1:1 (Server:Client) relation. If, however, I go to some 
> 1:N (N > 1) configuration, things start falling apart. (I've tested this 
> under MS NET 1.1 on XP with 1:4 so the application itself is -AFAICT- 
> not to blame for failure.)
> 
> Below you can find the exception messages Mono throws on my AMD64 system 
> when I try to run 2 or more clients concurrently. The error happens at 
> different locations, at different running times (sometimes no error at 
> all). BTW: The client is concurrently invoked in the same directory in 
> different shells. The server is also invoked in the same directory in 
> another shell.
> 
> Most of the time only one Client application manages to finish  - all 
> other instances give up with one of the exception messages below.
> 
> 
> Any hints greatly appreciated,
>   Willi
> 
> 
> 
> 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[]&)
> 
> 
> --------------------------------------------------------------------------
> Unhandled Exception: System.InvalidOperationException: Token 
> StartAttribute in state Content would result in an invalid XML document.
> 
> Server stack trace:
> in <0x008b6> System.Xml.XmlTextWriter:WriteStartAttribute 
> (string,string,string)
> in <0x00033> System.Xml.XmlWriter:WriteAttributeString 
> (string,string,string,string)
> in <0x00083> 
> System.Runtime.Serialization.Formatters.Soap.SoapWriter:Href (long)
> in <0x000f9> 
> System.Runtime.Serialization.Formatters.Soap.SoapWriter:SerializeComponent 
> (object,bool)
> in <0x00294> 
> System.Runtime.Serialization.Formatters.Soap.SoapWriter:SerializeSimpleObject 
> (object,long)
> in <0x0019a> 
> System.Runtime.Serialization.Formatters.Soap.SoapWriter:SerializeObject 
> (object,long)
> in <0x001b9> 
> System.Runtime.Serialization.Formatters.Soap.SoapWriter:WriteObjectQueue ()
> in <0x00481> 
> System.Runtime.Serialization.Formatters.Soap.SoapWriter:Serialize 
> (object,System.Runtime.Remoting.Messaging.Header[],System.Runtime.Serialization.Formatters.FormatterTypeStyle,System.Runtime.Serialization.Formatters.FormatterAssemblyStyle)
> in <0x00141> 
> System.Runtime.Serialization.Formatters.Soap.SoapFormatter:Serialize 
> (System.IO.Stream,object,System.Runtime.Remoting.Messaging.Header[])
> in <0x00038> 
> System.Runtime.Serialization.Formatters.Soap.SoapFormatter:Serialize 
> (System.IO.Stream,object)
> in <0x004cb> 
> System.Runtime.Remoting.Channels.SoapServerFormatterSink:ProcessMessage 
> (System.Runtime.Remoting.Channels.IServerChannelSinkStack,System.Runtime.Remoting.Messaging.IMessage,System.Runtime.Remoting.Channels.ITransportHeaders,System.IO.Stream,System.Runtime.Remoting.Messaging.IMessage&,System.Runtime.Remoting.Channels.ITransportHeaders&,System.IO.Stream&)
> 
> 
> Exception rethrown at [0]:
> 
> in <0x00ab5> System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke 
> (System.Runtime.Remoting.Proxies.RealProxy,System.Runtime.Remoting.Messaging.IMessage,System.Exception&,object[]&)
> --------------------------------------------------------------------------
> 
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list




More information about the Mono-devel-list mailing list