GraphDB FAQ

compared with
Current by Venelin Kotsev
on Oct 27, 2015 12:09.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History
# Rename the folder for this repository in the file system
#* mv /home/<user>/.aduna/openrdf-sesame/repositories/OLD_NAME /home/<user>/.aduna/openrdf-sesame/repositories/NEW_NAME (linux/unix)
#** unless repositories location has not been explicitly defined by parameter:&nbsp;-Dinfo.aduna.platform.appdata.basedir=
#** repositories location can be explicitly defined by using parameter:&nbsp;-Dinfo.aduna.platform.appdata.basedir=<repositories_location>
#* The location for the 'repositories' folder under Windows varies depending on the version of Windows and the installation method for Tomcat - some possibilities are:
#** {{C:\Users\<username>\AppData\Roaming\Aduna\repositories}} (Windows 7 when running Tomcat as a user)



bq. Invocation of init method failed; nested exception is java.io.IOException: Unable to create logging directory /usr/share/tomcat6/.aduna/openrdf-sesame/logs
then this indicates that Tomcat does not have write permission to its data directory (where it stores configuration, logs, and actual repository data). To fix this, log in as root to the server machine and do the following:



bq. Parser has reached the entity expansion limit "64,000" set by the Application.
when it generates more than a specified number of 'entities'. The default limit for the built-in Java XML parser is 64,000, however it can be configured by using a Java system property. To increase the limit, pass the following to the JVM in which GraphDB/Sesame is running. Note that the actual value can be increased as necessary. Don't forget that if running in Tomcat then this must be passed to the Tomcat instance using the CATALINA_OPTS environment variable.