Last updated on SEPTEMBER 23, 2013
Applies to:Oracle(R) BPEL Process Manager - Version 10.1.3.5.0 and later
Information in this document applies to any platform.
A new thread pool was introduced in BPEL 10.1.3.5 through unpublished BUG:9924311 - NEED TO PROVIDE ABILITY OF TUNING THREADPOOL FOR NONBLOKING INVOKES. The new pool called Non Blocking Invoke Pool , will process only non-blocking invoke dispatch messages. Previously, non-blocking invoke dispatch messages were processed by the invoke dispatch set, which also processes instance invocation messages. If high number of non-blocking invoke messages are created, the non-blocking invokes will compete with instance invocation messages for the invoke dispatch set threads. This could cause starvation of threads if the BPEL process performs a high number of non-blocking and synchronous invokes.
The size of the Non Blocking thread pool can be configured through the new property dspNonBlockThreads which needs to be added inside domain.xml file as follows:
<name>non blocking invoke pool</name>
<comment><![CDATA[non blocking invoke pool ]]></comment>
- Default value of dspNonBlockThreads is 3.
- The nonBlockingInvoke property must be set to TRUE at the partner link level to use the new thread
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms