Flow Limit

This property specifies the ActiveMatrix BusinessWorks application's process starters or service bindings flow limit value. There is no default value.

Flow limit is useful when the engine needs to be throttled, as the property specifies the maximum number of jobs that can be started before suspending the process starter. This ensures that the incoming requests do not overwhelm the engine performance and the CPU and memory is preserved.

If the flow limit is set to a particular value at the application level, each of its process starters contains the same value. For example, if you set the flow limit at application level as eight and the application has two process starters, the flow limit for each of these process starters is eight.

If you want to set the value for one process starter only, set the flow limit at the component level by using the environment variable, BW_COMPONENT_JOB_FLOWLIMIT.

Note: For component level, use only the BW_COMPONENT_JOB_FLOWLIMIT environment variable.

If the number of jobs being created exceeds the flow limit, the engine suspends the creation of new jobs but continues running the jobs in memory. The engine resumes creating jobs when sufficient resources are available. There is no default flow limit value and it is not enforced by the engine unless the flow limit property is specified for an application.

This value can be set either in the AppNode config.ini file or the Admin UI. In the Admin UI, this property is required to be created as a user-defined property.

Note:
  • Only set the bw.application.job.flowlimit property for applications using non-HTTP-based transports, for example, JMS. If applications are using HTTP-based transports, ensure you set the Max QTP Threads value of the HTTP Connector shared resource to apply the Flow limit.
  • To push a new property value to runtime, stop the application, update this property in the AppNode or AppSpace config.ini file, and restart the application.

    You can update the flow limit without restarting an application using the Admin UI and the REST API. For more information, see "Engine and Job Tuning" in TIBCO BusinessWorks™ Container Edition Administration.

  • Property = bw.application.job.flowlimit.<UsersBWApplicationName> [.<UsersBWApplicationVersion>][.<UsersBWComponentName>]

    The parameters enclosed in square brackets [ ] are optional. For example: [<UsersBWComponentName>]

  • Parameter location in the Admin UI = AppNodes > Select AppNode > Configure > User Defined > Create
  • Default Value = No default value

Note: Get the logs for the component states such as Start, Stop, and Resume based on whether the Flowlimit is breached or complied by enabling the core runtime logger com.tibco.bw.core at INFO level.