[Mono-bugs] [Bug 544357] New: Sponsoring an object in another appdomain does not appear to work

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Oct 5 11:10:27 EDT 2009


http://bugzilla.novell.com/show_bug.cgi?id=544357


           Summary: Sponsoring an object in another appdomain does not
                    appear to work
    Classification: Mono
           Product: Mono: Runtime
           Version: 2.4.x
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: remoting
        AssignedTo: lluis at novell.com
        ReportedBy: brett at fogcreek.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


Created an attachment (id=321066)
 --> (http://bugzilla.novell.com/attachment.cgi?id=321066)
A small XSP test site that does remote object sponsorship

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.3)
Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)

I set up a sponsor in the root AppDomain to sponson an object in a second
AppDomain, but the object gets collected after the default lease time anyway,
and I get "No receiver for uri
8d23430c_2a2e_445b_96d9_10e7b6df3697/2893f493_3.rem". 

Reproducible: Always

Steps to Reproduce:
1. Run the attached XSP website under mod_mono
2. Hit (site)/default.aspx

Actual Results:  
500

No receiver for uri 8d23430c_2a2e_445b_96d9_10e7b6df3697/2893f493_3.rem

Description: HTTP 500. Error processing request.

Stack Trace:

System.Runtime.Remoting.RemotingException: No receiver for uri
8d23430c_2a2e_445b_96d9_10e7b6df3697/2893f493_3.rem

Server stack trace: 


Exception rethrown at [0]: 

  at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke
(System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, System.Exception&
exc, System.Object[]& out_args) [0x00000] 

Version information: Mono Version: 2.0.50727.1433; ASP.NET Version:
2.0.50727.1433

Expected Results:  
As in .Net 2 under IIS:
10/5/2009 10:59:07 AM: I shall now create an appdomain, instantiate an object
therein, sponsor that object with an object in this appdomain, call a method on
it twice in quick succession, wait 2 seconds, and call that method again. We
expect all three calls to the remote object to work just fine, because the
remote object is sponsored.
10/5/2009 10:59:07 AM: 2
10/5/2009 10:59:07 AM: 2
10/5/2009 10:59:09 AM: 2
10/5/2009 10:59:09 AM: Cool.

We use plugins in our web application, and run them in a less-privileged
AppDomain. However, we want to manage collection of these objects ourselves,
and therefore want to sponsor them from the root AppDomain, rather than leave
objects hanging around after every page serve.

-- 
Configure bugmail: http://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