cancel
Showing results for 
Search instead for 
Did you mean: 

IDM - Some of the Dispatchers are not running

Former Member
0 Kudos

Hi ALL

For our IDM system  we have high Provisioning Queue and Dispatchers locked  (Some of the dispatchers are not running .) Below is some information:

--------------------------------------------------------------------------------------------------------------------------------------------------------

[09.08.2013 06:12:43-337] - MxDispatcher:Picked:0 is LOCKED

[09.08.2013 06:12:43-339] - MxDispatcher:Picked up tasktype: -1

[09.08.2013 06:12:43-384] - MxDispatcher:All locked. Sleeping ...

[09.08.2013 06:12:47-308] - MxDispatcher:RUNTIME COUNT MODE: 0

[09.08.2013 06:12:47-308] - MxDispatcher:This disp has started: 0 runtimes

[09.08.2013 06:12:47-308] - MxDispatcher:Executing 'getWaitingjobs'

[09.08.2013 06:12:48-385] - MxDispatcher:Executing clear old semas from IFCheck

[09.08.2013 06:12:50-962] - MxDispatcher:[Executions ]  - none:

[09.08.2013 06:12:51-071] - MxDispatcher:Executing set sema from IFCheck

[09.08.2013 06:12:51-071] - MxDispatcher:Policy type is :1

Get Counts String:select actiontype,count(state) as count from mxp_provision wit

h (nolock) where State IN (1, 2, 23, 24, 25, 26) and exectime<getdate() group by

actiontype

[09.08.2013 06:12:52-654] - MxDispatcher:Setting visited[1] to 1

[09.08.2013 06:12:52-654] - MxDispatcher:Setting visited[3] to 1

[09.08.2013 06:12:52-655] - MxDispatcher:Setting visited[4] to 1

[09.08.2013 06:12:52-655] - MxDispatcher:Picked:0

[09.08.2013 06:12:52-681] - MxDispatcher:(441) semaphore already set

[09.08.2013 06:12:52-712] - MxDispatcher:Picked:0 is LOCKED

[09.08.2013 06:12:52-712] - MxDispatcher:Picked:2

[09.08.2013 06:12:52-729] - MxDispatcher:(443) semaphore already set

[09.08.2013 06:12:52-747] - MxDispatcher:Picked:2 is LOCKED

[09.08.2013 06:12:52-747] - MxDispatcher:Picked up tasktype: -1

[09.08.2013 06:12:52-784] - MxDispatcher:All locked. Sleeping ...

---------------------------------------------------------------------------------------------------------------------------------------------------------------

We have restarted all dispatchers and restarted the whole system .

Please can you let us know if you have any idea , how to resolve this issue. It would be agreat help if you reply ASAP.

Thanks in Advance!!!

Accepted Solutions (0)

Answers (2)

Answers (2)

ChrisPS
Contributor
0 Kudos

Hello Prasanna,

                        can you let us know which version of IdM including SP is used and how many dispatchers are configured and how the policy is setup for these (e.g. all set to handle provisioning). There is some difference between 7.2 SP6 and SP7 onwards in the way the dispatcher management is setup.

Thanks,

Chris

bxiv
Active Contributor
0 Kudos

What ID was assigned to the Windows service for the dispatcher?

It should look like "MxDispatcher_customname", and I chose to use the <SID>adm account that runs the Java application server for IDM.