Problem with Dispatcher

[Former Member]

Hi,

in my other thread [|] i had the problem, that the provisioning framework tasks dont work at all. change own data, create new business role or create identity are working. not working tasks for example are "delete identity" or "lock identity". the "write hcm employee to sap master" doesnt work too.

Testing the dispatcher shows this:

[18.01.2011 10:08:36-359] - MxDispatcher:All locked. Sleeping ...

[18.01.2011 10:08:39-328] - MxDispatcher:Executing 'getWaitingjobs'

[18.01.2011 10:08:39-390] - MxDispatcher:[Executions ] - none:

[18.01.2011 10:08:41-359] - MxDispatcher:Executing clear old semas from IFCheck

[18.01.2011 10:08:41-609] - MxDispatcher:Executing set sema from IFCheck

[18.01.2011 10:08:41-609] - MxDispatcher:Policy type is :1

Get Counts String:select actiontype,count(state) as count from mxp_provision with (nolock) where State IN (1, 2, 23, 24, 25, 26) and exectime<getdate() group by actiontype

[18.01.2011 10:08:41-750] - MxDispatcher:Setting visited[0] to 1

[18.01.2011 10:08:41-750] - MxDispatcher:Setting visited[1] to 1

[18.01.2011 10:08:41-750] - MxDispatcher:Setting visited[2] to 1

[18.01.2011 10:08:41-750] - MxDispatcher:Setting visited[3] to 1

[18.01.2011 10:08:41-750] - MxDispatcher:Setting visited[4] to 1

[18.01.2011 10:08:41-750] - MxDispatcher:Picked up tasktype: -1

[18.01.2011 10:08:41-765] - MxDispatcher:All locked. Sleeping ...

Any suggestions why my dispatcher is not running correctly?

Bg,

Philip

[Former Member]

Hi Philip,

have you recreated the dispatcher scripts?

The dispatchers are konfigured to run provisioning jobs and other jobs?

Kind regards,

Achim

[Former Member]

Hi Achim,

i recreated them several times.

We got 1 dispatcher. In "Jobs" --> "Run jobs" all flags are acitvated.

In my opinion it should be a problem with the DB, but i can´t identify it.

Br,

Philip

[former_member2987]

Philip,

Have you examined the dispatcher script and prop files (I'm assuming you are running a Windows dispatcher, if it's a *NIX install it would be a .sh file)

There's some comments in there about changing logging levels and possibily some troubleshooting.

Off the top of my head I'd suggest (in no particular order)

DSE_HOME location

JAVAHOME location

SQLJDBC connection string (mxmc_rt uses this)

Usually the issue is due to the Java conifiguration. Also check what version of Java is being used. It should be 32 Bit and at least version 1.5 (1.4 is needed for NetWeaver) Both versions can be on the same system.

HTH,

Matt

[Former Member]

Hi Matt,

it is a windows dispatcher, youre right.

In .prop file theres a some lines about that

LOGLEVEL=4 (Log level for DSE runtime engine, 4 = Extended)

MXDISPATCHER_LOGTYPE=3 ( 2 = console only)

JAVA version on my client is 1.4.2_19 (32 Bit)

JAVA version on (windows 64 Bit) server is 1.4.2_17 (64 Bit)

On the client i tried out 1.6.0_07 5 minutes ago but same error.

Br,

Philip

[former_member2987]

Hello Philip,

JAVA version on (windows 64 Bit) server is 1.4.2_17 (64 Bit)

Is your dispatcher running on this server? If so, install a 32bit Java 1.5 or later and try the dispatcher against that.

To do this go to the IDM MMC console and select Options, then JAVA. Select the JAVA.EXE that you just installed.

See if that helps you out.

Matt

[Former Member]

Hi Matt,

the dispatcher is running on my 32bit win xp client.

So i think thats not the problem?

Br,

Philip

[former_member2987]

Philip,

You need a dispatcher pointing to a 32 bit JAVA, with a version 1.5 or above. It does not need to be on your XP machine, but can be for testing...

Matt

[Former Member]

Hi Matt,

i changed in ic below tools --> options --> java path to "C:ProgrammeJavajre1.6.0_05 injava.exe" (jvm changed automatically). Recreated the scripts and tested the dispatcher again, Does not make an difference. It´s the same error.

Or do you mean that i have to install a 32bit java on the server?

Br,

Philip

[Former Member]

Hi,

have you tried deleting the whole provisioning queue either by calling the appropriate task (available in the job wizard) or by calling "DELETE FROM mxp_provision"?

This week we had strange error messages that were caused by full database tablespaces. You should also verify that you have enough diskspace available for your database tables.

Best regards

Holger

[Former Member]

Hi Holger,

first i tried to delete with the job. But it didn´t make a difference. It did not clean the provisioning queue.

Then i deleted entires with "DELETE FROM mxp_provision" (like you told me). It worked and the queue was of course empty. When i start this jobs/tasks again theres the same problem.

I think it should not be the tablespaces. Yesterday i cleaned the hole identity store and just reloaded a part of the data, that have been in is before deleting but i request my admin.

In my opinion it is a technical problem with the dispatcher which does not work correct. Theres an open message to SAP now. Maybe they can help.

Br,

Philip

[former_member2987]

Philip,

The 32 bit JAVA is needed on any manchine runniing a SAP IDM dispatcher.

Matt

[Former Member]

Hi Matt,

i just got 1 dispatcher running. This one is running on my client.

Br,

Philip

[Former Member]

Did you solve the issue? I am experiencing similar behaviour.

[Former Member]

Hi,

i didn´t solve it yet. Whats your exact problem. Contact me by email in Business Card

Bg,

Philip

[Former Member]

Solved!

Description:

Jobs don´t run and still hang in provisionqueue.

Testing the dispatcher shows: policy type is :1

Solution:

"Dispatchers" --> untick "Dispatcher task execution priority __ Enable (global)"