Return
-
Title
High CPU usage for vasd on db2 servers when one account is doing authentication. DB2 slowness. vasd stops resolving ids. SCP batch no longer working. FTP job fails. -
Description
High CPU usage for vasd on db2 servers. DB2 slowness when one account is doing the authentication.
Single service account doing batch authentication begins to fail.
The vasd daemon stops resolving ids. SCP batch no longer working using one account to do the authentication.
The auth daemon is gradually increasing in size and consuming more processor time when an account is performing a large number of very rapid authentications. The cache should be getting cleaned up but does not resulting in increased usage. -
Cause
Product Defect 1455213:
vasd: Better handle constant authentications from the same account. Less CPU
usage. Also remove changes for Bug 26341, on AIX LAM won't automaticallyhandle processes starting with db2* as try_disauth_first. The current 4.1 codewill handle repeated auths faster. Fixed in 4.1.0.21790 -
Resolution
STATUS: Fixed.RESOLUTION:
Upgrade to new version of the product. We recommend that you use the latest maintenance fix version. Please go to https://support.oneidentity.com/authentication-services/download-new-releases to download the latest software.
-
Change Request
455213