Bugzilla – Bug 1535
Potentially collocated IORs demarshaled as nil references
Last modified: 2005-04-04 17:39:50
You need to log in before you can comment on or make changes to this bug.
ThruPOA collocation does not require a servant, however, the collocation flags are disabled if the servant cannot be found when the object reference is created. This wastes opportunities for collocation, as object references created before the servant (say via string_to_object() or via create_reference_with_id()) will not be collocated though they could be.
Created an attachment (id=217) [details] Suggested patch
Created an attachment (id=218) [details] My proposed (untested) changes
Irfan's changes look better
Accepted. Here is the general description of the fix: As long as there is a profile match, we should create a collocated object. If we can find the servant, well and good. If not, it will be resolved later or an exception will be thrown by the POA. There is no point in creating a remote object after the profiles match since the remote invocation will be handled by the local ORB. DIRECT collocation users beware, you must have the servant available when the Object is created. Once we have a test, we can check in the patches.
Fixed. ChangeLogTag: Tue Jul 22 16:57:06 2003 Irfan Pyarali <irfan@oomworks.com>
The bug was reintroduced before 1.4.2. I will attach a proposed patch and a regression test shortly.
Created an attachment (id=291) [details] TAR file with the regrssion test....
Created an attachment (id=292) [details] Proposed fixes, the regression test passes, still running full testsuite
Changing the summary. Unlike previous incarnations of the bug this one nows returns a nil reference when the object is not demarshaled properly. Needless to say that is a more serious problem that just a performance issue.
Fixed using Carlos's patches. Thanks Carlos! Sun Nov 14 05:01:28 2004 Balachandran Natarajan <bala@dre.vanderbilt.edu>
The bug is showing up again on 1.4.3 This is the second or third time that I have to reopen this bug. I have sent a regression test already. What is the excuse for not using the regression test?
Doh! The fix (and regression test) is in the current CVS version. Apologies.