Bug 1986

Summary: AMH and collocation..
Product: TAO Reporter: Nanbor Wang <bala>
Component: AMHAssignee: DOC Center Support List (internal) <tao-support>
Status: ASSIGNED ---    
Severity: normal    
Priority: P3    
Version: 1.5.4   
Hardware: All   
OS: All   
Bug Depends on: 1369    
Bug Blocks: 2319, 2454    

Description Nanbor Wang 2004-11-21 10:05:49 CST
Here is a valid report from Malcolm. 

-----------------------------------------------------------------------------------
TAO VERSION: 1.4.1
ACE VERSION: 5.4.1

HOST MACHINE and OPERATING SYSTEM:
Pentium 4, Debian linux

TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
COMPILER NAME AND VERSION (AND PATCHLEVEL): g++ (GCC) 3.3.4 (Debian
1:3.3.4-13)

AREA/CLASS/EXAMPLE AFFECTED:
AMH

DOES THE PROBLEM AFFECT:
COMPILATION? no
LINKING? no
EXECUTION? yes
OTHER (please specify)?

SYNOPSIS:
When calling an AMH servant from a proxy within the same process, the
proper servant method is called, but the data passed into the
parameters is bad.

DESCRIPTION:
It appears that the TAO option to perform direct function calls for
colocated objects isn't compatible with AMH servants. The same call
works ok with -ORBCollocation no. We'd still like to be able to use this
feature with non-AMH servants. Can we mix these 2 safely? Are we
going to have the same problem with AMI?

REPEAT BY:
Make any call on an AMH object from within the same process.

SAMPLE FIX/WORKAROUND:
Run with -ORBCollocation no .

--
+-----+
|SPEED| "It's not just a good idea, it's the law"
| | - Albert Einstein (paraphrased)
| c |
| |
|LIMIT|
+-----+
Comment 1 Nanbor Wang 2004-11-21 10:06:34 CST
When Ossama works on AMH in skeleton refactoring this needs to be taken care off. 
Comment 2 Ossama Othman 2004-11-23 22:36:17 CST
Mine.
Comment 3 Johnny Willemsen 2005-05-25 06:56:15 CDT
Ossama, is this addressed with the skeleton refactoring?
Comment 4 Johnny Willemsen 2006-02-03 08:39:39 CST
added blocks
Comment 5 Charles Frasch 2006-04-13 13:00:23 CDT
We're having the same problem with AMI (on vers 1.4.2). A colocated AMI call
that assigns a value to an out parameter causes a segmentation fault.
Comment 6 Johnny Willemsen 2006-08-09 08:20:28 CDT
accept, still valid with 1.5.2
Comment 7 Johnny Willemsen 2006-08-13 13:23:55 CDT
changed component to AMH
Comment 8 Johnny Willemsen 2007-01-15 01:06:34 CST
updated version