MM IDocs got stuck

It was related to MM team the IDocs got stuck and even by manually processing the IDocs in background with program RBDAPP01, it was getting hung ( the job was running for infinite time.

We were checking the Idocs in transaction WE02 and putting 64 (Idocs ready to be processed) in "Current Status" and Message Type in "Logical Message", but the numbers were not reducing.

Upon Analysis, we came to know that there was a long running process on application server avggsqeh by user 10501828 which was indirectly holding a table lock on NRIV table.

How we got the clue ?

In t-code DB01 there were entries like HOLD and __WAIT, the application server which was holding the lock was avggsqeh but it was not relevant to our activity,"Linked Locks" button but it was showing up time and again when we clicked on anyhow we logged on to the application server and saw that there was a long running process there and we killed that after that everthing went on fine.