Custom Properties for the HTTP Palette

In some situations, you may want to alter the configuration of the HTTP server that receives incoming HTTP requests for ActiveMatrix BusinessWorks. You can configure the following custom properties:

Property

Tomcat or HTTPComponent

Description

bw.plugin.http.server.minProcessors

Tomcat

The minimum number of threads available for incoming HTTP requests. The HTTP server creates the number of threads specified by this paramter when it starts up. The default value of this property is 10.

bw.plugin.http.server.maxProcessors

Tomcat

The maximum number of threads available for incoming HTTP requests. The HTTP server does not create more than the number of threads specified by this parameter. The default value of this property is 75.

bw.plugin.http.server.maxSpareProcessors Tomcat The maximum number of unused request processing threads that can exist until the thread pool starts stopping the unnecessary threads. The default maximum number of spare threads is 50.
bw.plugin.http.server.acceptCount Tomcat The maximum queue size for incoming requests. Incoming requests that are not handled by available threads are placed on the queue until they can be processed. If the queue is full, new incoming requests are refused with an error. The default value of this property is 100.
bw.plugin.http.server.restrictIPAddresses Both

A comma-separated list of regular expression patterns that is compared with the remote client’s IP address before accepting or rejecting requests from the client. The remote IP address of the client must not match for any request from this client to be accepted.

bw.plugin.http.server.serverType Both The type of server to be used for the HTTP connection resource. Two server types are available: Tomcat and HTTP Component. The default value of this property is Tomcat.
bw.plugin.http.server.httpcomponents.workerThread HTTPComponent The maximum number of web server threads available to handle HTTP requests for the HTTPComponents server type. The default value of this property is 50.
bw.plugin.http.server.restrictHttpMethods Tomcat Specific HTTP methods can be disabled. By default, none of the HTTP methods are restricted by the server. You can specify a comma-separated list of methods that are to be restricted. These restrictions are then applicable to all resources accessed on this server, for all roles. You cannot disable methods selectively for a particular service or for a particular server.

Note: If the same IP address is allowed and restricted, the restriction overrides the allowance and restricts the IP address.

If you have a large number of incoming requests, you may want to change the values of these properties to handle more incoming requests concurrently.

For more information about setting custom engine properties, see TIBCO ActiveMatrix BusinessWorks™ Administration.

Note: When a client sends a request that cannot be processed because no threads are available, ActiveMatrix BusinessWorks returns a ConnectionRefused exception to the client. The HTTP Receiver uses the minProcessors/maxProcessors properties to control the flow of incoming HTTP requests. If you set the Flow Limit deployment property for a process definition with the HTTP Receiver process starter, maxProcessors is set to <flowLimitValue>-1 and minProcessors is set to <maxProcessorValue>/2. Therefore, the Flow Limit value can not be reached because the maxProcessors property prevents new requests from being accepted before the Flow Limit value is reached.