A linux system is intermittently slow due to heavy load, and could become unresponsive when archive files such as .jar are scanned by the On-Access Scanner (OAS).

System dump analysis shows many application processes are waiting for the completion of the OAS, as seen in the following example stack trace:

PID: 28675 TASK: ffff88013c5f0ae0 CPU:2 COMMAND: "sm_sender"
#1 [ffff88013b193a40] doScan at ffffffffa0281341 [linuxshield]
#2 [ffff88013b193af0] SC_doScan at ffffffffa0281d6b [linuxshield]
#3 [ffff88013b193b50] openHook at ffffffffa27c773 [linuxshield]
#4 [ffff88013b193b90] invokeCallbacks at ffffffffa025bb25 [lshook]
#5 [ffff88013b193c80] fileOpenHook at ffffffffa025d387 [lshook]
#11 [ffff88013b193f30] custom_file_open at ffffffffa025d660 [lshook]

System event logs from the Web UI or ePolicy Orchestrator server show some .jar files timed out during OAS. The following is an example of message seen in the event log:

"Timeout scanning /usr/java/jdk1.7.0_67/jre/lib/rt.jar for user root using /usr/java/jdk1.7.0_67/bin/java"