On Nov 15, 2012, at 12:17 PM, Jennifer Jackson wrote:
> Hi Akshay,
> Please post all technical questions directly to the galaxy-dev mailing list.
> I'm sure we'll be able to help out shortly,
> Galaxy team
> My name is Akshay and I am a computer science graduate student at UGA in Dr.
> Kissinger's Lab. We have created an extension to galaxy which allowed users
> to add web services as tools into galaxy, these could be either used as
> stand-alone or in a workflow. I wanted to know if Galaxy employs any time out
> Consider a case where I have a workflow with BLASTP now it takes some time to
> run blast and then get result form it. When I try that experiment as
> standalone (i.e., running the run method first and then after several mins
> getting result using job id works) however when I create a workflow in which
> one tool being run method of blast followed by getresult, galaxy seems to
> time out.
> Would appreciate your feedback on the same.
Galaxy itself doesn't have a timeout, but often the proxy server does. If
Galaxy takes too long to respond to a request (some requests block, such as
creation of complex workflows), a timeout may be reported to the client.
Galaxy typically finishes the request behind the scenes, however.
> -Akshay Choche
> 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:
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: