RemoteObject request timeout

Report · Apr 03, 2008

I am having an issue with a request failing when executing a long data call (examining over 9 million rows). I have compiled the app in Flex and all is fine, but when I compile the same code using WindowedApplication (an AIR app) the request seems to fail after 30 seconds with the shorter data calls working fine. I have set the requestTimeout property to 0 in my RemoteObject and have tried setting numerous timeouts within the Web.config, services-config.xml, and the remoting-config.xml to no avail. Am I missing something? Please help!

Report · Apr 28, 2008

I'm experiencing this same problem. It's just right at 30 seconds max for the timeout. I can't get AIR to obey any requesttimeout values higher than 30 seconds.

jukee - did you ever find a solution to your problem?

Report · Apr 28, 2008

I ended up defining a channel to use RTMP instead of HTTP. I select my remote object based off of my estimated query time.

Report · Apr 28, 2008

Ahhh... Yes, I am going to have to workaround this somehow too. FYI - Someone reported it in JIRA as a bug today. Go vote for it if you can.

https://bugs.adobe.com/jira/browse/SDK-15403

Report · May 08, 2008

I just ran across this thread. Anyone have any luck? I looked at the bug link that Cameron provided but it shows a closed status. What's the deal with that?

Here's my issue with File.upload():
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=75&catid=697&threadid=1360921

Report · May 08, 2008

I think they closed the issue because it was logged as an SDK bug, but in reality is a bug in the AIR player. Also, it seemed that it was assigned an internal bug number by someone at Adobe, so I think it's being worked on now for a future release. At any rate, it's been acknowledged as a reproducible bug by someone at Adobe.

I'll reply in your other thread about your specific issue...

Report · Sep 23, 2009

I got Same Probleam If Any Updates Release or Not ?

Report · Jun 13, 2010

Dear all,

We are developing under AIR 2.0 beta 2 on Windows (Vista or 7) and we still have this 30 seconds limitation on RemoteObject calls, whatever we fix in Channel.requestTimeout or operation.service.requestTimeout. According to this post this bug has been fixed in AIR1.1, but it seems that it is still there.

This is very annoying. Is there a workaround ? (this 30 sec value must surely be fixed somewhere in source code or config values).

Regards and thanks for help,

Cédric

Report · Jul 05, 2010

Hi,

We are developing in Air 2.0 and still getting the same issue, no matter what the requestTimeout is for the RemoteObject, it seems to bypass this and automatically go for 30 sec. It has been more than 2 years now, judging by the post date from the OP and we're still waiting for a fix?

Report · Aug 17, 2010

I also just ran into this issue with RemoteObject for an AIR 2.0 application on Windows. The request (in this case, a large file upload) times out after exactly 30 seconds.

Any progress from Adobe on this issue or viable workarounds?

Thanks,

-Jose

Report · Aug 18, 2010

I know that Jose has already seen this, but for others following along, please see this thread for further discussion on this issue.

Moved discussion to the Problems & Bugs forum.

Chris

Report · Aug 19, 2010

There was a change introduced to the networking sub-system in AIR 2 which will cause RemoteObjects (which make use of NetConnection for their communication) to have a shorter idleTimeout on Windows when using the AIR 2.0 namespace (usually around 30 seconds but varies depending on which version of msinet.dll is installed).

We are working on a resolution for this issue to be included in the next release of the AIR Runtime.

Please refer to the following item in the Flex public bugbase for additional information:

https://bugs.adobe.com/jira/browse/SDK-22016

At this time, the only known workaround for RemoteObjects is to publish your AIR application with a namespace less than 2.0.

Chris Thilgen

AIR Engineering

Report · May 10, 2011

I'm running AIR 2.6 and this is still an issue. You said you were working on a resolution for the "next release" - did this ever happen?

I can replicate the issue with both AIR and ADL versions 2.6, using the 2.6 namespace.

Report · May 10, 2011

From my understanding, this should have been fixed in the latest AIR and Flex SDK's. Would you mind adding a new bug to bugbase.adobe.com and include some sample code or project that illustrates the problem? It would be great if you could post back with the bug URL so others effected can cast their votes and add comments.

Thanks,

Chris

Report · May 10, 2011

Chris, do you know what Flex SDK version this issue was fixed in?

Report · May 10, 2011

The bug has been logged here: https://bugbase.adobe.com/index.cfm?event=bug&id=2872062

Report · May 10, 2011

Guys,

The bug has been announced to be fixed and closed by alisa wang (see attached mail, we received 04/26 see http://bugs.adobe.com/jira/browse/FP-4934.

The problem is that she just says : "An internal bug was already tracking this issue."

So that means it is not fixed...

The related one https://bugs.adobe.com/jira/browse/SDK-22016 is also marked as closed and fixed...

We confirm that we still have this bug, even with very last AIR release.

And another interesting thing, we have some PC on Windows 7 in our team, where the workaround (modifying Win Registry) doesn't work, timeout stays to 30 seconds whatever we do. Very strange. On other PCs it works.

Today we are not annoyed because the software is not used outside our company. But it will be in the future. This will be a quite big problem, as we must then have a dedicated installer for the AIR app, this installer doing first the registry fix, and install the AIR app after... And we'll still have the issue on some PCs we don't know why in some PCs the workaround doesn't work in fact. And overall there might have side effects on other apps if we update this receiveTimeout key in registry, maybe..

AIR is a great product really, but PLEASE ADOBE TEAM FIX THIS 3 YEARS OLD BUG !!!!!!!!!!!!!!!!!!! the initial post on this was https://bugs.adobe.com/jira/browse/SDK-15403, posted 4/28/08...

Cédric NICOLAS.

Report · May 11, 2011

I'll see if I can track this down and find out what's going on. I'll provide more info asap.

Thanks,

Chris

Report · Sep 22, 2011

I am using FileReference.download method for downloading one file from the server.The same issue exists for me. After 30 seconds,IOError pops out which stops my download process.Did anyone find a solution for this ?

Report · Sep 22, 2011

We don't use this function and that bug is related to RemoteObject call in AIR applications, but for you 3 things to try :

1) use File class instead of FileReference, if you are in AIR application, see doc :"

Note: In Adobe AIR, the File class, which extends the FileReference class, provides more capabilities and has less security restrictions than the FileReference class."

2) Set values of the following parameter : URLRequestDefaults.idleTimeout to 180000 for example (3 minutes). Normally this should work, if the bug related here is fixed (not verified)

3) if you run on Windows, set ReceiveTimeout Windows registry value, as is it is explained there : http://support.microsoft.com/kb/181050.

Cédric

Report · Sep 23, 2011

I am using flex 3 sdk with 2.7 air sdk and htmlPlayerVersion="10.0.0" in my compiler settings.I tried first 2 ways..but those are not working.3rd point (editing the OS registry value) is not possibile since for evey client systems we cannot do that.So please give another solution for FileReference.download timeout issue.

Report · Sep 25, 2011

Hi,

Please provide me a solution or please confirm that this bug has not been fixed yet by Adobe for FileReference.download() method .....

Report · Sep 25, 2011

Could you please open a new bug over at bugbase.adobe.com and include sample code that will illustrate what you're seeing? If you'd prefer to keep your code private, please feel free to email it to me directly at ccampbel@adobe.com. I do believe the original issue from this thread was addressed, but getting a bug in on your problem will make sure we follow up properly. Please post back with the bug URL so others affected can add their votes and comments.

Thanks,
Chris

Report · Dec 12, 2012

Hi, I have the problem of timeout with Adobe air 2.0 FlashBuilder 4.1. I use blazeDS with Tomcat.

I've tried to set a value of requestTimeout for the remoteObject > 30 but The problem still again.

If the Java function i too long (>30 sec) I have this error:

RPC Fault faultString="error" faultCode="Channel.Call.Failed" faultDetail="NetConnection.Call.Failed: HTTP: Failed"

Could you help me? Can I have a way to change the timeout?

Thanks

Silvia P

Report · Dec 12, 2012

Silvia,

First upgrade if possible your AIR version. Current one is 3.5 ! Bug has been corrected in 3.1. You'll have also to upgrade also your Flash Builder.

If you cannot, then only solutions are described in post of 22.09.11 in this topic.

Cédric