Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
MnTeddy
Starting Member
2 Posts |
 Posted - 2007-10-24 : 12:42:15
|
| 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 32) 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 up to the 255, which I believe is the default?References:http://www.sql.ru/forum/actualthread.aspx?tid=173607http://thedotnet.com/nntp/224118/showpost.aspxhttp://www.unixadmintalk.com/f46/380...nt-log-150378/ |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-10-24 : 22:59:36
|
| I'll increase worker threads for sql agent first, but not to 255 of course. |
 |
|
|
|
|
|
[380] Unable to start JobManager thread