Small correction to stack trace from previous email, in case that matters:
Thread [qtp975404820-93] (Suspended (breakpoint at line 305 in
BlockMgrJournal))
owns: NodeTableNative (id=586)
owns: DatasetPrefixesTDB (id=587)
BlockMgrJournal.checkActive() line: 305
BlockMgrJournal.
Hi Andy,
with our current migration to Jena 4.1 we noticed this change
https://issues.apache.org/jira/browse/JENA-2006
is affecting the way that we use TDB (in the "shared TDB aka XDB") mode.
Previously, all named graphs were storing their own prefixes, yet now
there seems to be only one
Hi there,
I can't explain the Linux/Windows difference.
Fuseki was wrong (it could double decode because the servlet API does
decoding)
For Linux - looks like there is still a bug - it should work (I tried
using using curl and a Fuseki server in Jetty).
What does the Fuseki log file say? T
Hi Users,
I have been testing apache-jena-fuseki version 4.1.0. and
found one issue with the graph name.
Previously I was using apache-jena-fuseki 3.14.0 and upload ttl files using
python post request using graph names. As an example
http://localhost:3030/eva-dev/data?graph=htt