Access Manger MUX Pool Exhausted error message
Originally Published: 2012-11-01
Last Modified: 2023-10-06
Article Number
Applies To
Issue
The aserver logs a very large volume of messages of this type:
sequence_number=33788,remote_client=aserver1,2012-08-24 04:00:03:886 CDT,messageID=15,result_code=0,result_action=MUX Event,result_reason=MUX Pool Exhausted
Resolution
This hotfix introduces two new configuration parameters that may be used to configure the frequency an threshold for mux log messages. The new mux log messages also indicate the queue length.
Here is an example message:
sequence_number=3,2012-10-12 15:18:22:812 IST,messageID=15,result_code=0,result_action=MUX Event,result_reason=MUX Pool Exhausted,mux_queue_length=52,mux_request_wait_count=430
You must add the following parameters to your aserver.conf file.
# Optional. This optional parameter specifies the wait time threshold
# for a request in the queue after which a MUX_POOL_EXHAUSTED error event
# is triggered for each request. The frequency at the will the MUX_POOL_EXHAUSTED
# message is logged depends on the value of cleartrust.aserver.mux.msg_log_threshold
#
# Allowed Values:
# Any positive integer that represents the number of milli seconds.
# A value of zero won't trigger the MUX_POOL_EXHAUSTED event.
#
# Default Value:
# 5000
#
#cleartrust.aserver.mux.request_wait_threshold=5000
# Optional. This optional parameter specifies the time
# interval between each MUX_POOL_EXHAUSTED error event.
#
# Allowed Values:
# Any positive integer that represents the number of milli seconds.
# A value of zero won't trigger the MUX_POOL_EXHAUSTED event.
#
# Default Value:
# 5000
#
#cleartrust.aserver.mux.msg_log_threshold=5000
If no logging is required change the values to 0. There can be some performance overhead when using mux pool logging. If you require warning about mux pool performance set the values high enough that log messages are only generated in exceptional circumstances.
To tune the mux pool increase the value of cleartrust.aserver.thread_pool_size setting until the mux_request_wait_count is acceptable.
For real time tuning of the mux pool it is more efficient to use SNMP.
Workaround
New functionality was added in SP4 that introduced a log message for mux pool tuning. This message is generated whenever an incoming request comes in and is not immediately passed to the mux pool thread. For many customers it is normal for this to occur. Items that are queued are serviced by the next free mux pool thread. What is more important is the length of the mux queue and the maximum time to clear events from the queue.
Related Articles
Data Purging stuck "in Progress" in "Step 7/12 Purging Workflow Custom Tasks" in RSA Identity Governance & Lifecycle 52Number of Views RSA Access Manger error message 'This stream has been closed'. 96Number of Views RSA Identity Governance & Lifecycle unification fails with ORA-30926: unable to get a stable set of rows in the source tab… 344Number of Views Manage the Node Secret 233Number of Views Quick Setup Guide - RSA iShield Key 2 HOTP OTP 364Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities RSA Authentication Manager Patch Updates RSA Authentication Manager Upgrade Process
Don't see what you're looking for?