Automatically exported from code.google.com/p/blazeds-servlet3-support on 15th Dec, 2015
Extension to the BlazeDS server to support Servlet 3 API in handling continues requests. Each streaming connection managed with Servlet 3.0 endpoint doesn't consume one of the request handler threads provided by the servlet container, so it is highly scalable in comparison with standard streaming endpoint.
- Install Tomcat 7 and Blaze DS 4. The turnkey install of BlazeDS 4 is not going to work since it ships with Tomcat 6.
- Once you have Tomcat and BlazeDS working fine, change the Tomcat Connector configuration to use the NIO connector instead of the BIO conntector. The setting is in the server.xmland should be changed as follows.
<!--<Connector port="8400" protocol="HTTP/1.1"
connectionTimeout="20000" redirectPort="8443"/>-->
<Connector connectionTimeout="20000" port="8400"
protocol="org.apache.coyote.http11.Http11NioProtocol" redirectPort="8443"/>
- In your Tomcat BlazeDS application context change the Servlet configuration to allow asynchronous capability for the MessageBrokerServlet?. This should be done in the web.xml as follows. Notice the lines marked by *
<servlet>
<servlet-name>MessageBrokerServlet</servlet-name>
<display-name>MessageBrokerServlet</display-name>
<servlet-class>flex.messaging.MessageBrokerServlet</servlet-class>
<init-param>
<param-name>services.configuration.file</param-name>
<param-value>/WEB-INF/flex/services-config.xml</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
*<async-supported>true</async-supported>*
</servlet>
<filter>
<filter-name>springSecurityFilterChain</filter-name>
<filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class>
*<async-supported>true</async-supported>*
</filter>
- Copy the compiled blazeds-servlet3-support jar file to the WEB-INF/lib folder of the context.
- Change the WEB-INF/flex/service-config endpoint as follows.
<channel-definition id="amf-stream" class="mx.messaging.channels.StreamingAMFChannel">
<endpoint url="/http://{server.name}:{server.port}/{context.root}/messagebroker/streamingamf"
class="org.iobit.servlet3.endpoint.AMFServlet3Endpoint"/>
<properties>
<idle-timeout-minutes>3</idle-timeout-minutes>
<max-streaming-clients>10000</max-streaming-clients>
<server-to-client-heartbeat-millis>500</server-to-client-heartbeat-millis>
</properties>
</channel-definition>
- Restart Tomcat and you should be good to go!
An explanation of how this can be used can be found in the following post Scaling BlazeDS with Servlet 3
##Channel Definition Example Example of a Channel Definition to use this endpoint
<channel-definition id="amf-stream" class="mx.messaging.channels.StreamingAMFChannel">
<endpoint url="/http://{server.name}:{server.port}/{context.root}/messagebroker/streamingamf"
class="org.iobit.servlet3.endpoint.AMFServlet3Endpoint"/>
<properties>
<idle-timeout-minutes>7</idle-timeout-minutes>
<max-streaming-clients>500</max-streaming-clients>
<server-to-client-heartbeat-millis>500</server-to-client-heartbeat-millis>
<enable-debug-mode>true</enable-debug-mode>
</properties>
</channel-definition>
-
idle-timeout-minutes - Use this to set the time-outs for the streaming connections
-
max-streaming-clients - Use this to set the total number of streaming clients you want to limit the endpoint to.
-
server-to-client-heartbeat-millis - Use this to adjust the latency vs server process consumption. Reducing this value may make your server go hot. Increasing the value will increase the latency on the messages
-
enable-debug-mode - Keep this false unless you want to see the code traces on your server log. This can make your log files bloat up pretty fast