Environment
NetIQ Access Manager 3.1
NetIQ Access Manager 3.1 Support Pack 5 applied
NetIQ Access Manager 3.1 Access Gateway Service on Linux
NetIQ Access Manager 3.1 Support Pack 5 applied
NetIQ Access Manager 3.1 Access Gateway Service on Linux
Situation
Access Manager 3.1 SP5 installed and working successfully. The Access Gateway Service (AGS) is used to protect back end web servers. Despite everything working perfectly, the Administrator for the AGS was notified that the file system was running out of disk space. Following some research, it was noted that the catalina log file had grown to more than 4GB, despite logging to that server being disabled (configurable in the IDP -> Logging setup of iManager).
Almost every single entry in the log file was the same ie. there were 10000s of lines with the message:
"RequestChannel: TimeoutException"
Almost every single entry in the log file was the same ie. there were 10000s of lines with the message:
"RequestChannel: TimeoutException"
Resolution
Make sure that the novell-apache2 service is started AFTER the novell-activemq services by either
a) restarting novell-apache2 after all services have restarted or
b) adding a small change to the novell-apache2 script to introduce a delay
start*)
echo -n "Starting Novell Gateway Service..."
sleep 1 // Add this line
The error is reported because the apache proxy service cannot talk to activeMQ service. When you manually start Apache after ActiveMQ and the problem goes away, it is because ActiveMQ is fully initialised when Apache loaded and both services could communicate. The tip is to delay the loading of Apache until ActiveMQ is fully initialised.
The issue is not seeing with NAM 3.2.
a) restarting novell-apache2 after all services have restarted or
b) adding a small change to the novell-apache2 script to introduce a delay
start*)
echo -n "Starting Novell Gateway Service..."
sleep 1 // Add this line
The error is reported because the apache proxy service cannot talk to activeMQ service. When you manually start Apache after ActiveMQ and the problem goes away, it is because ActiveMQ is fully initialised when Apache loaded and both services could communicate. The tip is to delay the loading of Apache until ActiveMQ is fully initialised.
The issue is not seeing with NAM 3.2.