I'm encountering every now and then TDBTransactionException's. These errors may be due to my code not respecting the transaction gotchas, but also to real bugs. These errors may be due to my code not respecting the transaction gotchas, but also to real bugs.
The context : I'm developing Swing applications (DataGUI<http://svn.code.sf.net/p/eulergui/code/trunk/eulergui/html/documentation.html#Data1> , DomainApplication<http://svn.code.sf.net/p/eulergui/code/trunk/eulergui/html/documentation.html#L7253> ) that accumulate documents from the web in a TDB store that is used as a cache. The writings occur in threads (Scala futures) associated to the URI downloaded, and to the named graph. Also, the user can add triples (in a special named graph) that are at once commited. So, there is plenty of room for errors, plus the application is sometimes killed. Here are examples of errors: [ERROR] - 2014-02-21 09:54:52,181 [ForkJoinPool-1-worker-1] TDB (JournalControl.java:replay:259) Exception during journal replay com.hp.hpl.jena.tdb.transaction.TDBTransactionException: Checksum error reading from the Journal. Exception after commit point : transaction commited but internal status not recorded properly com.hp.hpl.jena.tdb.transaction.TDBTransactionException: Checksum error reading from the Journal. I need some advice about debugging, like displaying dataset, graph, journal status, or adding assertions, or whatever is possible. I'm willing to contribute to make TDB more robust by providing repeatable situations. Another question is : how to repair a broken TDB ? Or maybe the question is : can a TDB be broken at all, or is it my bad application code that repeatedly creates similar problems? Kind regards -- Jean-Marc Vanel Déductions SARL - Consulting, services, training, Rule-based programming, Semantic Web http://deductions-software.com/ +33 (0)6 89 16 29 52 Twitter: @jmvanel , @jmvanel_fr ; chat: irc://irc.freenode.net#eulergui
