I set up a simple method in a CFC on my server.

<cfcomponent name="Remoting">
<cffunction name="testConnect" access="remote" returntype="any"
output="false">
<cfreturn true />
</cffunction>
</cfcomponent>

A simple Flex RemoteObject call is throwing an error with te following message:

mx.rpc.remoting.mxml.RemoteObject
"Channel disconnected"
Fault Code: Client.Error.DeliveryInDoubt
Detail: Channel disconnected before an acknowledgment was received

Here is my MXML:

<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
<mx:RemoteObject id="svc" destination="ColdFusion"
source="irovrdev.controller.RemotingService"
endpoint="http://remoting.irovr.com/flex2gateway/" showBusyCursor="true" />
<mx:Button click="svc.testConnect()" />
</mx:Application>


I know it's not a mapping issue, because if I fudge the name of the source to
"foo", I get a valid error from ColdFusion that the component is not found.

I am also getting the same error "Channel disconnected". If you have any answer please post it. I changed IIS timeout to 1 hour , that did not help. it is giving this error every 40 minutes or so...

Turns out our application.cfc was redirecting based on the http_user_agent. Make sure you are not using a cflocation that might be firing.

Same problem here

Hi ErikMadsen,
I had the same problem with the "channel disconnected". I changed it like you said and now it works.

Thanks,
Guido

I am also getting the same error "Channel disconnected". If you have any answer please post it. I changed IIS timeout to 1 hour , that did not help. it is giving this error every 40 minutes or so...

Turns out our application.cfc was redirecting based on the http_user_agent. Make sure you are not using a cflocation that might be firing.

Same problem here

Hi ErikMadsen,
I had the same problem with the "channel disconnected". I changed it like you said and now it works.

Thanks,
Guido

I am also getting the same error "Channel disconnected". If you have any answer please post it. I changed IIS timeout to 1 hour , that did not help. it is giving this error every 40 minutes or so...