thanks,
yes i read this post already, but than I read somewhere thar AIR has a
default of 30sec timeout
and got away from this solution...also because waiting > 30sec for a
DB-query to return (not millions of rows)
would not be a real solution
but I will keep this in mind
but, the provider told me to give him some time figures when the error
occurred so he could look at logs etc.
I told the customer to write down the time when error occurs
so we had 10:31, 10:35 10:40, 10:42 yesterday (hh:mm)
shouldn't the provider be able to see heavy load on the server at these
times if that was the case? (if he is willing to;))
(I'm not really in the server-admin-stuff)
maybe i should try, if the error occurs, immediately try to "ping" the
server and also another server like google
if only the second ping is succesfull, then it is the server not AIR or else
very intersting, as I said we will first finish the new version and then
maybe investigate further
Am 18.02.2016 um 16:55 schrieb Clint M:
You might get this error if the remote object is timing out... possibly
because the server is under too much load.
It seems like someone is having a similar issue with a workaround by
setting the connectTimeout and requestTimeout properties on the amf channel.
Check the last post on this thread: https://forums.adobe.com/thread/100543
Here's a full example of how to setup an amf channel at runtime:
https://gertonscorner.wordpress.com/2008/09/06/remoteobject-using-amfphp-and-actionscript-3/
This will also override anything you have setup using services-config.xml
which generates code at compile time so you could do away with compiling
those in if you're actually using a services-config.xml in the first place.
On Thu, Feb 18, 2016 at 7:48 AM, Frank Dahmen <[email protected]> wrote:
thanks,
- no this version uses 2 or 3 year old sdk and AIR
- it's the message of the FaultEvent in the eventlistener of the
RemoteObject, can't say the whole text now (error not reproducable)
"........http failed"
- yes, it worked, the app is in production phase for 2 years
we will see with the new version, if the error also occurs, we will have
to investigate more
