Hi Andy,
unfortunately (in terms of reproducing the error, not in terms of my project),
starting with a fresh database seems to have solved the problem. It is well
possible that the previous database was corrupted due to an abort transaction,
and that this only happened once - I assumed that d
Hi Andreas,
Do you have a reproducible test case even if it happens only occasionally?
Having looked at the code, I can't see a risk point and certainly not
like earlier problems with TDB1.
Have you had any abort transactions - these happen in the Fuseki UI only
if you browse away from a fil
