Github user afs commented on a diff in the pull request:
https://github.com/apache/jena/pull/361#discussion_r168597752
--- Diff: jena-tdb/src/main/java/org/apache/jena/tdb/solver/BindingTDB.java
---
@@ -120,6 +121,8 @@ public Node get1(Var var)
if ( id == null )
return null ;
n = nodeTable.getNodeForNodeId(id) ;
+ if ( n == null )
+ throw new TDBException("No node in NodeTable for NodeId
"+id);
--- End diff --
I don't know all the reasons for getting it. The use reports don't tend
to tell us when things are fixed so I don't for sure whether my suggestions
were of any help.
One possible case is early exit, non-transactional use of TDB so the triple
or quad table has written back (by natural OS managed file caching) but the
NodeTable has not. Exit without sync (not necessarily a crash) and they are
out of step.
Maybe with this we'll get better information and be able to refine it - at
the moment, coudl well be a false trail.
---
