Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# General Parameters

Note | This dialog box is from the Windows TIBCO iProcess® Objects Server Configuration Utility. The configuration parameter names shown in the callouts are from the UNIX TIBCO iProcess® Objects Server configuration file. This illustration provides a cross-reference to determine which fields to change when using the configuration utility.

# NumThreads

Number of message processing threads to create. This specifies the size of the pool of threads in the TIBCO iProcess® Objects Server available for processing requests from clients. Note that this sets the TOTAL number of message processing threads, not the number per processor.

Thread information can be monitored using SWNodeInfoEx.ThreadInfos (TIBCO iProcess Objects), vANode.getThreadInfos (TIBCO iProcess Server Objects (Java)), or vANode.ThreadInfos (TIBCO iProcess Server Objects (.NET)). You can increase the number of threads if the threads are always busy, you’ve added more CPUs, you’re running short transactions, or you’ve added more users.

Note that if you change the value of this parameter, you may also need to change the value of the `MAXPOOLSIZE` parameter, which is specified in the $SWDIR`/etc/staffcfg` (UNIX) or SWDIR`\etc\staffcfg` (Windows) file. This depends on whether or not your TIBCO iProcess® Objects Server has CR 14735 implemented. If your TIBCO iProcess® Objects Server contains CR 14735, you do not need to set `MAXPOOLSIZE`. If it does not contain CR 14735, you must set `MAXPOOLSIZE` according to the information .

To ensure that you do not run out of database connections, you must make sure that the value of the `MAXPOOLSIZE` parameter in the `staffcfg` file is set to the proper value. Running out of database connections can result in the TIBCO iProcess® Objects Server failing with an ER_SYSTEM error. The value to set `MAXPOOLSIZE` depends on the number of threads being used. Therefore, to determine its value, you must use the value of the NumThreads configuration parameter. Use the following formula to determine the value to set the `MAXPOOLSIZE` parameter:

    ((NumThreads + 3) * 2) + 5

Values:

| — | 1 to 512 (Windows)

| — | 1 to 32,767 (UNIX)

## Default Value

The function for calculating the default number of message processing threads is as follows:

`Default value = NumCPUs*DFLTMAXTHREADS*Multipler`

`Multipler = MAX (1, (2.4 - LOG (NumCPUs)))`

where:

| • | `NumCPUs` is the number of processors on the system.

| • | `DFLTMAXTHREADS` is the default value, `5`.

Run the following command to display the default number of message processing threads:

| • | On Microsoft Windows

SWDIR`\bin\swentobjsv -v`

| • | On UNIX

$SWDIR`/bin/swentobjsv -v`

The default number of message processing threads is prompted as follows:

    # of CPU's  : Number_of_CPU
    # of Threads: Number_of_Threads

Note | The upper range of the allowable values for this parameter was changed a couple of times in previous versions of the TIBCO iProcess® Objects Server. The upper range for pre-version 8.1 servers is 31; for versions from 8.1 to 9.0(0.5), it is 512; for version 9.0(0.6) and later, it is 32,767. Be aware that if you are running multiple TIBCO iProcess® Objects Servers on the same machine, and they are different versions that allow a different upper range for NumThreads, TIBCO iProcess® Objects Server Configuration Utility will allow you to set the upper limit up to 32,767. Ensure that you specify only the number of threads allowed for the version of server you are configuring.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2025. Cloud Software Group, Inc. All Rights Reserved.