incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel A. Pierre (JIRA)" <>
Subject [jira] [Commented] (FLEX-28407) RemoteObject times out after 30 seconds every time (not fixed)
Date Thu, 11 Oct 2012 16:33:03 GMT


Lionel A. Pierre commented on FLEX-28407:

I set the same delay in URLRequestDefaults.idleTimeout and in the remoteObject's requestTimeout.

Having both set to the same value seems to have effectively extended my timeout (Flex 4.6).

private var _ro:RemoteObject;


URLRequestDefaults.idleTimeout = 180000;
_ro.requestTimeout = 180;
> RemoteObject times out after 30 seconds every time  (not fixed)
> ---------------------------------------------------------------
>                 Key: FLEX-28407
>                 URL:
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: RPC: RemoteObject
>    Affects Versions: Adobe Flex SDK 4.5.1 (Release)
>         Environment: Affected OS(s): Windows
> Affected OS(s): Windows 7
> Language Found: English
>            Reporter: Adobe JIRA
> If I call a PHP script using RemoteObject and ZendAMF that takes longer than 30 seconds
to complete, the request fails, even though max_execution_time on the server is more than
30 seconds.
> (I believe that the max timeout on PC is 60 seconds. But on Android it is for sure only
30 seconds)
> This happens with both AIR and ADL 2.6. (and 2.7)
> When the request fails, Network Monitor says:
> {Fault code=Channel.Call.Failed, Fault string=error, Fault detail=NetConnection.Call.Failed:
HTTP: Failed, Destination=zend}
> This also happens when the backend is Coldfusion Flash remoting gateway. 
> Seems to be connected to some sort of a max request timeout outside of the SDK.
> If you follow the direction in the following link
the issue is actually resolved (only on the machine you make the change on), but it may shed
some light on the core cause of this problem.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message