On 08/08/13 16:52, David Jordan wrote:
Andy, With regard to your statement "This is a well-documented issue
on MS Windows with memory mapped files (on Windows 64bit)". What are
all the things that this could affect if one is running TDB on
Windows 64bit? Is it only the deletion of underlying TDB files? Or
are there other issues as well? During development I have deleted the
files of a TDB database. But I did this when I had no software
running against the TDB database.
Just deleting the database on disk in a running system.
If there are no running instances, it's just files on disk. If they
can't be deleted then you may wish to talk sternly to your OS!
It is my understanding that my single JVM is the only running process
against the TDB database, that there is not a separate server
processing running, which may continue to run after I have terminated
my application process. Is that true? If one is not currently running
a JVM using TDB on a particular TDB store, there should not be a
problem with the deletion of the files, correct?
True. No hidden processes.
If your running TDB in an application, then the database engine is
embedded in the application JVM.
Andy
