Bojensen Blogs

Info: AifResourceLock Table « Santosh Ramamurthy AX Blog


When debugging X++ code the developer tends to press (Shift+F5) to stop the execution of program. This symbolizes that either the issue is figured out (or) may be he needs more data to understand the issue which is going on.

This type of debugging usually has a side effect on AIF.


ü While processing inbound message, the AifGatewayReceiveService locks the channel to ensure that only one process can access a message at any given time. These locks also ensure that the messages are processed in FIFO or parallel order on the basis of the channel and endpoint. As a result when the execution is terminated after the following stack ClassesAifGatewayReceiveServiceprocessInboundMessages – Line 19

So during inbound operation a record gets inserted into the Resource Lock table based on the following cluster index

· Channel Id

· AifResourceType – Channel, Conversation, Endpoint or Message

· AifResourceLockType – Gateway or Document Service

This doesn’t allow to process any further Xml until record in AifResourceLock table is deleted. Only if the message is cleared/deleted the adapter will start processing it successfully.

Info: AifResourceLock Table « Santosh Ramamurthy AX Blog

Comments are closed.