AtesComp commented on issue #1583:
URL: https://github.com/apache/jena/issues/1583#issuecomment-1289483003
Apparently so.
I did some additional work and it looked like the `ja:schema` may have been
partially suspect. I went back to 4.6.1 and adjusted the config to remove the
`ja:UnionModel` and use a `tdb2:unionDefaultGraph` instead like so:
```
...
fuseki:endpoint [ fuseki:name "sparql" ; fuseki:operation fuseki:query ;
## Set default-union-graph for this endpoint.
ja:context [ ja:cxtName "tdb2:unionDefaultGraph" ; ja:cxtValue true
] ; ] ;
...
:graphInfMyData ja:InfModel ;
rdfs:label "MyData Inference Model" ;
ja:baseModel :graphDefault ;
ja:reasoner :reasonerMyData ;
.
...
<<< Remove :modelUnionMyData <<<
...
:graphDefault a tdb2:GraphTDB2 ;
rdfs:label "Default Graph" ;
tdb2:graphName "urn:x-arq:UnionGraph" ;
tdb2:dataset :ds_tdb2_MyData;
.
```
This left the Reasoner intact:
```
:reasonerMyData a ja:Reasoner ;
ja:reasonerURL res:OWLMicroFBRuleReasoner ;
ja:schema :graphGNR_Ont ;
ja:schema :graphGNR_VCard ;
.
```
On startup, I got an error immediately after the Shiro load:
```
[2022-10-24 14:33:19.738] ERROR [main]
[org.apache.jena.fuseki.webapp.FusekiServerListener.serverInitialization(FusekiServerListener.java:106)]
- Exception in initialization: caught: Not in a transaction
[2022-10-24 14:33:19.738] WARN [main]
[org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:541)] -
Failed startup of context...
```
When I removed the `ja:schema` statements, it all worked well for 4.6.1:
```
...
:reasonerCOLT a ja:Reasoner ;
ja:reasonerURL res:OWLMicroFBRuleReasoner ;
# ja:schema :graphGNR_Ont ;
# ja:schema :graphGNR_VCard ;
.
...
```
As I was writing this up, I decided to test 4.7.0-SNAPSHOT as well.
1. Using 4.7.0-SNAPSHOT with the previous config and only moving the
`ja:schema` statements to `ja:subModel` statements in the `ja:UnionModel`
didn't help as much as I thought it might--I still got 500 errors after using
the UI Edit to view a few graphs.
2. Using 4.7.0-SNAPSHOT with the updated config (above) seems to work well.
I couldn't break it with my limited testing.
Also, I've tested this issue on multiple machines with different
environments, so it's not just due to one machine's peculiar settings.
**It seems a `ja:UnionModel` is the ultimate culprit.**
By using the config with the changes above, the resulting inference on the
union default graph adds more graphs than I want. I can live with it for now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
