RSA Federated Identity Manager (FIM) 2.0 shows very high memory usage when under load using DSig
Originally Published: 2004-05-18
Article Number
Applies To
Digital Signing
Issue
Cause
Resolution
Disable signing of the Assertion on the AP and your load tests should show more favorable memory usage.
Related Articles
Symptoms of a failed memory module on RSA SecurID hardware appliance Number of Views Risk Engine Considerations for Risk-Based Authentication Number of Views RSA Identity Governance & Lifecycle aveksaServer.log repeatedly shows "updateServerAgentUptimeDate: Setting new uptime for… Number of Views High CPU Utilization due to misconfiguration of Manual Activities Workflow in RSA Governance & Lifecycle Number of Views Installing patch 2 on Authentication Manager 8.6 p1 fails with an error "Cannot allocate memory" Number of Views
Trending Articles
RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide "HTTP response error! Response code=401" when starting RSA Identity Governance and Lifecycle Access Fulfillment Express (A…
Don't see what you're looking for?
