Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of esteban.franqueiro@bea.com
 designates 66.248.222.89 as permitted sender)
Message-ID: <040b01c81b33$0270ad40$7309240a@goku>
From: "Esteban Franqueiro" <esteban.franqueiro@bea.com>
To: <dev@jackrabbit.apache.org>
References: <A047748A00BCDC4794D0D3FB35009F84D99703@repbex02.amer.bea.com>
 <04b201c810fd$06c4f300$7309240a@goku>
 <5f211bd50710190706y3444aaf2l6a302f2001e4be6b@mail.gmail.com>
Subject: Realtime datastore garbage collector
Date: Tue, 30 Oct 2007 17:25:26 -0300
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

Hi Thomas.
Regarding this:

>> who has the hard reference to the data identifier
>
> The chain is:
> PropertyImpl -> InternalValue -> BLOBInDataStore -> DataIdentifier

Who holds on to the PropertyImpl? Is this reference removed before or after the save?
Im asking because while testing the code I came up with the following scenario:

   JR                      |  GC
------------------------|---------------------
add properties    |
                              | set cut-point as part of the next scan / mark cycle
                              | (won't mark recently added properties, because they're unsaved)
  save                    |
(evict)                   |
                              | deleteUnused()

(evict): identifiers evicted from the weak hash map

Is it possible that the identifiers get removed from the weak hash map immediatly after the save 
operation? Or the identifiers can't be removed because a hard reference to them (ie, to the 
PropertyImpl object) is kept somewhere in the Jackrabbit core? When is this reference removed?
In testing, this is possible to do by calling the clearInUse() method you provided. But what about a 
real scenario?
I hope you can understand me. If not, I'll try to explain better.
Regards,

Esteban Franqueiro
esteban.franqueiro@bea.com 


Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.