[Mono-bugs] [Bug 75886][Cri] New - Remoting Configuration Win32-Client Mono-server

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Aug 23 13:50:11 EDT 2005

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 yngve.zackrisson at mobila-kontoret.se.


--- shadow/75886	2005-08-23 13:50:11.000000000 -0400
+++ shadow/75886.tmp.31943	2005-08-23 13:50:11.000000000 -0400
@@ -0,0 +1,117 @@
+Bug#: 75886
+Product: Mono: Runtime
+Version: 1.1
+OS Details: Fedora Core 3
+Status: NEW   
+Severity: Unknown
+Priority: Critical
+Component: remoting
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: yngve.zackrisson at mobila-kontoret.se               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Remoting Configuration Win32-Client Mono-server 
+Please fill in this template when reporting a bug, unless you know what you
+are doing. 
+Description of Problem:
+I am developing a console applcation that hosts remote objects 
+and I want to call the functions of these remote objects. 
+(I gona change the console hosting to windows service hosting later on).
+The host application will be run on Linux under Mono and 
+the client application will run on Win32 under Microsoft.NET.
+(In order to try to increase the security in the final remoting solution 
+I will attempt to customize the channel).
+The host application is compiled using mcs on Linux (Fedora 3). 
+The Mono versio is Mono ver.mono-core-
+The host application uses RemotingConfiguration.Configure(configFilePath) 
+to configure the remoting.
+The configuration file which is referred to in configFilePath
+(appname.exe.config) is attached. 
+When starting up my hosting application in Linux (Fedora 3)  with : 
+$ mono --debug --trace=none appname.exe
+I got the following exceptions (the rest of the text 
+is written text to the console) during the remoting configuration : 
+PostServer - Main - Started: 8/23/2005 3:27:36 PM GMT
+Configuring remoting for specified objects...
+Configuring with : appname.exe.config
+EXCEPTION handling: FormatException
+EXCEPTION handling: FormatException
+EXCEPTION handling: FormatException
+EXCEPTION handling: FormatException
+ApplicationName :
+Hit <enter> key to exit
+The ApplicationName is fetched from RemotingConfiguration.ApplicationName 
+and is for some reason empty.
+When calling the remote object from the client through http channel I got a :
+     400 : Bad request
+message on the client side.
+When starting upp the same appname.exe in Windows 
+(complied in windows with Microsoft.NET 1.1)  
+I got the ApplicationName properly written out 
+and I did not get any complaints about "Bad request" 
+and the remoting worked.
+Steps to reproduce the problem: 
+1. Create the applications (Win32 client and Linux host) 
+   and a similar configuration file for the remoting.
+   (I guess you have some sample application you can twist 
+    to fit the setup in the attached configuration file).
+2. Run the application in Win32 (Client) and Linux (Console Host).
+3. Check the results. 
+   (The content in RemotingConfiguration.ApplicationName and 
+    the response to the client).
+Actual Results:
+Nothing in RemotingConfiguration.ApplicationName 
+and a '400 : Bad request' response to the client.
+Expected Results:
+The application name in RemotingConfiguration.ApplicationName 
+and no '400 : Bad request' response to the client.
+An working remoting invokation of the remote objects functions
+(at least those only containing primitive types in the parameters 
+and the response).
+How often does this happen? 
+Additional Information:
+I made a note when I traced the mono (Linux) appname.exe 
+more in detail.
+I noticed that Mono.Xml.SmallXmlParser was used quite heavily 
+in the application.
+Could that class be the source of the exception : 
+   EXCEPTION handling: FormatException

More information about the mono-bugs mailing list