Environment
NetIQ Access Manager 3.2
NetIQ Access Manager 3.2 Access Gateway Appliance
NetIQ Access Manager 3.2 Access Gateway Appliance
Situation
Access Manager 3.2 setup and working fine. All users can access protected resources behind the Access Gateway (AG) after having authenticated successfully at the Identity (IDP) Server. After about 4 or 5 days, some users would start complaining about delays rendering application level pages viewed through the AG, which typically became worse at peak load times during the day. Restarting the Access Gateway proxy (/etc/init.d/novell-apache2 restart) would solve the problem for a few days.
Resolution
Edit the /etc/opt/novell/ag/mod_disk_cache_monitor.conf file on the AG and comment out the line with 'LoadModule disk_cache_monitor_module /opt/novell/ag/lib/mod_disk_cache_monitor.so'
This prevents the NetIQ disk caching monitoring that provides some caching stats to the Admin Console, but has no impact whatsoever on functionality. The overhead with the disk cache monitoring caused delays of up to 2 minutes on the AG before sending the object back to the browser, causing the delays visible at the browser level.
This prevents the NetIQ disk caching monitoring that provides some caching stats to the Admin Console, but has no impact whatsoever on functionality. The overhead with the disk cache monitoring caused delays of up to 2 minutes on the AG before sending the object back to the browser, causing the delays visible at the browser level.