OK looks like it does not read the old fuseki_base directive (plus content) and I had to re-create a new folder structure to get it to start. This way I have to upload a complete new data set now. In the past I was able to recycle the folder with each new fuseki release.
On Sat, Oct 11, 2025 at 11:37 AM Andy Seaborne <[email protected]> wrote: > Marco, > > Which packaging of fuseki are you running? > Was there a stacktrace? > > Andy > > On 10/10/2025 23:07, Marco Neumann wrote: > > builds fine but the servlet container in the fuseki package reports on > > startup > > > > HTTP ERROR 500 jakarta.servlet.ServletException: > > java.lang.IllegalStateException: No SessionManager > > > > Is there a new configuration step here for the fuseki server? > > No. > > > > > Marco > > > > On Fri, Oct 10, 2025 at 3:13 PM Andy Seaborne <[email protected]> wrote: > > > >> > >> Hi, > >> > >> Here is a vote on the first release candidate for > >> Apache Jena version 5.6.0. > >> > >> ==== Release Vote > >> > >> This vote will be open until at least > >> > >> Tuesday, 14th October 2025 at 08:00 UTC > >> > >> Please vote to approve this release: > >> > >> [ ] +1 Approve the release > >> [ ] 0 Don't care > >> [ ] -1 Don't release, because ... > >> > >> Everyone, not just committers, is invited to test and vote. > >> Please download and test the proposed release. See the checklist below. > >> > >> Staging repository: > >> > https://repository.apache.org/content/repositories/orgapachejena-1070 > >> > >> Proposed dist/ area: > >> https://dist.apache.org/repos/dist/dev/jena/ > >> > >> Keys: > >> https://svn.apache.org/repos/asf/jena/dist/KEYS > >> > >> Git commit (browser URL): > >> https://github.com/apache/jena/commit/99267df180 > >> > >> Git Commit Hash: > >> 99267df18097141bd2ac27e2b14edc96226f0895 > >> > >> Git Commit Tag: > >> jena-5.6.0 > >> > >> If you expect to check the release but the time limit does not work > >> for you, please email to let us know within the schedule above. > >> > >> ==== In this release > >> > >> + Preparation for Jena 6.0.0; mostly using deprecations > >> to indicate plans for removal. > >> + Use async HTTP; abortable remote query requests > >> + Update to Titanium json-ld v1.7.0 > >> + Jena testing switches to Junit6 (most sub-modules) > >> > >> Issues in this release: > >> > >> https://s.apache.org/jena-5.6.0-issues > >> > >> == Preparation for Jena 6.0.0 > >> > >> In preparation for a future Jena 6.0.0, the 5.6.0 release has code > >> deprecations indicating methods, classes and modules that are planned > >> for removal. > >> > >> * Minimum java version: Java 21 > >> * Lucene update to 10.* (this requires Java21+) > >> * Code deprecations planned for removal at Jena 6.0.0 > >> * Switch to jena-iri3986 as the IRI parser; retire jena-iri > >> * Retire jena-permissions > >> * Retire the Fuseki WAR file, jena-fuseki-webapp, jena-fuseki-war > >> * More deprecation of TDB1 but not for removal at Jena 6.0.0. > >> * Remove Graph Capabilities and Graph.dependsOn > >> * No RDF/XML in jena-core/main > >> * Remove ARQ initial bindings > >> * Prepare for switching to org.apache.jena.ontapi (artifact jena-ontapi) > >> from the original org.apache.jena.ontology (part of jena-core) > >> > >> ==== Contributions > >> > >> == Contributions to Jena 5.6.0: > >> > >> @shawnsmith: > >> * Fix for resolved URIs in jena-iri3986 > >> https://github.com/apache/jena/issues/3465 > >> > >> Aklakan: > >> > >> * GH-3464: ASync HTTP > >> https://github.com/apache/jena/pull/3464 > >> Switch Jena's HTTP request processing (HttpLib) to using > >> HttpClient.async. > >> * GH-3437: Initialize fields of Cmds.java before JenaSystem.init() > >> * Allow transform from NodeValue to Var. > >> * GH-2048: Remove left-over dependencies to expiring-map and rdf-tables. > >> * Use kryo-shaded instead of kryo in order to avoid conflicts with asm. > >> * Support CONSTRUCT_JSON query type in RDFLinkHTTP. > >> * Allow Node_Ext to be wrapped as NodeValueNode without further checks. > >> * Revert fontawesome > >> > >> sszuev > >> * GH-3322: [jena-ontapi] add assemblers > >> > >> @arne-bdt > >> * GH-3323 COALESCE checks variable bindings > >> > >> ------------------- > >> > >> Checking: > >> > >> + are the GPG signatures fine? > >> + are the checksums correct? > >> + is there a source archive? > >> + can the source archive be built? > >> (NB This requires a "mvn install" first time) > >> + is there a correct LICENSE and NOTICE file in each artifact > >> (both source and binary artifacts)? > >> + does the NOTICE file contain all necessary attributions? > >> + have any licenses of dependencies changed due to upgrades? > >> if so have LICENSE and NOTICE been upgraded appropriately? > >> + does the tag/commit in the SCM contain reproducible sources? > >> > >> > > > > -- --- Marco Neumann
