- The affected instance suffers from an apparent standstill situation. Most actions will just hang and new users cannot logon to the application server.
- You also notice that a few processes seem to be waiting for semaphore 39, in the snapshot generated in dispatcher trace file (dev_disp)
- One of the following warning entries is noticed at work process trace files:
*** WARNING => MtxLock xxYYxxYYxxYY EMADM owner=<wp number> deadlock ? [mtxxx.c 2574]
*** WARNING => MtxLock xxYYxxYYxxYY EGPHxx owner=<wp number> deadlock ? [mtxxx.c 642]
- By extracting the C-STACK from the work process number displayed as the mutex holder (owner=<wp number>), the following (or similar) is seen:
<signal handler called> [0x7f94b12a8c00,0x11c00]
SAP NetWeaver release independent
semaphore 36, semaphore 39, mutex, freeze, hanging situation, extended global, SAP memory , KBA , BC-CST-DP , Dispatcher, Task Handler , BC-CST-MM , Memory Management , Problem
About this pageThis 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.