Solution : https://service.sap.com/sap/support/notes/3223 (SAP Service marketplace login required)
Summary :
Interactive sessions and RFC communications errors may surface due to insufficient sizing of shared memory areas, keying errors such as "No WP block received" and system log entries of R36 or Q03. The system utilizes rdisp/wp_ca_blk_no for allocating wp_ca blocks and rdp/appc_ca_blk_no for appc_ca blocks, potentially needing adjustment if session counts or work processes have increased. Each block size is defined—wp_ca at 32048 bytes and appc_ca at 34816 bytes. Appropriate parameter adjustments guided by formulas correlating to the system's workload, like user count and active connections, can prevent these issues and necessitate a server restart following changes.
Key words :
rdisp/wp_no_dia + rdisp/wp_no_vb + rdisp/wp_no_vb2 + rdisp/wp_no_enq + rdisp/wp_no_btc + rdisp/wp_no_spo, rdisp/wp_no_dia + rdisp/wp_no_vb + rdisp/wp_no_vb2 + rdisp/wp_no_enq + rdisp/wp_no_btc + rdisp/wp_no_spo, rdisp/wp_ca_blk_no ~ rdisp/tm_max_no + 2, parameters rdisp/wp_no_dia, rdisp/wp_no_vb, rdisp/wp_no_vb2, rdisp/wp_no_enq, rdisp/wp_no_btc, rdisp/wp_no_spo, -> information -> appc-ca blocks
Related Notes :
| 1587018 | SPM freezes and server hangs with log error ***LOG R36 |
| 384971 | System parameters for high interface load |