Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
I got Same Probleam If Any Updates Release or Not ?
Copy link to clipboard
Copied
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
Copy link to clipboard
Copied
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?
Copy link to clipboard
Copied
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
Copy link to clipboard
Copied
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
Copy link to clipboard
Copied
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
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
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
Copy link to clipboard
Copied
Chris, do you know what Flex SDK version this issue was fixed in?
Copy link to clipboard
Copied
The bug has been logged here: https://bugbase.adobe.com/index.cfm?event=bug&id=2872062
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
I'll see if I can track this down and find out what's going on. I'll provide more info asap.
Thanks,
Chris
Copy link to clipboard
Copied
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 ?
Copy link to clipboard
Copied
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
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
Hi,
Please provide me a solution or please confirm that this bug has not been fixed yet by Adobe for FileReference.download() method .....
Copy link to clipboard
Copied
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
Copy link to clipboard
Copied
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
Copy link to clipboard
Copied
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