Solution : https://service.sap.com/sap/support/notes/1153975 (SAP Service marketplace login required)
Summary :
When an SAP application server becomes non-responsive, further analysis often shows all work processes in RUNNING status as seen in transaction SM50. This can be caused by various issues, mainly related to kernel faults or external influences affecting memory or system functions. It is recommended to apply the latest kernel patch from SAP Service Marketplace to address these. For example, the symptom might emerge from setting rdisp/no_hooks_for_sqlbreak = 1, as this has been proven to cause shared memory corruption. Other potential problems include slowdowns due to DNS lookup delays or inappropriate use of the rdisp/test_roll parameter, leading to work processes accessing invalid memories. Deleting problematic parameters from the profile and updating the kernel typically resolves these issues.
Key words :
error => invalid hypercontext handle fffffffe5d5dab08 46524545 [emxx, increasingly access invalid shared memories, sap gui connection terminates, sap gui connections terminate, support package patch level, parameter reduces system performance, sap service marketplace, sap netweaver version 7, terms system standstill, form warning => niaddrtohost
Related Notes :
| 1132350 | Incomplete update records |
| 1055602 | Automatically deactivating the reverse name lookup |
| 845564 | User SAPSYS blocks all work processes |
| 768371 | Work process blocked after attempt to terminate |