taverna-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Javıer R. Balderrama <jrbalderr...@gmail.com>
Subject Re: Could not find any active jobs for facade0
Date Thu, 13 Aug 2015 11:34:35 GMT
Alan,

I ran more tests and I realised that the error only occurs with 'Run after'
dependencies. With the same workflow configurations (number of services,
links between them) but regular links this issue does not appears.

--JRB

On Thu, Aug 6, 2015 at 2:26 PM, Javıer R. Balderrama <jrbalderrama@gmail.com
> wrote:

> Well, I cannot reproduce the problem systematically but I face it from
> time to time. That is why I'm no be able to execute workflows in batch mode
> without monitoring them all the time. A colleague here also reproduce it
> using a more recent OS and a different JRE. I think it worth trying to
> inspect this behaviour in case someone else tries to run Taverna by command
> line. I plan to execute more tests so I let you know if I have more
> feedback. About JIRA it is up to you.
>
> --JRB
>
> On Thu, Aug 6, 2015 at 1:47 PM, alaninmcr <alaninmcr@googlemail.com>
> wrote:
>
>> On 30/07/2015 21:41, Javıer R. Balderrama wrote:
>>
>>> Here you have a smaller version with 15 services.
>>> I reproduced the error by executing:
>>>
>>> for i in {1..100}; do executeworkflow.sh -logfile taverna.log
>>> control-0003x0005.t2flow; done​
>>>
>>
>> Hello
>>
>> I have tried to replicate the problem but haven't managed to.
>>
>> One workaround could be, if the services can be safely re-run, then to
>> configure them so that they are retried if they fail. That, at least, would
>> reduce the frequency you see failures.
>>
>> Do you want me to create the Jira issue?
>>
>> Alan
>>
>>
>

Mime
View raw message