Hi,
I am currently testing out things internally with the just released 2.7.3
but I am running into some problems. One seems pretty low-level and is
worrysome. This is the exception:
Caused by: com.hp.hpl.jena.tdb.TDBException: Allocation attempt on
NodeTableReadonly
at
com.hp.hpl.jena.tdb.nodetable.NodeTableReadonly.getAllocateNodeId(
NodeTableReadonly.java:37)
at com.hp.hpl.jena.tdb.store.GraphNamedTDB.getGraphNodeId(
GraphNamedTDB.java:149)
at com.hp.hpl.jena.tdb.store.GraphNamedTDB.countThis(
GraphNamedTDB.java:124)
at com.hp.hpl.jena.tdb.store.GraphTDBBase.graphBaseSize(
GraphTDBBase.java:178)
at com.hp.hpl.jena.sparql.graph.GraphBase2.size(
GraphBase2.java:381)
at com.hp.hpl.jena.sparql.graph.GraphBase2.isEmpty(
GraphBase2.java:432)
at com.hp.hpl.jena.rdf.model.impl.ModelCom.isEmpty(
ModelCom.java:871)
at com.ibm.team.jfs.rdf.internal.jena.tdb.JenaTxTdbProvider$8.run(
JenaTxTdbProvider.java:991)
at com.ibm.team.jfs.rdf.internal.jena.tdb.JenaTxTdbProvider$8.run(
JenaTxTdbProvider.java:1)
at
com.ibm.team.jfs.rdf.internal.jena.tdb.JenaTxTdbProvider.storeOperation(
JenaTxTdbProvider.java:204)
... 56 more
Unfortunately, I can't seem to reliably reproduce it even though I am not
running any concurrent tests. Any idea who this kind of exception can
occur and what I can do to perhaps construct a test case?
none of this has been observed in 2.7.1 so it must be related to recent
changes
thanks
Simon
