Hi everyone,

before filing a bug, I want to make sure I am not doing something wrong. I 
am running in the following problem.

Until I call  StoreConnection.release(location) the TDB code holds a lock 
on the file system of the index. I think this is the journal file mostly 
because I can separately close a dataset.

However, when I call this and then later try to "reconnect", e.g. by 
calling StoreConnection.make(location) or just creating a dataset, it 
seems that the persisted data is not accessible anymore. I.e. it seems 
that StoreConnection.release is doing more than just releasing the 
location. It seems to persist something that makes the data go away.

Note that I am seeing this independent on whether I use transactions or 
not (I have 2 versions around to compare the transactional and 
non-transactional behavior)

This is troublesome. I need some way to "disconnect" from a TDB store (so 
all file handles are released), but such that I can reconnect at a later 
time. Am I doing something wrong? Or is this a bug?

thanks

Simon

PS: if it is a bug, it would be a showstopper for our 2.7.1 adoption

Reply via email to