Symptom
At SM50, you can see work processes stuck in program "<VMC OP TH_VMC_DELETE_SESSION>".
Just before the situation started, the Dispatcher trace logs that a work process has crashed.
The trace file for the corresponding work process (that has crashed) has the following C-Stack:
jvm!CVMsgcGetSharedGCSnapshot [shared_gc.c (1150)]
jvm!CVMspGetSharedGCSnapshot [shared_pool.c (1199)]
disp+work!ThJGetSGCInfo [thxxjava.c (911)]
disp+work!ThJVmInvolvedInSgc2 [thxxjava.c (10265)]
disp+work!ThJCloneVm [thxxjava.c (9381)]
disp+work!ThJCreateContext [thxxjava.c (8857)]
disp+work!ThJAttachVm2Context [thxxjava.c (7849)]
disp+work!ThVmcAttachServer [thxxvmc.c (4435)]
disp+work!ThVmcICallServer [thxxvmc.c (3808)]
disp+work!ThVmcCallServer [thxxvmc.c (7520)]
(...)
Read more...
Environment
- SAP NetWeaver ABAP based product with VMC active
Product
Keywords
KBA , BC-VMC , Virtual Machine Container , BC-CST , Client/Server Technology , 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.
SAP Knowledge Base Article - Preview