Results 1 to 1 of 1
  1. #1
    Join Date
    Mar 2003
    Location
    The Bottom of The Barrel
    Posts
    6,102
    Provided Answers: 1

    Unanswered: [380] Unable to start JobManager thread

    I am intermittently receiving the following error when attempting to start jobs in my sql agent logs, note that no other errors occur in conjunction:

    "[380] Unable to start JobManager thread"



    My google-fu tells me that this happens when max worker threads has been exceeded, or physical hardware limits have been hit.

    I have two questions.

    1. Is the best way to go about confirming whether I'm maxing out the number of worker threads (more likely IMO, currently set to 255) or pegging physical resource limits to use the Sql server counters against physical counters in perfmon?

    2. My understanding is that if I limit the number of threads available in the offending subsystem (tsql in this case), that this is an acceptable solution because it makes it difficult for concurrent tsql processes to peg the max allowed worker thread threshold. The other solution is to increase the number of max worker threads.

    Am I on the right track here? If so, is there any significant danger to bumping max number of worker threads above 255, which I believe is the default?


    References:
    http://www.sql.ru/forum/actualthread.aspx?tid=173607
    http://thedotnet.com/nntp/224118/showpost.aspx
    http://www.unixadmintalk.com/f46/380...nt-log-150378/
    Last edited by Teddy; 10-26-07 at 11:11.
    oh yeah... documentation... I have heard of that.

    *** What Do You Want In The MS Access Forum? ***

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •