Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Unreferenced

 
BJ Grau
Ranch Hand
Posts: 234
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
Bryan Clauser
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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 ]
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, you don't need to worry about it. I only used Unreferenced, and had it wait for the entire lease time, that is absolutely fine.
Mark
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic