[omniORB] Synchronization between omniNames service & Services

[R. P. Janaka]

No.. still did not get a solution.

As I found with new experiments, this problem is not a specific for this
Master/Slave case. If we just consider only about the Master, Problem still
remains. I found these result with debugging.

I just repeat the same procedure with only a single server.


   - Start the server and get registered with the name service
   - Manually kill the server
   - Start the server and get registered with the name service *again *.


Then the registration also get success. But when the client try to call
server's functions, it gives this exception.

the exception is *"SystemException: TRANSIENT_ConnectFailed"*

The reason for this problem may be the sudden break down of the server with
out informing it to the name service.

Do we have any solution for this....?


On Mon, Aug 4, 2008 at 6:55 PM, Martin Okeke <mokeke at free.fr> wrote:

>  Hi Janaka
>
> Have you found any solution to the problem you mentionned herebelow. Is it
> possible for the Master and Slave to mutually test for their respective
> status with the name server once they are up and running. They can then
> deregister/reregister wth the name server after the slave must have been
> killed. I assume this could be done through a messaging system.
>
> Cheers
>
> M. Okeke
>
> R. P. Janaka wrote:
>
> Hi all,
>
> I am writing a simple Fault tolerant server which can handle client request
> without any service interruption..Using C++ & omniORB
>
> In my system there are two servers as Master & Slave..
>
> When they starts they get registered with the name service as usual.
> Normally the first one will be the Master and the next one is the slave.
>
> All are working properly..But still have a simple problem which I was
> unable to solve. It is as follows.
>
>
>    - When both Master & Slave are running....
>    - Manually kill the Slave
>    - Start the Slave again.
>
> In some situation this Slave restart does not work properly.. it gives an
> exception. This exception is my own exception and It says that Slave already
> exist.
> This happens only randomly, but occurring frequency is pretty high. (at
> least 30% of the time it will happen)
>
> If I retry several times I could get success. Because If I call start
> method within the catch block I can really reduce the occurring frequency of
> this exception.
>
>
> So I guess the problem is with the name service. Because when I just kill
> the Slave, the name service does not know anything about this killing. So it
> is still keep registering details of the Slave. Because of that it gives and
> exception when I am going to register the Slave again.
>
> Please can anyone guess any other reason for this problem.....?
>
> If my guess is correct...Please can anyone help me to solve this problem..
> Is there a continues synchronization between the name service and the
> service itself .....?
>
>
> --
> Regards,
> R. P. Janaka
>
> ------------------------------
>
> _______________________________________________
> omniORB-list mailing listomniORB-list at omniorb-support.comhttp://www.omniorb-support.com/mailman/listinfo/omniorb-list
>
>
>


-- 
Regards,
R. P. Janaka
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20080805/10215c51/attachment.htm