Re: Debugging corrupted TDB?

2019-07-05 Thread Andy Seaborne
Matt, I see in your original message: >> com.hp.hpl.jena.tdb That is quite an old version of TDB (which is by the way?) And it may be sufficiently old if t did not check if two copies ran at once - nowadays it checks. Andy On 05/07/2019 19:36, Matthew Holt wrote: Apologies for the lack

Re: Debugging corrupted TDB?

2019-07-05 Thread Matthew Holt
Apologies for the lack of detail there. The TDB had been rebuilt, but when trying to use it the above error was thrown, and from what I understand it means it is corrupted. Was wondering if there are any strategies for determining what is corrupted? Such as loading it in memory or turning on a

Re: Debugging corrupted TDB?

2019-07-04 Thread Rob Vesse
What do you mean by a re-index? i.e. what were the sequence of operations that preceded this error Rob On 03/07/2019, 20:40, "Matthew Holt" wrote: Hi all, Upon trying to access a TDB instance that was just re-indexed, we are getting the following error:

Debugging corrupted TDB?

2019-07-03 Thread Matthew Holt
Hi all, Upon trying to access a TDB instance that was just re-indexed, we are getting the following error: com.google.common.util.concurrent.UncheckedExecutionException: com.hp.hpl.jena.tdb.base.file.FileException: