With the new functionality of JSRs 78 and 76, it is now possible to export an object using a fixed endpoint (fixed port, etc) and a fixed ObjID, unexport the object, and then reexport an object (the same one or a different one) with the same endpoint and ObjID. If DGC has been enabled for both exports, the stub from the first export will participate in DGC for the object used in the second export. However, there is a timing issue. When the client receives the second stub, it may well think it still has a valid lease for the first stub (since it doesn't know the first object was unexported), and so (the way AbstractDgcClient is currently implemented) a new dirty call is not immediately made. Unfortunately, that means the second remote object might get DGC'd before the old lease expires.