Set some jobs to run detached and then check in the Task Manager (Processes tab page) which process(s) consumes the most CPU. Sort processes by name and watch for processes with 24x7.exe name. When jobs are launched new instances of 24x7.exe will appear in the process list. Check if these new instances consume a lot of CPU. If they do, the problem is most likely in jobs of in VBScript installation. If they don't, the problem is most likely in 24x7 configuration. Check which options are enabled in Tools/Options menu Log page. If you have tracing enabled, disable it. If you have HTML Status reports enabled, make sure you have the latest version of 24x7 and HTMLGen.exe. If you have log files of HTML reports generated on a network drive check you don't have network access latency issues. If you find that detached jobs : We are having jobs started by 24x7 but standing still afterwards.
: On that moment almost 100% CPU is used by 24x7
: Other (asynchronous!) jobs are blocked on that moment. : We are only using VBscript to start the 24x7 jobs.
: Only few jobs run at the same time.
: There are about 50 asynchronous jobs.
: All jobs run asynchrone in the same default queue.
: We do not have remote agents.
: We do not use semaphore files.
: In fact the implemantation is rather simple. : Inside the VB script the job is started and result monitored by: RunAndWait
: start_string, "", 0, process_id : ProcessGetExitCode exit_code : What could be the case?
|
