Thanks for the update. Please note that recommended configuration is not to run ASYNC jobs. This mode should be used in rare cases to run never-stopping jobs in background or long running jobs that take hours to complete. In all other cases SYNC jobs should be used. To allow concurrent job processing use multiple job queues and assign different groups of jobs to different queues. FYI: Every ASYNC job loads separate instance of the job engine as well as sends lots of internal communication messages to the scheduling engine. Lots of ASYNC jobs can create a lot of stress on the system. : This message is kind of a continuation of the
: thread 24x7.EXE abend that I started last week. : I think we have isolated the SNMP problem. : Here is the current scenario (with the SNMP service stopped) : Windows 2003 server, Latest version of 24x7 running
: as a service.
: I have lots of trigger based jobs that fire off when a
: file exists. : I had set these up as ASYNC and Detached.
: With this setup, I get frequent Faults in Module
: PBVM70.DLL to the desktop and event log. : Yesterday, I changed these to be ASYNC and NON detached.
: I didn't get even one error since 2:00 PM yesterday. : The same setup (ie. same application, similar environment,
: and 24x7 running jobs that are asyn / detached) works
: without problems at another customer. : I don't feel comfortable leaving these jobs as NON detached.
: Many posts to this forum recommend using the detached option
: especially for jobs that may leak memory. : Can you help explain why?
|
