Flex BlazeDS timeout on server side after 60 seconds

Question

I have an application based on flex client and blazeds at the server side. Scenario: 1. Client makes a remoting call over secure-amf channel. 2. Server takes some time processing the request usually more than 60 seconds

When server side code tries to write back to the pipe over which the connection is made. it reports broken pipe error.

I have found several queries on this topic without any conclusive solution.

Error log at servier side: [BlazeDS]java.io.IOException: Broken pipe Write failed: Broken pipe

Here is my serives-config.xml snippet.

<channel-definition id="my-secure-amf"             class="mx.messaging.channels.SecureAMFChannel">
<endpoint url="https://{server.name}:{server.port}/{context.root}/messagebroker/amfsecure"   class="flex.messaging.endpoints.SecureAMFEndpoint"/>
            <properties>
                <add-no-cache-headers>false</add-no-cache-headers>
            </properties>
</channel-definition>

henrik henrik · Accepted Answer · 2015-02-09T13:15:34

The time-out of your AMF/http connection is set by your Http server application. And depending on what server you are running, you should look for the configuration matching timeout-value. If you are running Apache Tomcat 7, refer to the following configuration: http://tomcat.apache.org/tomcat-7.0-doc/config/http.html

There is also a possibility to change the timeout in the services-config.xml: (but this isn't applicable to you)

<channel-definition id="my-channel" .... >
  <endpoint url...../>

  <properties>

    <add-no-cache-headers>false</add-no-cache-headers>

    <connect-timeout-seconds>10</connect-timeout-seconds>

  </properties>

</channel-definition>

Flex BlazeDS timeout on server side after 60 seconds

1 Answers