D4Science Infrastructure

You can configure the servive to use the dev instance of orientdb.

In the config file you have to use the root password of dev instance. Generate new passwwords for admin adn users. Moreover the name of the db could be: joint-rr-preprod

The deploy fails with the following exception:

2017-11-21 19:30:29,757 [localhost-startStop-1] ERROR org.apache.catalina.core.StandardContext- Error during ServletContainerInitializer processing
javax.servlet.ServletException: cannot manage application @ /resource-registry (see cause)
    at org.gcube.smartgears.Bootstrap.onStartup(Bootstrap.java:71)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5493)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
    at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1073)
    at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
    at org.gcube.smartgears.managers.ApplicationManager.start(ApplicationManager.java:132)
    at org.gcube.smartgears.Bootstrap.onStartup(Bootstrap.java:61)
    ... 12 more
2017-11-21 19:30:29,763 [localhost-startStop-1] ERROR org.apache.catalina.core.StandardContext- Context [/resource-registry] startup failed due to previous errors

@luca.frosini@isti.cnr.it can you investigate?

@lucio.lelii@isti.cnr.it can you investigate too?

We think that the problem is in the configuration because also the version up and running in production has the same errors. Lucio and me are investigating