A

Anonymous

Question

RemoteObject request timeout

Forum|Forum|17 years ago
April 3, 2008
9 replies
17466 views

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!

Performance issues

This topic has been closed for replies.

R

roumy

Participant

We ran into the same issue this week, having to send a custom file format as a ByteArray along with some custom mapped AS3 value objects to Zend AMF (knowing the file size can range from 100Ko to over 5Mo and request was systematically shut after 8-9 seconds on a Windows 10 desktop computer).

The solution is in fact to set two properties with the same value on the channel of your RemoteObject.

Let's say you instantiate it programmatically :

var remote : RemoteObject = new RemoteObject("zendamf");

var channel : AMFChannel = new AMFChannel ( "zendamf-application-endpoint", "http://domain.com/services/application/public/amf" );

channel.connectTimeout = 150; // seconds

channel.requestTimeout = 150; // seconds

var channelSet : ChannelSet = new ChannelSet();
channelSet.addChannel(channel);

remote.channelSet = channelSet;
remote.source = "AMF_Service";

Hope this helps !

B

bh-pano-life

Participant

It´s still broken. Using AIR 3.6 and php. On server side I just put sleep(60) then return something and it is broken, but AIR doesn´t wait on Desktop, it DOES wait on an iPad we testet on. Works with Flex/Flash as well. Please fix this! It´s very important for our project.

3/8/2013 14:05:11.909 [INFO] mx.messaging.Channel 'AMF_Service' channel endpoint set to http://192.168.178.88/amf

3/8/2013 14:05:11.913 [INFO] mx.messaging.Producer 'DDE585D9-E1B3-7FFF-C152-4A1AEEDEDDA8' producer set destination to 'AMF_Service'.

3/8/2013 14:05:11.918 [INFO] mx.messaging.Producer 'DDE585D9-E1B3-7FFF-C152-4A1AEEDEDDA8' producer sending message '55DB88DB-8804-C756-818E-4A1AEEEDFA31'

3/8/2013 14:05:12.005 [DEBUG] mx.messaging.Channel 'AMF_Service' pinging endpoint.

3/8/2013 14:05:12.145 [INFO] mx.messaging.Channel 'AMF_Service' channel is connected.

3/8/2013 14:05:12.148 [DEBUG] mx.messaging.Channel 'AMF_Service' channel sending message:

(mx.messaging.messages::RemotingMessage)#0

body = (Array)#1

clientId = (null)

destination = "AMF_Service"

headers = (Object)#2

messageId = "55DB88DB-8804-C756-818E-4A1AEEEDFA31"

operation = "getStuff"

source = "AMF_Service"

timestamp = 0

timeToLive = 0

ChannelEvent: channel connect

3/8/2013 14:05:12.150 [INFO] mx.messaging.Producer 'DDE585D9-E1B3-7FFF-C152-4A1AEEDEDDA8' producer connected.

3/8/2013 14:05:12.257 [INFO] mx.messaging.Producer '836795A9-95A8-9886-8497-4A1AF03CE655' producer set destination to 'AMF_Service'.

3/8/2013 14:05:42.699 [DEBUG] mx.messaging.Channel 'AMF_Service' channel got status. (Object)#0

code = "NetConnection.Call.Failed"

description = "HTTP: Failed"

details = "http://localhost:37813/amf?hostport=192.168.178.88&https=N&id=-1"

level = "error"

[object Channel]

ChannelFaultEvent: NetConnection.Call.Failed: HTTP: Failed

[ChannelSet AMF_Service ]

ChannelFaultEvent: NetConnection.Call.Failed: HTTP: Failed

3/8/2013 14:05:42.701 [WARN] mx.messaging.Producer 'DDE585D9-E1B3-7FFF-C152-4A1AEEDEDDA8' producer channel faulted with Channel.Call.Failed NetConnection.Call.Failed: HTTP: Failed

3/8/2013 14:05:42.703 [ERROR] mx.messaging.Producer 'DDE585D9-E1B3-7FFF-C152-4A1AEEDEDDA8' producer fault for '55DB88DB-8804-C756-818E-4A1AEEEDFA31'.

[RemoteObject destination="AMF_Service" source="AMF_Service" channelSet="[ChannelSet AMF_Service ]"]

FaultEvent: NetConnection.Call.Failed: HTTP: Failed

3/8/2013 14:05:42.708 [INFO] mx.messaging.Channel 'AMF_Service' channel polling stopped.

3/8/2013 14:05:42.709 [INFO] mx.messaging.Channel 'AMF_Service' channel disconnected.

3/8/2013 14:05:42.710 [INFO] mx.messaging.Channel 'AMF_Service' channel has exhausted failover options and has reset to its primary endpoint.

3/8/2013 14:05:42.710 [INFO] mx.messaging.Channel 'AMF_Service' channel endpoint set to http://192.168.178.88/amf

ChannelEvent: lost connection

3/8/2013 14:05:42.712 [WARN] mx.messaging.Producer 'DDE585D9-E1B3-7FFF-C152-4A1AEEDEDDA8' producer channel disconnected.

3/8/2013 14:05:42.714 [DEBUG] mx.messaging.Channel 'AMF_Service' pinging endpoint.

3/8/2013 14:05:42.828 [INFO] mx.messaging.Channel 'AMF_Service' channel is connected.

ChannelEvent: channel connect

3/8/2013 14:05:42.828 [INFO] mx.messaging.Producer 'DDE585D9-E1B3-7FFF-C152-4A1AEEDEDDA8' producer connected.

chris.campbell

Community Manager

@ph-pano-life

Could you please open a new bug report on this over at bugbase.adobe.com? When adding the bug, please include sample code or an application so we can quickly test this out internally. If you'd like to keep this private, feel free to email the attachment to me directly (ccampbel@adobe.com).

Once added, please post back with the URL so that others affected can add their comments and votes.

Thanks,

Chris

K

kevinchenYJ

Participant

reset "netConnection.httpIdleTimeout" property

A

andres_margalef

Participant

I have the same problem.

V

VilleFluide

Participating Frequently

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.

chris.campbell

Community Manager

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

Thanks,

Chris

N

Nedumangad Chandra

Participating Frequently

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 ?

V

VilleFluide

Participating Frequently

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

L

lnexus

Participant

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?

A

Anonymous

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

P

pranavDP

Participant

I got Same Probleam If Any Updates Release or Not ?

J

joechristopher

Participating Frequently

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

C

cameroncf

Participant

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...

A

Anonymous

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

C

cameroncf

Participant

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

C

cameroncf

Participant

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?

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded