Skip to Content
0

IdM queue is not being processed

Feb 20, 2017 at 05:44 AM

188

avatar image

Hi,

On IdM 8, SP3, Oracle DB and Unix

I am having an issue where entries in the provisioning queue are not being processed.

On the create user form, I have a simple process on submit. The process task goes into the provisioning queue, but it is not being picked up by the dispatcher.

There is nothing in the dispatcher log to indicate any issues - or in any other log for that matter.

The system is a development system, with very little data, so it is not due to any other stuck processes/dependencies.

The tasks are eventually processed, but it takes any where up to 5 hours before it happens, which is obviously not acceptable.

Any help would be much appreciated!

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Matt Pollicove
Feb 20, 2017 at 08:16 PM
0

Hi Henrik,

Can you see anything in the system log? Also can you confirm that the job is enabled, and the dispatcher is assigned and running?

Gotta clear the basics first :)

Regards,

Matt

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Matt,

Yes, the dispatchers are running and assigned - And the jobs are picked up eventually - but with several hours of delay.

Yes, the jobs are also enabled.

In the system log, there is an entry saying: "Job has not been requested. Rescheduling". This appeared several hours after I kicked off the job, so looks like timeout.

There are also multiple entries with: "1 stale semaphores released"

Strange thing is that sometimes the job will kick off immediately, and other times it takes hours.

There is no other processes running for IdM - no provisioning, no housekeeping etc - I don't even have any repositories set up yet, so data volume is very very low.

/henrik

0

Interesting. Can you please verify that all components are on SP3? Also it might be a good idea to post the contents of your dispatcher files.

Matt

0
Henrik Madsen Feb 24, 2017 at 01:03 AM
0

It turned out that the java engine was wrong... It was set up using the standard java 1.7 runtime. After updating/changing to SAPJVM it seems to be resolved. I will come back if I see this again.

Share
10 |10000 characters needed characters left characters exceeded
Matt Pollicove
Feb 24, 2017 at 01:08 PM
0

Hi Henrik, what version of SAP JVM are you using. Generally speaking this should not make a difference, so I always like to know when it does :)

Matt

Share
10 |10000 characters needed characters left characters exceeded