Re: Reliability and deadlock in Annex E/distributed code

[Jerome Hugues <hugues@antigone.enst.fr>]

In article <pan.2006.09.10.20.55.57.113998@linuxchip.demon.co.uk.uk.uk>, Dr. Adrian Wrigley wrote:

> There are three partitions A, B, C
> The program starts up normally.
> A procedure (in a normal unit) in partition C calls a function (in a
> normal package) in partition B (using dynamic dispatch on a remote access
> to class-wide type). The function in partition B calls a function (in a
> rci package) in partition A The function in partition A never executes,
> and the program stops executing.

> It's as if there is some deadlock or shortage of tasks to allocate
> or something.
>
> Any ideas?

How many application tasks do you have on each node ? did you
configure a task pool for each node ? (just to check you do not run
out of task)
 
> I've tried building PolyORB from https://libre2.adacore.com/ but it
> seems to be missing the src/dsa directory needed to support Annex E.
> If I get the version from cvs, it gets the error "raised
> RTSFIND.RE_NOT_AVAILABLE : rtsfind.adb:497".  What's the best way to
> build the DSA personality?

Short answer: waiting for an AdaCore annoucement stating it is ready ;)

Long answer: DSA requires that GNAT, GLADE (gnatdist) and PolyORB
versions are consistent. So getting it from CVS expose you to
problems.
 
AFAICT, the error you see means expanded code references an entity
that does not exist. It is the symptom of a strong inconsistency
between the compiler and the PCS.

> If I used the DSA personality from PolyORB, will it be any different
> from the GARLIC PCS?  Might it be more/less robust? faster?

Lots of new configuration options, new protocols. 

-- 
Jerome