You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by Simone Bnà <s....@cineca.it> on 2016/09/05 11:00:50 UTC

Re: OperatingLimit and MaxRuns in Taverna

Dear Taverna staff,

I've been told that Taverna queues the workflows that are triggered after reaching the maximum number of "operating" workflows (aka OperatingLimit) but not the runLimit.

What I noticed is instead that Taverna complains and return the following error:

http error status code 503; server too busy; try later please

Are there some configuration parameters that need to be changed in order to activate the workflow queue?

Best regards,

Simone.





----- Original Message -----
From: "alaninmcr" <al...@googlemail.com>
To: users@taverna.incubator.apache.org
Sent: Friday, August 26, 2016 11:29:41 AM
Subject: Re: OperatingLimit and MaxRuns in Taverna

On 25/08/2016 20:48, Simone Bnà wrote:
> Dear Taverna team, users,

Hello

> I am wondering how to change the "OperatingLimit" and "MaxRuns" in Taverna as written here:
>
> http://dev.mygrid.org.uk/wiki/display/tav250/Taverna+Server+FAQ
>
> Is there an API or a config file to be modified?

There is a configuration file - see 
http://dev.mygrid.org.uk/wiki/display/tav250/Administration+Guide

> What happens if I try to run a new workflow when the number of "operating" workflows reached the maximum allowed value?

Then it is queued.

> Is the workflow added in a queue and when some "operating" workflows finish, it is triggered or Taverna returns an Error?

It will run.

> Thanks.
>
> Best regads,
>
> Simone.

Alan


-- 
Simone Bnà, PhD
C++ Software Developer, CINECA
Via Magnanelli 6/3, 40033 Casalecchio di Reno, Italy
office:   +39-0516171938
email: s.bna@scsitaly.com/s.bn@cineca.it