Hang on though - I saw a commons jira issue from 08 that claimed the
javadoc for this class was misleading and there was no default cleaner
set - that issue was resolved, but the javadoc *still* seemed to
indicate there was a default cleaner in use ... so I wondered if the
code had changed, or the javadoc was still misleading ...
Looking at getFileCleaningTracker(), it also says:
An instance of FileCleaningTracker, defaults to FileCleaner.getInstance().
But then looking at the code, I don't see how that is possible. It
really appears to default to null (no cleaner).
So I ran a quick test, printing out the cleaning tracker, and it prints
'null'.
So, perhaps we try setting one and see where your problem is? It really
appears the javadoc I'm seeing does not match the code.
- Mark
On 6/9/10 8:01 AM, [email protected] wrote:
Ok, that theory bites the dust then...
I'll have to work on some diagnostics then to see why the content doesn't get
added.
Karl
-----Original Message-----
From: ext Mark Miller [mailto:[email protected]]
Sent: Wednesday, June 09, 2010 10:39 AM
To: [email protected]
Subject: Re: Solr spewage and dropped documents, while indexing
On 6/9/10 6:01 AM, [email protected] wrote:
but if I correctly recall how DiskFileItemFactory works, it creates
files and registers them to be cleaned up on JVM exit. If that's the
only cleanup, that's not going to cut it for a real-world system.
Class DiskFileItemFactory
"Temporary files are automatically deleted as soon as they are no longer
needed. (More precisely, when the corresponding instance of File is
garbage collected.) Cleaning up those files is done by an instance of
FileCleaningTracker, and an associated thread."
--
- Mark
http://www.lucidimagination.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
