Flow Limit (bw.application.job.flowlimit)

This property specifies the TIBCO BusinessWorks™ Container Edition 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 will contain 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 will be eight.

If the user wants to set the value for one process starter only, they can set flow limit at the component level.

If the number of jobs being created exceeds the flow limit, the engine suspends the creation of new jobs but continues executing the jobs in memory. The engine resumes creating new 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.

Note: Only set the 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 thread value of the HTTP Connector share resource to apply Flow Limit.
Docker: 
docker run -e BW_APPLICATION_JOB_FLOWLIMIT=32
-p <Host_ApplicationPortToExpose>:<Container_ApplicationPort>
<ApplicationImage>
Kubernetes: 
env:
	-name: BW_APPLICATION_JOB_FLOWLIMIT
	 value: 32
Pivotal Platform: 
env:	
	BW_LOGLEVEL: ERROR
	BW_APPLICATION_JOB_FLOWLIMIT: 32