Webservice Jobs

Discussion created by 6979faefbacb4dee06d02fb1aad9714d on Oct 21, 2015
Latest reply on Oct 27, 2015 by Darren_Sniezak_40
Hi all,

We have a few web service jobs set up right now that are behaving extremely strangely.

Specifically, they will run the webservice WSDL fine (most of the time) but then report back that the job failed. We've noticed it happening with a few different jobs and the most bizarre aspect is that it's failing after exactly 5 minutes. I know what you're thinking, there must be a timeout set to make it fail at that time but the thing is that we've looked through every timeout parameter we can think of in UC4 and cannot find one. We're wondering at this point if maybe there's a timeout either in the WSDL or the corresponding .JAR file for which I'm going to search but wanted to see if anyone either

a) has had this happen before and has some idea as to why/how to fix it?
b) knows of a timeout parameter that can be set in UC4 somewhere that we may not be thinking about?

Seriously, anything anyone can do to shed some light on this would be very much appreciated, we've been trying to figure this out for a couple of weeks now.

-Bertie Wright