[Mono-bugs] [Bug 342211] New: Several remoting issues
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Fri Nov 16 10:15:37 EST 2007
https://bugzilla.novell.com/show_bug.cgi?id=342211#c323447
Summary: Several remoting issues
Product: Mono: Runtime
Version: 1.2.5
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: P5 - None
Component: remoting
AssignedTo: lluis at novell.com
ReportedBy: oldpasch at gmail.com
QAContact: mono-bugs at ximian.com
Found By: Other
Created an attachment (id=183707)
--> (https://bugzilla.novell.com/attachment.cgi?id=183707)
c-sharp solution
This week i wrote a little test example to check mono's remoting capabilities.
I found some strange behaviours which i'm not able to explain, so i just post
my findings here - including a small c-sharp solution.
I used a mono 1.2.5 installation with fresh mono-charge package from 15th of
november 07.
The test example constists of a server and a client. The server provides a
simple service function GetString() and an event. When a client subscribes to
the event, the server begins raising events via remoting.
Despite the fact that there obviously are errors when remoting between linux
and windows it also shows that there seem to be differences in the ppc
implementation of remoting which lead to different error patterns.
Test 1: works
------------------------------------------------------------------
- server compiled against mono, runs on linux-x86
- client compile against mono, runs on linux-x86
Test 2: does not work -> TypeLoadException at Activator.GetObject() (Error in
this test case 2 may be relatet to #323447)
------------------------------------------------------------------
- server compiled against mono, runs on linux-x86
- client compiled against mono, runs on windows
Test 3: works
------------------------------------------------------------------
- server compiled against mono, runs on windows
- client compiled against mono, runs on windows
Test 4: works
------------------------------------------------------------------
- server compiled against mono, runs on windows
- client compiled against mono, runs on linux-x86
Things get even whorser when mono runs on ppc:
Test 5: does not work Activator.GetObject() returns null
------------------------------------------------------------------
- server compiled againgst mono, runs on linux-x86
- client compiled against mono, runs on linux-ppc
Test 6: does not work Activator.GetObject() returns null
------------------------------------------------------------------
- server compiled againgst mono, runs on windows
- client compiled against mono, runs on linux-ppc
Test 7: does not work, see detailed error description
------------------------------------------------------------------
- server compiled against mono, runs on linux-ppc
- client compiled against mono, runs on linux-x86
This test case is somewhat different to all: The connection is established. The
simple Remoting function GetString() works, i.e. the client gets a string from
the server.
Remoting in the other direction does NOT work, i.e. when the server raises an
event, it catches a RemotingException ("Network is unreachable") and as a
consequence the handler is not called in the client. Don't know whats going
wrong there. Maybe this is a configuration problem??
Test 8: does not work -> TypeLoadException at Activator.GetObject() (Error in
this test case may be relatet to #323447)
------------------------------------------------------------------
- server compiled against mono, runs on linux-ppc
- client compiled against mono, runs on windows
Hope someone can check whats going wrong there!
Regards,
jOe
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the mono-bugs
mailing list