Have you made any progress on this, I have never heard of this
behavior but at the same time it does not surprise tremendously
either. How large is the workflow? If large - you will almost
certainly want to make sure you are using a Postgres database server
instead of sqlite. Likewise if you don't have a proxy like nginx or
Apache setup that might help.
You can checkout the following page for more information on scaling up Galaxy:
What version of Galaxy are you using?
Thanks for using Galaxy and good luck,
On Wed, Jun 18, 2014 at 11:33 AM, Carlos del Ojo <deep...@gmail.com> wrote:
> Hi All,
> I am using the API (posting to 'http://localhost:8080/api/workflows' )
> and running 8 workflows in a row.
> I use submit function imported from common.
> First call to submit takes few seconds to return from submit()
> second takes a few more seconds, but in the fifth submit it gets hanged.
> However if I start stopping all workflows via the web interface fifth
> submit() ends goes on with 6th 7th and 8th.
> I am not sure if there is a limit of workflows running in parallel but if a
> run them manually through the GUI they work fine (the eight)
> does anyone know why API calls get blocked? Is it maybe something to do with
> the Paste HTTP server used by galaxy?
> Please keep all replies on the list by using "reply all"
> in your mail client. To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
> To search Galaxy mailing lists use the unified search at:
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: