[Ace-users] Re: [tao-users] Event Service and Consumers/Suppliers
Douglas C. Schmidt
schmidt at dre.vanderbilt.edu
Wed Aug 22 09:13:07 CDT 2007
Thanks for providing the PRF info. Please upgrade to ACE+TAO+CIAO
x.5.10 (i.e., ACE 5.5.10, TAO 1.5.10, and CIAO 0.5.10), which you can
under the heading: "Latest Beta Kit".
The DOC groups at Washington University, UC Irvine, and Vanderbilt
University only provide "best effort" support for non-sponsors for the
latest release, as described in
Thus, if you need more "predictable" help for earlier versions of
ACE+TAO, I recommend that you check out
for a list of companies that will provide you with ACE+TAO commercial
>sorry, here the missing information.
>TAO VERSION: 1.5
>ACE VERSION: 5.5
>HOST MACHINE and OPERATING SYSTEM:
>2 x Intel(R) Xeon(R) CPU 3.00GHz
>Linux 18.104.22.168-0.12-smp #1 SMP i386 GNU/Linux
>TARGET MACHINE and OPERATING SYSTEM, if different from HOST:
>COMPILER NAME AND VERSION (AND PATCHLEVEL):
>gcc version 3.4.3
>DOES THE PROBLEM AFFECT:
>Event Service and Consumers/Suppliers with persistent IORs
>Johnny Willemsen wrote:
>> Please use the PRF form, we now don't know which TAO version you are using
>> which can influence the answer.
>> Johnny Willemsen
>> Remedy IT
>> Postbus 101
>> 2650 AC Berkel en Rodenrijs
>> The Netherlands
>> www.theaceorb.nl / www.remedy.nl
>> *** Integrated compile and test statistics see
>> http://scoreboard.theaceorb.nl ***
>> *** Commercial service and support for ACE/TAO/CIAO ***
>> *** See http://www.theaceorb.nl/en/support.html ***
>>> I have a question concerning the use of the Event Service in
>>> with consumers/suppliers that use persistent IORs.
>>> My principal idea was to use consumers/supplier with
>>> persistent IORs in
>>> order to prevent a multiple registration of a
>>> consumer/supplier crashed.
>>> When restarted the reregistration results in a lot of exceptions when
>>> the Event Service is trying to sent out consumers which not
>>> valid anymore.
>>> Although the IORs of consumers/suppliers are persistent the Event
>>> Service handles them as a registration of a new
>>> consumers/suppliers. In
>>> case of consumers, this results in receiving all events twice. This
>>> proves to me that both IORs are still valid. But for some reason the
>>> Event Service does not throw an 'AlreadyRegistered' exception when
>>> reregistering after a crash.
>>> I worked around this using transient IORs and letting the
>>> Event Service
>>> monitor broken links. This does very much the same except that the ES
>>> needs one exception to notify that the llink is broken.
>>> I wonder why my approach using persistent IORs does not work. Has
>>> someone similar experience?
>>> Kind regards
>>> tao-users mailing list
>>> tao-users at mail.cse.wustl.edu
Dr. Douglas C. Schmidt Professor and Associate Chair
Electrical Engineering and Computer Science TEL: (615) 343-8197
Vanderbilt University WEB: www.dre.vanderbilt.edu/~schmidt
Nashville, TN 37203 NET: d.schmidt at vanderbilt.edu
More information about the Ace-users