20.2.4. Configuring Netty HTTP
Netty HTTP tunnels packets over the HTTP protocol. It can be useful in scenarios where firewalls allow only HTTP traffic to pass. Netty HTTP uses the same properties as Netty TCP along with some following additional properties:
The following parameters can be used with acceptors as well as connectors. Netty HTTP transport does not allow the reuse of standard HTTP port (8080 by default). The use of standard HTTP port results in an exception. You can use Section 20.2.5, “Configuring Netty Servlet” (Netty Servlet Transport) for tunneling HornetQ connections through standard HTTP port.
<socket-binding name="messaging-http" port="7080" />
<acceptors> <netty-acceptor name="netty" socket-binding="messaging-http"> <param key="http-enabled" value="false"/> <param key="http-client-idle-time" value="500"/> <param key="http-client-idle-scan-period" value="500"/> <param key="http-response-time" value="10000"/> <param key="http-server-scan-period" value="5000"/> <param key="http-requires-session-id" value="false"/> </netty-acceptor> </acceptors>The following table describes the additional properties for configuring Netty HTTP:
Table 20.3. Netty HTTP Configuration Properties
|http-enabled||false||If this is true HTTP is enabled|
|http-client-idle-time||500 milliseconds||How long a client can be idle before sending an empty HTTP request to keep the connection alive|
|http-client-idle-scan-period||500 milliseconds||How often (milliseconds) to scan for idle clients|
|http-response-time||10000 milliseconds||The time period for which the server can wait before sending an empty HTTP response to keep the connection alive|
|http-server-scan-period||5000 milliseconds||How often, in milliseconds, to scan for clients needing responses|
|http-requires-session-id||false||If this is true then client will wait after the first call to receive a session ID|
Automatic client failover is not supported for clients connecting through Netty HTTP transport.