Symptom
Here are the symptoms of this issue.
- One or more work processes are stuck in WP_NEW status in transaction SM50 or SM66.
- The call stack (Note 1964673, KBA 3122914) of the work process shows the following pattern.
- ThInit => ThrtAbapEnvInit2 => checkVersion => XGDKGetFSVersion => FeatureMgr::buildDBList => database calls
- The system may experience performance degradation or become unavailable if many work processes are in the above status.
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Read more...
Environment
All ABAP environments
Product
SAP NetWeaver all versions
Keywords
WP_NEW, ThInit, ThStartUp2, ThrtAbapEnvInit2, ipl_Init, ipl_InitImpl, checkVersion, XGDKGetFSVersion, FeatureMgr, fetchFeatures , KBA , XX-SER-MCC , Mission Control Center - Knowledge Management , BC-FES-ITS , SAP Internet Transaction Server , HAN-DB , SAP HANA Database , 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