[Mono-bugs] [Bug 49997][Nor] New - Cannot remote an object using HttpChannel

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 22 Oct 2003 10:53:49 -0400 (EDT)


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 jsorrels@toptech.com.

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

--- shadow/49997	2003-10-22 10:53:49.000000000 -0400
+++ shadow/49997.tmp.14349	2003-10-22 10:53:49.000000000 -0400
@@ -0,0 +1,134 @@
+Bug#: 49997
+Product: Mono/Class Libraries
+Version: unspecified
+OS: Red Hat 9.0
+OS Details: RedHat 9.0
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: System
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: jsorrels@toptech.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Cannot remote an object using HttpChannel
+
+Description of Problem:
+
+I cannot remote an object using the HttpChannel object, I can remote the 
+same object on the same machine using the TcpChannel and a Binary 
+formatter.
+
+This functionality may not be implemented yet, if so, I apologize in 
+advance for this report.
+
+Steps to reproduce the problem:
+
+Created an object to remote from Mono using an Http channel and 
+SoapServerFormatterSinkProvider, I can also reproduce the problem with 
+the BinaryServerFormatterSinkProvider on the HttpChannel.
+
+The client requesting the object is a .net v1.1 client running on 
+WindowsXP-Pro
+
+Actual Results:
+
+Error:
+The remote server returned an error: (400) Bad Request.
+
+Expected Results:
+
+A remoted object as I can produce with TcpChannel and 
+BinaryServerFormatterSinkProvider on the same two machines.
+
+How often does this happen? 
+
+Consistant
+
+
+Additional Information:
+
+Either scenerio HttpChannel or TcpChannel works as expected .Net v1.1 <-
+> .Net v1.1
+
+
+The soap message off the wire:
+
+POST /DeviceMonitor HTTP/1.1
+User-Agent: Mozilla/4.0+(compatible; MSIE 6.0; Windows 5.1.2600.0; 
+MS .NET Remoting; MS .NET CLR 1.1.4322.573 )
+Content-Type: text/xml; charset="utf-8"
+SOAPAction: "http://schemas.microsoft.com/clr/nsassem/Lrc_Comm.DeviceMonit
+or/Lrc_Comm#InitServer"
+Content-Length: 599
+Expect: 100-continue
+Connection: Keep-Alive
+Host: linuxsrc:5052
+
+HTTP/1.0 100 Continue
+Server: Mono Remoting, Mono CLR 1.1.4322.573
+
+<SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
+xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-
+ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-
+ENV="http://schemas.xmlsoap.org/soap/envelope/" 
+xmlns:clr="http://schemas.microsoft.com/soap/encoding/clr/1.0" SOAP-
+ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
+<SOAP-ENV:Body>
+<i2:InitServer id="ref-1" 
+xmlns:i2="http://schemas.microsoft.com/clr/nsassem/Lrc_Comm.DeviceMonitor/
+Lrc_Comm">
+<sTerminalId id="ref-3">test</sTerminalId>
+</i2:InitServer>
+</SOAP-ENV:Body>
+</SOAP-ENV:Envelope>
+HTTP/1.0 400 Bad Request
+Content-Type: text/xml; charset="utf-8"
+Server: Mono Remoting, Mono CLR 1.1.4322.573
+Content-Length: 2016
+
+<SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
+xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-
+ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-
+ENV="http://schemas.xmlsoap.org/soap/envelope/" 
+xmlns:clr="http://schemas.microsoft.com/soap/encoding/clr/1.0" SOAP-
+ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
+  <SOAP-ENV:Body>
+    <SOAP-ENV:Fault id="ref-1">
+      <faultcode id="ref-3">Server</faultcode>
+      <detail href="#ref-4" />
+      <faultstring id="ref-5"> **** 
+System.Runtime.Remoting.RemotingException - No receiver for 
+uri /DeviceMonitor</faultstring>
+    </SOAP-ENV:Fault>
+    <a1:ServerFault id="ref-4" 
+xmlns:a1="http://schemas.microsoft.com/clr/ns/System.Runtime.Serialization
+.Formatters">
+      <message xsi:null="1"></message>
+      <exceptionType xsi:null="1"></exceptionType>
+      <exception href="#ref-6" />
+      <stackTrace xsi:null="1"></stackTrace>
+    </a1:ServerFault>
+    <a3:RemotingException id="ref-6" 
+xmlns:a3="http://schemas.microsoft.com/clr/ns/System.Runtime.Remoting">
+      <Message id="ref-7">No receiver for uri /DeviceMonitor</Message>
+      <StackTraceString id="ref-8">in &lt;0x00165&gt; 
+System.Runtime.Remoting.Channels.SoapServerFormatterSink:ProcessMessage 
+(System.Runtime.Remoting.Channels.IServerChannelSinkStack,System.Runtime.R
+emoting.Messaging.IMessage,System.Runtime.Remoting.Channels.ITransportHead
+ers,System.IO.Stream,System.Runtime.Remoting.Messaging.IMessage&amp;,Syste
+m.Runtime.Remoting.Channels.ITransportHeaders&amp;,System.IO.Stream&amp;)
+</StackTraceString>
+      <RemoteStackTrace id="ref-9"></RemoteStackTrace>
+      <Source xsi:type="SOAP-ENC:anyType" xsi:null="1" />
+      <ClassName xsi:type="SOAP-ENC:anyType" xsi:null="1" />
+      <RemoteStackIndex>0</RemoteStackIndex>
+      <HResult>0</HResult>
+      <HelpURL xsi:type="SOAP-ENC:anyType" xsi:null="1" />
+      <InnerException xsi:type="SOAP-ENC:anyType" xsi:null="1" />
+    </a3:RemotingException>
+  </SOAP-ENV:Body>
+</SOAP-ENV:Envelope>