3649405 - Short Dump BLOCKED_COMMIT on HTTP call in bgRFC

When processing a background RFC (bgRFC) unit, the process terminates with a short dump. The ST22 dump analysis shows the following:

A typical ABAP Call Stack leading to this dump looks like this, showing an HTTP client call originating from within a bgRFC execution context:

FUNCTION     SAPLSHTTP                           LSHTTPU16
 HTTP_WRITE_SC
METHOD       CL_HTTP_CLIENT================CP    CL_HTTP_CLIENT================CM00K
 CL_HTTP_CLIENT=>IF_HTTP_CLIENT~SEND
[...]
 (Custom or Standard Application Logic)
[...]
METHOD       CL_RFC_RECORDER_EXECUTOR======CP    CL_RFC_RECORDER_EXECUTOR======CM003
 CL_RFC_RECORDER_EXECUTOR=>IF_RFC_RECORDER_EXECUTOR~EXECUTE_ALL
METHOD       SAPLBGRFC_EXTERN                    LBGRFC_EXTERNF01
 LCL_BGRFC_SERVER=>BGRFC_EXECUTE
FUNCTION     SAPLBGRFC_EXTERN                    LBGRFC_EXTERNU08
 BGRFC_DEST_SHIP
[...]

Images/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental

Read more...

This behavior applies to all SAP NetWeaver and ABAP Platform releases that support bgRFC

• SAP NetWeaver 7.0 and higher
• SAP NetWeaver Application Server for SAP S/4HANA
• ABAP PLATFORM - Application Server ABAP (All versions)

ABAP platform all versions ; SAP NetWeaver 7.0 ; SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP NetWeaver 7.5 for SAP S/4HANA 1511 ; SAP NetWeaver 7.51 for SAP S/4HANA 1610 ; SAP NetWeaver 7.52 for SAP S/4HANA 1709

bgRFC, BLOCKED_COMMIT, HTTP, CL_HTTP_CLIENT, SAPLSHTTP, Transactional Consistency, Implicit Commit, DB_COMMIT , KBA , BC-MID-RFC-BG , Background RFC (bgRFC) , Problem