On 30/10/2014 18:09, Hoeftberger, Johann wrote:
I try to install the current version of the Taverna server (2.5.4) on a 64 bit Linux machine (CentOS release 6.3), I can deploy the Taverna .war archive, but the web application doesn't start up.It seems there is an initialization issue with the used spring framework in the background, see logs below.
Technically speaking, it's actually foreground so far as Taverna Server is concerned; the configuration processing is done in a single thread prior to the registering of the webapp as a published endpoint.
I followed the instructions under http://dev.mygrid.org.uk/wiki/display/tav250/Installation+Guide, chose a self-signed certificate for SSL with the java tool, %JAVA_HOME%\bin\keytool. I adjusted the java cryptography settings and can use the Tomcat server with SSL. I could deploy the Taverna .WAR archive, BUT it doesn't start up. It always gives me the following errors:
[... There's just one real error ...]
org.springframework.beans.MethodInvocationException: Property 'defaultExecuteWorkflowScript' threw exception; nested exception is java.lang.NullPointerException
I'm puzzled as to why it would be setting the defaultExecuteWorkflowScript property and why that would be failing. That's something that is supposed to usually correctly self-bootstrap. Do you have anything set for the executeWorkflowScript configuration property? If so, please unset it. The default that is selected (via a magic token, "NONE" :-)) in the absence of anything explicitly overriding it ought to be to use the built-in copy of the workflow engine; that's virtually always the right choice (and perhaps this is something where simply removing the boot configuration option would be better, but I digress). Principal diagnosis: a null was sent to the method: void setDefaultExecuteWorkflowScript(String) in the class org.taverna.server.master.localworker.LocalWorkerState which was being instantiated and configured at that point. That particular method is not currently null-safe, but a null ought to not be appearing there either. I've no idea where the null is coming from; it's all driven from a PropertyPlaceholderConfigurer and that doesn't have a null-value set AFAIK. Leaving the property out of your configuration file entirely ought to work. Otherwise, use the string “NONE” (4 chars) explicitly. Donal.
<<attachment: donal_k_fellows.vcf>>
------------------------------------------------------------------------------
_______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/ Developers Guide: http://www.taverna.org.uk/developers/
