Matthew, as you said there's no way to set the time out on cfobject
(or createobject).
A couple of things of interest (maybe);
http://whatever/whatever.cfc?wsdl";)>
Adobe explain it better... http://www.adobe.com/go/2d5f8cc9
Just use cfinvoke ;)
Also, the default WS timeout is 60 secon
Hi Matthew,
your explanation of the CFLOCK makes sense.
Thanks for letting us know!
David
Matthew wrote:
> Haikal I think you figured it out! I've messed around with the
> tag (without using the to initialise!) and think
> it will work, however I'll have to wait until the next outage from th
On 18/07/2007, at 1:04 PM, David Harris wrote:
>
> could you do this:
>
>
>
> type="readOnly]" throwOnTimeout="true">
>
>
Hey Dave,
That's only going to time out other threads trying to get in to the
lock while cfobject is hanging up.
Haikal's solution is a good one. CFers should remembe
Haikal I think you figured it out! I've messed around with the
tag (without using the to initialise!) and think
it will work, however I'll have to wait until the next outage from the
web service source to test properly.
FYI: the suggestion won't work because the timeout attribute
doesn't contr
Here's another thought:
If it actually is the cfobject call that's timing out, maybe you could
save the WSDL file to your server, and have it hit that?
That way you won't have to worry about it timing out, and you can
happily use
Haikal Saadh wrote:
> So it's the actual cfobject tag that's t
So it's the actual cfobject tag that's timing out? Not the subsequent
cfinvoke? cfinvoke seems to have a timeout parameter.
(Excuse my ignorance, never actually used cfobject for a web service call)
Matthew wrote:
> Howdy,
>
> Our CF server keeps crashing whenever a web service we are consuming
> Throwing daggers in the dark here, but worth a shot.
yeah, this sounds like what's really needed in CF are asynchronous
event handlers for when there's a result to return...
... like in XMLHTTPRequest (Ajax) or Flex/Flash.
--~--~-~--~~~---~--~~
You received thi
could you do this:
it broke!
This should throw on a time out.
EG: if the lock runs for more seconds than in the "timeout" attribute,
it'll thrown an error.
HTH
Matthew wrote:
> Done that already. But there is nothing to catch because it's not
> actually throwing an error because it's c
Ooh... interesting.
The only thing I can think of is maybe setting a named lock, with a
timeout around it, and set it to 'readonly', so that multiple threads
come in, but it should time out?
Throwing daggers in the dark here, but worth a shot.
Mark
On 7/18/07, Matthew <[EMAIL PROTECTED]> wrote
Done that already. But there is nothing to catch because it's not
actually throwing an error because it's carrying on indefinitely and
hence once we get half a dozen of these it sends the server into a
loop so no one can access the website.
I understand that even if the user closes there browser t
Maybe just a try / catch block around the webservice call?
Mark
On 7/18/07, Matthew <[EMAIL PROTECTED]> wrote:
>
> Howdy,
>
> Our CF server keeps crashing whenever a web service we are consuming
> falls over (infrequent and random). I have no control over the web
> service, so I am trying to fin
11 matches
Mail list logo
