APAR status
Closed as program error.
Error description
The queue manager has been configured to use LDAP for user authentication and/or authorization. If the LDAP server is not reachable on the network, or is going slowly, then this will be visible in the times taken by the MQ API calls. For example, MQCONN can suffer if the queue manager is configured to perform authentication on the user's credentials, and the validation with the LDAP server is slow. Also, MQOPEN and MQPUT1 can suffer if the LDAP search for users/groups is slow. For clarity in such cases, a warning error message will be added to the QM error logs.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users of MQ who use an LDAP server as their user repository Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: No feedback was given when a customer's LDAP server was running slowly, or long times were taken to connect. A slow connection blocks other MQ threads waiting to authenticate connection requests as they are also waiting for access to the LDAP connection. It is useful to see a warning in the queue manager error logs to notify the administrator that this is happening.
Problem conclusion
When making calls to the LDAP server, MQ's Object Authority Manager (OAM) component will take a note of the time before and after the call. If this time is greater than the threshold 10 seconds, by default, alterable in qm.ini then the OAM will write an AMQ5544 error message to the QM error log. If the administrator wants to alter this threshold, then the tuning parameter name is OAMLdapResponseWarningTime in the TuningParameters stanza of the qm.ini file. The minimum valid value is 0, which switches off the mechanism. A value greater than 0 will be used as the number of seconds to use as the threshold. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.1 LTS 9.1.0.15 v9.2 LTS 9.2.0.10 v9.3 LTS 9.3.0.5 v9.x CD 9.3.3 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT35455
Reported component name
IBM MQ BASE MP
Reported component ID
5724H7271
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-01-08
Closed date
2023-02-22
Last modified date
2023-02-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
IBM MQ BASE MP
Fixed component ID
5724H7271
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 February 2023