CIF queues stay to be processed for days in RUNNING status due to locking conflict

[dmitriikarpov976]

Hello guys,

Can you help me with the problem of stopping incoming CIF queues in APO? They continue to be processed in the "RUNNING" status for several days due to a lock conflict. At the same time, it is not clear which table is blocked for access, since in this status the queue does not have debugging and in SM12 there is no entry in the blocking list with the LocID that appears in the detailed message at the bottom. The lock conflict message itself is yellow and suggests automatic resolution, but it doesn't. The stuck queue collects a bunch of waiting followers and therefore I have nothing to do apart from manual removal of it to restore data transfer.

In enclosed pictures the queue with ExtID 0A1DCDCB44C0661D7E060000 at the top of the list of queues has a log entry with lock conflict message and will never be proccessed. 

What is a way to avoid or automatically fix this lock conflict?

[Smax]

Hi,

If the queue remain in running status you can reset the status in order to be able to restart the queues.
In case you get this message the the queues that the queue is registered then you need to "unlock" the queues in via the unlock icon in SMQ2.

The queue income can not so easily, you can deregister in SMQR based on the queue name CFPLO123456 and example for a specific order. Then the queue will not be picked up by the inbound scheduler.

[dmitriikarpov976]

Hi Smax,

Yes, it works. But it is a burden to unwide these queues every morning. I am looking for a solution for spotting and fixing the root cause of this blockage or pushing the queues through automatically. They recommended RSQIWKEX or RCTRFCIC reports. Not sure which is better. And how to determine the root cause of the stucking if debugg is not available in running status?

Any idea?