Symptom
After a system refresh, the inbound bgRFC locks BGRFC_I_SERVER_REGISTRATION are missing in SM12 and there are ASSERTION_FAILED dumps in ST22.
The short dumps are similar to the one below:
Category ABAP Programming Error
Runtime Errors ASSERTION_FAILED
ABAP Program CL_BGRFC_DB_HELPER============CP
Application Component BC-MID-RFC-BG
Date and Time 20/06/2024 20:40:56
----------------------------------------------------------------------------------------------------
|Information on where terminated |
| Termination occurred in the ABAP program "CL_BGRFC_DB_HELPER============CP" - |
| in "USER_SWITCH". |
| The main program was "SAPMSSY1 ". |
| |
| In the source code you have the termination point in line 11 |
| of the (Include) program "CL_BGRFC_DB_HELPER============CM00V". |
----------------------------------------------------------------------------------------------------
Obs: The 'Wait for Scheduler' status might be experienced in SRT_MONI as a consequence of the missing inbound bgRFC locks, if Web Service messages are flowing in the system.
Read more...
Environment
- ABAP Platform
- SAP NetWeaver
Product
Keywords
RS_CLEAR_RFC_TABLES, ASSERTION_FAILED, CL_BGRFC_DB_HELPER============CP, USER_SWITCH, SM12, BGRFC, Locks, wait for scheduler, SRT_MONI, inbound lock, RS_BGRFC_MASS_PROCESSING, SBGRFCMON , KBA , BC-MID-RFC-BG , Background RFC (bgRFC) , BC-ESI-WS-ABA , Web Service and SOAP - ABAP , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.