D4Science Infrastructure

We face a problem when we try to run some experiments within the bluebridge infrastructure with openCpu/WPS client because a timeout error is thrown.
This is caused by the fact that OpenCpu is set to timeout after 90 seconds while some experiments can get some more time.
We strongly suggest to increase the opencpu's timeout settings to around 400 seconds to avoid these kind of problems due to the fact these experiments require heavy and time consuming calculations (an example is org.gcube.dataanalysis.wps.statisticalmanager.synchserver.mappedclasses.transducerers.ICHTHYOP_MODEL_ONE_BY_ONE )

the opencpu timeout can be configured inside /etc/opencpu/server.conf
to make the change effective a service restart is required with the command service opencpu restart