This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Folks - Does anybody have any input on how to handle a client that has crashed? I am using the Unreferenced interface to detect when a client is done with a remote object, but Unreferenced doens't help me much if a client does not finish with a remote object gracefully. If a client crashes I have to wait for the lease time to expire before Unreferenced.unreferenced() gets called on my object. I don't want to lower the lease time because to make it useful for cleaning up after a crashed client would require me to lower it to the point that my client VMs would be renewing leases far too frequently. Should I even be worrying about crashed clients? -BJ Grau
BJ, Depends on how robust you want to make you system. Remember that the specs say nothing about having to deal with a client crash. I stuck to the specs, and just documented that I did not implement anything for the client crashing, because of the small amount of time that there would be for a client to crash while actually having a record locked will be less than a second, so I felt at this stage of the program client crashes did not need to be taken into account. [ May 24, 2002: Message edited by: Bryan Clauser ]