![]() ![]() Once you’ve done this, you can then use report RSXMB_CHECK_MSG_QUEUE to restore the messaging system integrity by resetting the original message status to cancel it. Instead, in this exceptional case, you can delete the message in SMQ2. SAP notes state that you should NEVER delete messages directly from SMQ1 or SMQ2 as this leaves the messaging system in an inconsistent state. You may also be blowing the ICM http buffer, visible in the SMICM log file:īut, you can’t cancel the message in SXMB_MONI, as it is still scheduled on the QUEUE (“still scheduled in queue XBTS*”): The message is visible in transaction SMQ2 (inbound queue) for a few hours/days/months:Īnd it’s consuming significant resources, visible in SM50: (This solution is based on SAP note 688147). Scenario: You have a large message that is stuck in the INBOUND (XBTS*) queue of an integration server (maybe an ABAP proxy).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |