Question
aaseya it services pvt.ltd
SA
Last activity: 27 Sep 2019 6:16 EDT
WorkObjects directly falling into the broken process on queuing the items in queue processor
WorkObjects directly falling into the broken process on queuing the items in queue processor.
***Edited by Moderator: Lochan to update platform capability tags***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
FR
Hello,
Can we get more details, your Pega version running, any broken instance details, a tracer file, any log files about this issue
aaseya it services pvt.ltd
SA
version 8.2.1 Personal Edition I am not able to trace anything because tracer is not running
aaseya it services pvt.ltd
SA
I am getting error as lock is already obtained by another user
Pegasystems Inc.
IN
Hi Mounika,
Thanks for posting the query.
You can trace the queue processor activity in the queue processors tile which can be accessed in the admin studio to find the reason why the queue was moved to the broken queue..
aaseya it services pvt.ltd
SA
I tried already but not able to trace anything Please refer the document for details
Pegasystems Inc.
FR
So you have the response to your question. Instance cannot be processed because another user has the lock. It could be perfectly normal message.
aaseya it services pvt.ltd
SA
Yes administrator is running the case and he is not closing the work object so it is going into broken process when he closes the object work object is processing by requeuing in the queue processor. How to solve this issue even though work object is in open i want to process the object in the queue processor
Pegasystems Inc.
FR
Well,
You will have to wait for the system to unlock it. I think the default lock time is 2 hours. Maybe you can force the system to release the lock but it will have to be custom activities in play.
CPF
SG
Is it okay if you change the locking mode?
if Yes, could your try with optimistic locking mode.