From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6538aab6b5cbb022,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-08-26 07:44:11 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.freenet.de!194.168.222.61.MISMATCH!newspeer1-gui.server.ntli.net!ntli.net!newsfep4-winn.server.ntli.net.POSTED!53ab2750!not-for-mail From: "Dr. Adrian Wrigley" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Annex E, GLADE and fault-tolerance Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Inktomi-Trace: pc6-cmbg1-6-cust147.cmbg.cable.ntl.com 1061909050 27260 81.100.88.147 (26 Aug 2003 14:44:10 GMT) Message-ID: <%mK2b.4892$L15.72@newsfep4-winn.server.ntli.net> Date: Tue, 26 Aug 2003 15:44:09 +0100 NNTP-Posting-Host: 62.252.192.4 X-Complaints-To: abuse@ntlworld.com X-Trace: newsfep4-winn.server.ntli.net 1061909051 62.252.192.4 (Tue, 26 Aug 2003 15:44:11 BST) NNTP-Posting-Date: Tue, 26 Aug 2003 15:44:11 BST Organization: ntlworld News Service Xref: archiver1.google.com comp.lang.ada:41863 Date: 2003-08-26T15:44:09+01:00 List-Id: Hi all! OK. So I've got my client/server application working now, but have a problem with fault tolerance. (I am using Annex E/GNAT 3.15/GLADE/Linux) My objective is for clients to be able to run continuously for months at a time. I also want the server to run for months too. If a client terminates, I want to be able to restart it. If the server terminates, I want to be able to restart it too. So I use the "Reconnection" and "Termination" policy so that I can restart the client or the server as necessary. If the main boot server is separate from the client and application server partition, it works fine. Except when the main boot server is restarted :( When the main boot server is terminated and restarted, executing clients run into problems. The existing clients cannot communicate with the new main boot server invocation, nor with partitions started after the new main server is started. The effect is that if the main boot server dies, all the clients need to be restarted too. I have read the GLADE Users' Guide carefully, and can't see a solution to the problem - it seems to be a design feature(!) How can I prevent failure of the server causing failure of all the clients too? I just want the "simple" behaviour like web servers and clients, where you don't need to restart all the clients each time a server reboots. Thanks for any help on this! -- Dr Adrian Wrigley, Cambridge, England. Clients get the following exception, even after restarting the server: Exception name : SYSTEM.RPC.COMMUNICATION_ERROR Exception message : Partition 1 is unreachable Exception information : Exception name: SYSTEM.RPC.COMMUNICATION_ERROR