[omniORB] CORBA 2.3 standard and fault tolerance

[Jani Niittukari]

Our design goal is to deploy two PC boxes running identical HW/SW system.
This redundant system has to be accessible via CORBA interface. I just wan't
to write logic for the one PC box and then use some replication mechanism
provided by ORB or service.

We need full 24/7 functionality with no downtime, i.e. no singe point of
failure. If something breaks/crashes another box keeps going. Seems that i'm
hoping too much, or am i?

Thanks,
 Jani

-----Original Message-----
From: owner-omniorb-list@uk.research.att.com
[mailto:owner-omniorb-list@uk.research.att.com]On Behalf Of Ilinykh,
Andre
Sent: 2. marraskuuta 2000 19:22
To: omniorb-list@uk.research.att.com
Subject: RE: [omniORB] CORBA 2.3 standard and fault tolerance


In our application we use a simple and effective pattern- watchdog. This is
very simple UNIX daemon waiting for another process. If any trouble happens
watchdog restarts that process. All persistant objects keep their data in
memory mapped files, so no data lost. Of course this solution doesn't
provide load-balancing.
Thank you,
  Andrey

"There is no standardized mechanism by which applications can convey their
reliability requirements to the ORB." Quotation from Book: Enterprise CORBA,
Dirk Slama, Prentice Hall.

With couple days of studying i have realized that there is 3 ways to
implement Fault tolerant CORBA system.

1. I wait for the CORBA 3 compliant ORBs (Mmm, can't wait)
2. I pick one of the "expensive" commercial ORBs (Visibroker, Orbix, ...)
3. I have to implement my own replication mechanism, which i don't want to
do.

If you know any more solutions, i would be pleased to see them.

Regards,

 Jani