Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 6 Administering Process Attributes : General iProcess Engine Configuration : SPO_USERMUTEX_WAITTIME

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 for a mutual exclusion lock (mutex) before processing a message if multiple SSO clients use the same user name to log on 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, 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 begin processing the related message. Therefore it may take a long time for TIBCO iProcess Objects Server processesto wait for acuiring 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.
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 sw_warn file to record the errors:
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.
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.
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.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved