SAP Knowledge Base Article - Preview

3153768 - How to interpret blocked threads on HttpSessionMutexListener in SAP Commerce Cloud


When facing performance problems and collecting thread dumps, many blocked threads are found waiting to acquire a lock on a org.springframework.web.util.HttpSessionMutexListener$Mutex object:

"hybrisHTTP12" #421 daemon prio=5 os_prio=31 cpu=70.00ms elapsed=452.69s allocated=3744K defined_classes=0 tid=0x00007fefcb4b1000 nid=0x40003 waiting for monitor entry  [0x0000700023c12000]
   java.lang.Thread.State: BLOCKED (on object monitor)
at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(
- waiting to lock <0x00000007d0acecb8> (a org.springframework.web.util.HttpSessionMutexListener$Mutex)
at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(
at org.springframework.web.servlet.DispatcherServlet.doDispatch(
at org.springframework.web.servlet.DispatcherServlet.doService(
at org.springframework.web.servlet.FrameworkServlet.processRequest(
at org.springframework.web.servlet.FrameworkServlet.doGet(
at javax.servlet.http.HttpServlet.service(

This can be observed on monitoring tools as well, such as Dynatrace for example:



Any version of SAP Commerce & SAP Commerce on the Public Cloud.


SAP Commerce Cloud all versions


hybris, stuck, runnable, hanging, blank page , KBA , CEC-SCC-CLA-ENV-EMG , Environment Management , CEC-COM-CPS-PRF , Performance , How To

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.