[Ace-users] Re: [tao-users] Event Service and Consumers/Suppliers with persistentIORs

[Markus Debusmann]

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 2.6.16.46-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:
    COMPILATION?
        No.
    LINKING?
        No.
    EXECUTION?
        Yes.

SYNOPSIS:
Event Service and Consumers/Suppliers with persistent IORs

DESCRIPTION:
see below

SAMPLE FIX/WORKAROUND:
see below

Johnny Willemsen wrote:
> Hi,
>
> Please use the PRF form, we now don't know which TAO version you are using
> which can influence the answer.
>
> Regards,
>
> 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 
>> combination 
>> 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
>> Markus
>>
>> _______________________________________________
>> tao-users mailing list
>> tao-users at mail.cse.wustl.edu
>> http://mail.cse.wustl.edu/mailman/listinfo/tao-users
>>
>>     
>
>
>
>