SAP Knowledge Base Article - Preview

3118007 - Improper implementation of AfterSaveListener could lead to thread issue when load is high


When the site load is high, one of the scenario might happen is that one or more application server became thread saturated.

If we check the problematic application server, the DB connection pool is full even though in the meantime there's no response time issue from DB side.

From the thread dumps of the problematic application server, we could notice a lot of threads are in WAITING or TIMED_WAITING status, which are related with AfterSaveListener.



AfterSaveListener , KBA , CEC-SCC-PLA-PL , Platform , 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.