$JUMMP_CONF env variable not picked up by System Configuration pages

In our setup JUMMP configuration file is in non-standard location:

/opt/ebi/jummp/etc/repo.properties

and we specify this location via tomcat setenv.sh script using JUMMP_CONF environment variable.

The instance picks up the custom properties location during startup just fine, but System Configuration pages seem to still assume that the default JUMMP configuration file location is used.

E.g. when navigating to the page:

http://<HOST>/model-repository/configuration/database

I get the following error:

java.io.FileNotFoundException: /home/<user>/.jummp.properties (No such file or directory)

    at java.io.FileInputStream.<init>(FileInputStream.java:146)

    at net.biomodels.jummp.plugins.configuration.ConfigurationService.loadProperties(ConfigurationService.groovy:814)

    at net.biomodels.jummp.plugins.configuration.ConfigurationService.loadDatabaseConfiguration(ConfigurationService.groovy:209)

    at net.biomodels.jummp.plugins.configuration.ConfigurationController$_closure2.doCall(ConfigurationController.groovy:50)

    at grails.plugin.cache.web.filter.PageFragmentCachingFilter.doFilter(PageFragmentCachingFilter.java:200)

    at grails.plugin.cache.web.filter.AbstractFilter.doFilter(AbstractFilter.java:63)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

    at java.lang.Thread.run(Thread.java:744)

This happens in all /model-repository/configuration/* endpoints.

The workaround for this was to create a symlink from /home/<user>/.jummp.properties to the same location where the $JUMMP_CONF environment variable is pointing to.

Comments (0)