[omniORB] [Q] how to perge dead services from Naming service

V S P toreason at fastmail.fm
Tue Apr 21 14:27:09 BST 2009


Just as a follow up to my question

if there is no way to achieve what I am looking for,
does anybody have
an example of a program that 
'pings' all the entries in the naming service
and then asks them to be destroyed if they are not
valid

May be this is a more standard way... but I am stuck now.

Thank you in advance,
Vlad



On Tue, 21 Apr 2009 00:48 -0400, "V S P" <toreason at fastmail.fm> wrote:
> Hi,
> I am working on a simple
> 'load balancing' for my client side.
> 
> I have servant object's named 'OTRQ'
> when they register with the naming service they register
> as OTRQ__hostnm__ProcessId
> 
> Then the client asks the naming service for a list of registered
> servants (hopefully the naming convention above makes them unique -- I
> could not come up with anything 'brigher' that this)
> And then it randomly selects one -- and works with that.
> 
> The problem is, when traversing the list of servants I see dead
> servants (that is those processes are not running)
> -- I do not want them.  When I restart the servants, of course,
> the chance that they will bind to a 'dead' name is slim (but I still
> support it by calling rebind).
> 
> Is there something I can configure in the naming service to
> 'automagically remove' dead servants as soon as possible? 
> or is there a more standard load-balancing scheme?
> 
> omni 4.1.3
> 
> thank you,
> Vlad
> -- 
>   V S P
>   toreason at fastmail.fm
> 
> -- 
> http://www.fastmail.fm - Faster than the air-speed velocity of an
>                           unladen european swallow
> 
> 
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list
-- 
  V S P
  toreason at fastmail.fm

-- 
http://www.fastmail.fm - The way an email service should be




More information about the omniORB-list mailing list