Reasons for EH locking

[Affan_alavi]

Hi,

Does anyone know the reasons why EH are blocked in EM, apart from multiple messages arriving to the handler at the same time.

I have encountering several instances where a message is not assigned to the handler and it shows that the handler is locked. however there is no other message posted on the handler previously around the same time.

Strangely even after running the /SAPTRX/PROCESS_LOCKED_EHS, the handler still shows as being locked, even though the program shows that the handler has been unlocked and messages processed.

Has anyone else encountered this issue, and is there a resolution for this?

[former_member190756 · Accepted solution]

Hi Affan,

EHs are locked because of messages processing and if there are updates to the Eh from the corresponding Application object.

For 1) Check table /SAPTRX/LOCKEDEH there you find the message guids and EH guid.

For 2) Check table /SAPTRX/RP_AOID. Here you find the EH guid and the info about the application object taht tried an update.

-> to reprocess these entries report /SAPTRX/R_REPOST_AI_LOGS must be scheduled

Which scenario you are running? Especially using PTA scenario locking situations due to hierarchies can cause that EHs locked a longer time.

Best regards,

Steffen

[former_member186607 · Accepted solution]

Hi Affan,

EHs can also be locked if EE monitor report is running in background and updating one or more EE status of an EH.

Best regards, Daniel

[Former Member]

Hi Affan,

There could be different reasons:

1. If the event handler doesn't exist for event message then it will be in unprocessed stage.

2. If tracking ID doesn't not exist for an event handler, then it will be in unprocessed stage.

3. If the event handler is inactive when event message is posted then it will be in unprocessed stage.

4. If the event handler is archived when event message is posted then it will be in unprocessed stage.

5. If the event handler is deleted when event message is posted then it will be in unprocessed stage.

How to find a root cause?

1. Go to table /SAPTRX/LOCKEDEH and take some 10 EH_GUID id's and MSG_GUID and check different stages of posting events when it is occurring mostly.

2. Is this blocked event message happen only for few particular events or for all events?

3. Go to table /SAPTRX/EVM_HDR and take Tracking ID and Code set, now check in table /SAPTRX/EH_HDR whether EH exists.

Regards

GGOPII

[Former Member]

Hi Affan,

Can you check these OSS notes?

2060023 - Dump DBIF_RSQL_INVALID_RSQL when running /SAPTRX/PROCESS_LOCKED_EHS

1349175 - Hierarchy is not build if any EH is locked

1676646 - Hierarchy is not build if any EH is locked (2)

1945425 - Long runtime during processing of Event Messages for previously locked Event Handler

1867827 - Missing processing of event messages

Regards

GGOPII