Thanks Mahmut,

I did not try the taverna.wsdl.timeout setting with Taverna 1.7 because
Taverna 2.1 apparently has improved a lot and we decided to implement all
the workflow in the new version.

That setting seems exactly what we want for this timeout issue.  I am pretty
sure that was the client-side timeout as the Catalina.out did not log any
timeout exception.  I did not know if tavern.wsdl.timeout is still available
in Taverna 2.1.

Being more specific, some external java programs are called from our web
services using runtime().exec() followed by waitfor() to ensure the
subprocess returns before next service in the workflow gets executed. I
guess waitfor() caused Taverna timeout exception.

If I implement the service asynchronously, i.e., get rid of waitfor(), the
next service in the pipeline will suffer because the input might have not
been returned by its predecessor. Correct me please if I have a wrong
understanding about the asynchronous implementation.

As for not using Soaplab, we used Soaplab2 in all our previous pipelines,
but we found JAXWS works a lot better for its significantly less
configuration and coding work.

Thanks a lot.

Fan


-----Original Message-----
From: [email protected] [mailto:[email protected]] 
Sent: July 18, 2009 4:43 AM
To: [email protected]
Subject: Re: [Taverna-users] Service timeout


The error you are getting definitely looks like an axis timeout issue,
looks like there is no easy way of setting it using configuration files,
probably for this reason taverna developers implemented the above
property.

Do you get the same timeout error when using taverna-1.7 after setting
this property in taverna-1.7 as well? if it works in taverna-1.7 it may
mean a bug in taverna-2.

The last thing you can do implement your service asynchronously. in simple
terms
  - start your jobs in threads
  - your updated 'run' method should return job ids (internally associated
with your threads)
  - implement a getStatus method that checks whether the thread associated
with a given jobid is still running
  - implement a getResultsMethod given a job id returns your job

Actually soaplab do all above, i wonder why you don't want to use soaplab?

Good weekend.
Mahmut


No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.5.392 / Virus Database: 270.13.19/2244 - Release Date: 07/17/09
18:00:00


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
taverna-users mailing list
[email protected]
[email protected]
Web site: http://www.taverna.org.uk
Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/

Reply via email to