Project

General

Profile

Bug #123

Detect deceased rmi clients and clean up

Added by ronald - over 14 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Mulgara
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
fixed

Description

If an rmi client goes away (exits, is killed, whatever) while holding
the write lock then mulgara will stay locked up forever. One of the
rmi wrapper classes needs to implement java.rmi.Unreferenced to get
notified when clients disappear and needs to abort that client's
transaction, if any.

See also http://java.sun.com/j2se/1.5.0/docs/guide/rmi/faq.html#leases2 .

Note that #121 will help here, but catching the unreferenced
notifications has the potential to clean things up much quicker
because in a typical production internal network environment the rmi
lease timeouts can be set much lower than the transaction timeout.

#1

Updated by ronald - over 14 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

(In r979) Detect when the session becomes unreferenced (e.g. because the client dropped
the session or the client died) and close the session.

This closes #123.

Also available in: Atom PDF