You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jena.apache.org by "afs (via GitHub)" <gi...@apache.org> on 2025/07/16 09:14:04 UTC
[I] Warning for unset SIS_DATA from fuseki server. [jena]
afs opened a new issue, #3317:
URL: https://github.com/apache/jena/issues/3317
The message
```
WARN system :: The “SIS_DATA” environment variable is not set.
```
is logged when Fuseki server starts up.
Workaround:
Setting the environment variable to `.` makes it go away.
```
SIS_DATA="." fuseki-server
```
--
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: issues-unsubscribe@jena.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org
For additional commands, e-mail: issues-help@jena.apache.org
Re: [I] Warning for unset SIS_DATA from fuseki server. [jena]
Posted by "afs (via GitHub)" <gi...@apache.org>.
afs closed issue #3317: Warning for unset SIS_DATA from fuseki server.
URL: https://github.com/apache/jena/issues/3317
--
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: issues-unsubscribe@jena.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org
For additional commands, e-mail: issues-help@jena.apache.org
Re: [I] Warning for unset SIS_DATA from fuseki server. [jena]
Posted by "afs (via GitHub)" <gi...@apache.org>.
afs commented on issue #3317:
URL: https://github.com/apache/jena/issues/3317#issuecomment-3084291555
It seem to be hard to control because it is an environment variable.
Until a better idea comes along, controlling via log4j seems to be the way.
If setting to ERROR is itself a problem, it may be possible to start at level ERROR (log4j2.properties setting) and change to WARN during/after jena-fuseki-mod-geosparql.
--
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: issues-unsubscribe@jena.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org
For additional commands, e-mail: issues-help@jena.apache.org