Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# SPO_USERMUTEX_WAITTIME

General iProcess Engine Configuration

## Summary

This attribute defines the maximum amount of time (in milliseconds) that an iProcess Objects Server process should take to acquire a mutual exclusion lock (mutex) before processing a message if multiple SSO clients use the same user name to log in to TIBCO iProcess Engine. If the time for acquiring a user’s mutex is over the time specified by the `SPO_USERMUTEX_WAITTIME` attribute, the duration will be recorded and later reported in the `sw_warn` log.

Before TIBCO iProcess Objects Server processes a client message, it will check whether the corresponding user ID is used. If the user ID is used, the TIBCO iProcess Objects Server process will wait until the user ID is not used. When the user ID is not used, the TIBCO iProcess Objects Server process acquires the user’s mutex and then starts processing the related message. Therefore it may take a long time for TIBCO iProcess Objects Server processes to wait for acquiring a user’s mutex.

The attribute is used to identify possible performance problems with applications sharing the same user ID.

## Applies To

The attribute can be set for `SPO` processes.

## Permissible Values

The attribute value must be an integer in the range `100` to `20000`.

## Default Value

The attribute is assigned the following default value when the iProcess Engine node is installed.

Machine ID | Process | Instance | Value
0 | SPO | 0 | 200

## Notes

TIBCO iProcess Objects Server process needs to acquire the user’s mutex before processing a message.

An error is returned if the time for acquiring a user’s mutex by the iProcess Objects Server process is longer than the time you set for the process attribute. The following error message is logged in the `sw_warn` file to record the errors:

| • | If this is the first error message for the shared user name:

`The user` `user_name` `was in-use. Please check that multiple clients are not sharing the same username` `user_name` `as this can have performance impact.`

| • | If this is not the first error message for the shared user name and the time interval between the error messages is equal to or later than one hour:

`The user` `user_name` `was in-use and has been in use at time of acquisition` `number_times` `time(s), in that last` `number_time` `seconds. Please check that multiple clients are not sharing the same username (``user_name``) as this can have performance impact.`

Note: If this is not the first error message for the shared user name and the time interval between the log messages is less than an hour, no error message is logged in the `sw_warn` file.

where:

| • | `user_name` is the shared user name.

| • | `number_times` is the number of times errors are returned during the interval.

| • | `number_time` is the time interval between the returned error messages.

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.