This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Firefox 29 generating communication error in Adobe Flash / Blaze DS

mford23
mford23
more options

Our company has developed an application using Adobe FlashBuilder with Server Side communication via BlazeDS and Apache Tomcat 6.0. This application has been in production for years. In one part of our application, we have a Java method that can take 15 minutes to complete its task before returning results to the user. Since Firefox 29, about 5 minutes into the process, we now throw...

[RPC Fault faultString="Channel disconnected" faultCode="Client.Error.DeliveryInDoubt" faultDetail="Channel disconnected before an acknowledgement was received"] at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()[E:\dev\4.y\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:345] at mx.rpc::Responder/fault()[E:\dev\4.y\frameworks\projects\rpc\src\mx\rpc\Responder.as:68] at mx.rpc::AsyncRequest/fault()[E:\dev\4.y\frameworks\projects\rpc\src\mx\rpc\AsyncRequest.as:113] at NetConnectionMessageResponder/channelDisconnectHandler()[E:\dev\4.y\frameworks\projects\rpc\src\mx\messaging\channels\NetConnectionChannel.as:689] at flash.events::EventDispatcher/dispatchEventFunction() at flash.events::EventDispatcher/dispatchEvent() at mx.messaging::Channel/disconnectSuccess()[E:\dev\4.y\frameworks\projects\rpc\src\mx\messaging\Channel.as:1203] at mx.messaging.channels::NetConnectionChannel/internalDisconnect()[E:\dev\4.y\frameworks\projects\rpc\src\mx\messaging\channels\NetConnectionChannel.as:175] at mx.messaging.channels::AMFChannel/internalDisconnect()[E:\dev\4.y\frameworks\projects\rpc\src\mx\messaging\channels\AMFChannel.as:355] at mx.messaging.channels::AMFChannel/statusHandler()[E:\dev\4.y\frameworks\projects\rpc\src\mx\messaging\channels\AMFChannel.as:445]


The underlying code has not been changed in over a year. Performing the exact same operation in Google Chrome does not generate any errors.

Our company has developed an application using Adobe FlashBuilder with Server Side communication via BlazeDS and Apache Tomcat 6.0. This application has been in production for years. In one part of our application, we have a Java method that can take 15 minutes to complete its task before returning results to the user. Since Firefox 29, about 5 minutes into the process, we now throw... [RPC Fault faultString="Channel disconnected" faultCode="Client.Error.DeliveryInDoubt" faultDetail="Channel disconnected before an acknowledgement was received"] at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()[E:\dev\4.y\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:345] at mx.rpc::Responder/fault()[E:\dev\4.y\frameworks\projects\rpc\src\mx\rpc\Responder.as:68] at mx.rpc::AsyncRequest/fault()[E:\dev\4.y\frameworks\projects\rpc\src\mx\rpc\AsyncRequest.as:113] at NetConnectionMessageResponder/channelDisconnectHandler()[E:\dev\4.y\frameworks\projects\rpc\src\mx\messaging\channels\NetConnectionChannel.as:689] at flash.events::EventDispatcher/dispatchEventFunction() at flash.events::EventDispatcher/dispatchEvent() at mx.messaging::Channel/disconnectSuccess()[E:\dev\4.y\frameworks\projects\rpc\src\mx\messaging\Channel.as:1203] at mx.messaging.channels::NetConnectionChannel/internalDisconnect()[E:\dev\4.y\frameworks\projects\rpc\src\mx\messaging\channels\NetConnectionChannel.as:175] at mx.messaging.channels::AMFChannel/internalDisconnect()[E:\dev\4.y\frameworks\projects\rpc\src\mx\messaging\channels\AMFChannel.as:355] at mx.messaging.channels::AMFChannel/statusHandler()[E:\dev\4.y\frameworks\projects\rpc\src\mx\messaging\channels\AMFChannel.as:445] The underlying code has not been changed in over a year. Performing the exact same operation in Google Chrome does not generate any errors.

Toate răspunsurile (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Yes, there is a new 5-minute timeout. https://developer.mozilla.org/en-US/Firefox/Releases/29/Site_Compatibility#Networking